From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CqlWw-0008Vl-90 for qemu-devel@nongnu.org; Tue, 18 Jan 2005 00:03:50 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CqlTt-0006aV-D1 for qemu-devel@nongnu.org; Tue, 18 Jan 2005 00:00:41 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CqlTk-0006Cn-6L for qemu-devel@nongnu.org; Tue, 18 Jan 2005 00:00:32 -0500 Received: from [64.233.184.201] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Cql0r-0006I4-D8 for qemu-devel@nongnu.org; Mon, 17 Jan 2005 23:30:41 -0500 Received: by wproxy.gmail.com with SMTP id 69so10395wri for ; Mon, 17 Jan 2005 20:30:41 -0800 (PST) Message-ID: Date: Mon, 17 Jan 2005 23:30:40 -0500 From: Joe Bogner In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: Subject: [Qemu-devel] RE: W2K SP0 Status - mmx build Reply-To: Joe Bogner , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I'm pleased to say that I have the .NET Framework 2.0 successfully installed and Visual Web Developer Express. Here's my notes from the weekend. I literally the past three days getting this working.. I'm sending these notes on in the hope that someone else can be spared from the pain and also as a way to contribute back to the community. Qemu rocks! HARDWARE - 3000+ Athlon 64 1 gig of ram 120 SATA hard drive 64mb NVIDIA GEFORCE HOST OPERATING SYSTEM - Windows 2000 Server QEMU IMAGE - QCOW 10gig Using qemu 1/15 CVS version - Attempted to install W2k Pro w/SP4 and received numerous errors (see notes below) (used iso image) - Installed windows 2000 pro w/out service pack (used iso image) - Attempted to install .net framework 2.0 and received Access Violation error in event viewer * Futher investigation on the mailing list indicated a MMX error (CVS version did not have MMX enabled) Using qemu 1/17 CVS version with MMX enabled (custom build) *Security errors show up in EventViewer ("default local machine policy cannot be created") - programs would not install and WindowsUpdate did not work because Windows did not recognize that Administrator was an administrator - corrected by calling "Secedit /configure /db secedit.sdb /cfg basicwk.inf /log temp.log" - *Note: will create another 200mb of log files Install Windows Installer 2.0 - no notice of successful install, but it appeared to work Install .NET Framework 2.0 - first had to extract the files using dotnetfx.exe /a - had to install using quiet using install.exe /q Install IE 6 SP1 Install W2K SP4 SP4 screws up Windows Installer - must roll back to previous version *Error "Setup cannot access Windows Installer Components" - msiinstw.exe /a to extract the files - copy over msi.dll, msihnd.dll, and msiexec.exe - msiexec /unregister - msiexec /register *Notes - Win2k SP0 took a really long time at detecting devices and during the final phase of setup. I had to restart qemu a couple times to get past the detecting devices phase. - Moving the mouse during windows install appeared to help - Switching to the admin console and saving the VM state (savevm) and continuing 'c' also seemed to help - SP4 install fails due to COM+ Catalog error and endless security log generation resulting in out of disk space error. (watch the image file grow during the 'Registering Components' phase) 200MB of files were written - I've created a RAR of my image after each major install, just in case something goes wrong - rar is about about 300-500mb. ---------- Forwarded message ---------- From: Joe Bogner Date: Mon, 17 Jan 2005 18:58:11 -0500 Subject: Re: W2K SP0 Status - mmx build To: qemu-devel@nongnu.org I'm just writing to report that with MMX and SSE enabled ( CPUID_MMX | CPUID_SSE | CPUID_SSE2 ), I was able to install the .NET Framework 2.0 on a Windows 2000 Professional installation running under qemu. It took a little bit of work though, I first had to extract the files from dotnetfx.exe and then run the install in silent and automatic mode. I had a lot of difficulty installing w2k pro. At first I tried using w2k pro+sp4 and would receive errors when configuring COM+. It would never get past the final stage of setup. When I switched to w2k pro without a service pack, I had better luck. It still took at least three hours of rebooting and reinstalling before it finally worked. I seemed to have better luck when I would switch to the admin console and save my vm. I never had to restore the vm though. Just as another tip, somehow full-screen mode tends to work better on an install too (unless I was just seeing things after doing it so many times). I also seemed to have better luck when I'd move my mouse around in the qemu window during long-running setup processes. On Mon, 17 Jan 2005 15:38:02 -0500, Joe Bogner wrote: > I'm having trouble executing qemu after compiling on w2k pro. I > downloaded the 0.6.1 source and followed the porting instructions. > Everything compiled (although I had to use SDL-1.2.8-devel because SDL > wouldn't compile). I'm getting a segfault when I run the compiled > binary. The official release of 0.6.1 works fine on my machine (with > the same image). The version I compiled won't even show the BIOS > before crashing... > > Here's the GDB results: > > $ gdb qemu.exe > GNU gdb 5.2.1 > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i686-pc-mingw32"... > (gdb) set args -L c:/progra~1/qemu/bios -hda c:/virtual/temp.img > (gdb) r > Starting program: c:\dev\qemu\qemu-0.6.1\i386-softmmu/qemu.exe -L > c:/progra~1/qe > mu/bios -hda c:/virtual/temp.img > > Program received signal SIGSEGV, Segmentation fault. > 0x00000000 in ?? () > (gdb) backtrace > #0 0x00000000 in ?? () > #1 0x0044e414 in cpu_x86_exec (env1=0x0) > at c:/dev/qemu/qemu-0.6.1/cpu-exec.c:540 > > I also had the same results with the CVS source. My goal is to enable > MMX in the windows build so I can attempt to install MDAC/.NET > Framework on my windows 2000 pro image. My image works great except > that I get an access violation when attempting to install the .NET > framework. I read on here that lack of MMX support could be at fault. > > Does anyone have any suggestions on what I should try? I've been > fighting with this for at least 5 hours.... Or, I'd be grateful if > someone could just create a windows build with MMX enabled (as > specified below). > > Thanks, > Joe > > ------------------------------------------------------------------------------- > From: Tim > Subject: [Qemu-devel] W2K SP0 Status (was: Re: 2.6.10-mm3: swsusp: > out of memory on resume) > Date: Sat, 15 Jan 2005 13:02:14 -0500 > User-agent: Mutt/1.5.6+20040907i > > -------------------------------------------------------------------------------- > > > I did not enable SSE and MMX for x86 because I fear there are still bugs > > which may cause regressions. Interested people can enable the line: > > > > -- > > env->cpuid_features |= CPUID_FXSR | CPUID_MMX | CPUID_SSE | > > CPUID_SSE2 | CPUID_PAE; > > -- > > > > and see if their OS and application still work. > > I am using exclusively x86 on x86 (target=i386-softmmu). > > I just booted one of my older win2k images without this enabled. > Everything came up fine, and I am still stuck with the SP4 installer > (spews the same "an error has occured" that I have reported in the > past.) No change here. > > Then I added the two lines you mention in target-i386/helper2.c, and > recompiled. Upon booting this old image again, everything worked as > expected. I tried installing SP4 and I got the same old error. So, > this initial test showed no difference with MMX et al. enabled. (I was > hoping that MMX capabilities would fix their SP4 installer, but no > luck there.) > > Next, I kept MMX stuff enabled, and began installing win2k with an image > of the install CD. The disk is partitioned and formatted fine. After > the first reboot, and round of hardware detection, I get the dreaded > "not enough space on disk" error. It gives me the software selection > screen, and it indicates there is 0 space left on disk. I don't > remember how I got around this last time. I'll keep trying. (fyi- I > created this image with 'qemu-img win2k.img 3G'.) > > In short, I don't see any differences so far, besides the disk issue > that comes and goes for those installing Win2k. > > tim >