From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jx22S-0002yy-6e for qemu-devel@nongnu.org; Fri, 16 May 2008 11:40:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jx22Q-0002xq-NN for qemu-devel@nongnu.org; Fri, 16 May 2008 11:40:07 -0400 Received: from [199.232.76.173] (port=58350 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jx22Q-0002xb-I6 for qemu-devel@nongnu.org; Fri, 16 May 2008 11:40:06 -0400 Received: from mail2.shareable.org ([80.68.89.115]:37968) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jx22Q-0001pQ-3B for qemu-devel@nongnu.org; Fri, 16 May 2008 11:40:06 -0400 Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from ) id 1Jx22O-0000nz-0Z for qemu-devel@nongnu.org; Fri, 16 May 2008 16:40:04 +0100 Date: Fri, 16 May 2008 16:40:03 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] Problem installing NT4 under QEMU 0.9.1 - IDE driver error under high load? Message-ID: <20080516154003.GC32498@shareable.org> References: <482DA817.4010402@siriusit.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482DA817.4010402@siriusit.co.uk> Reply-To: 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 Mark Cave-Ayland wrote: > Upon reboot, I get a BSOD and errors about files being corrupted on the > partition. However the error goes away, and the install completes fine > after the reboot if I use the cdrom directly, i.e. I run qemu like this: > > qemu-system-x86_64 -hda /home/images/ntfs.img -cdrom > /dev/hda -vnc localhost:11 -no-acpi -win2k-hack -boot d > > If I execute 'md5sum winnt4.img' and 'md5sum /dev/hda' then I get back > the same MD5 hash for both the physical CDROM copy and the local CD > image, so I am fairly sure the local CD image is not corrupt. I have > also tried with/without -win2k-hack and it doesn't seem to make a > difference. > > My theory is that there is some form of race condition in the IDE driver > related to the transfer speed. When using the local winnt4.img CD > image, the installation is very quick, but the resulting file system > appears to be corrupted. When I use the real CD inserted into /dev/hda, > the installation is much slower but the file system appears fine. > > Has anyone else experienced similar symptoms during normal QEMU usage? Fwiw, I am experiencing similar problems with Windows Server 2003 which is already installed. Someone else prepared a working WS2003 image inside VirtualPC (a Microsoft VM which runs only on Windows hosts). I took the disk image, which QEMU understands (thank you), and tried to run it under QEMU (with/without KQEMU), and KVM. (It bluescreened on boot but that's an NT problem from changing hardware. I applied the registry fix which lets it boot, using a Windows XP guest (running in QEMU) to apply the registry fix. Then it booted. This is due to QEMU providing PIIX3 while VirtualPC provides PIIX4 IDE emulation.) On the first successful boot, my WS2003 image insisted on running chkdsk. It took a _very_ long time in KVM (due to video refresh slowness), so I ran it in QEMU which is ironically much faster at this, even without KQEMU. chkdsk showed thousands of errors, which it repaired. But even after repair, some files are corrupted or missing in the running image. I still have yet to verify whether the image is fine, or was corrupted when it was sent to me, or was sent to me in a "suspended" rather than "powered off" state. But such a large number of chkdsk repairs isn't expected for a "suspended" state, and corruption isn't likely. I had also wondered if may QEMU's VHD disk format module wasn't handling the format correctly. But another possibility is a fault in the IDE emulation. -win2k-hack didn't change the behaviour. -- Jamie