From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DHbpp-0000A7-1l for qemu-devel@nongnu.org; Sat, 02 Apr 2005 01:10:17 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DHbph-00007f-Ot for qemu-devel@nongnu.org; Sat, 02 Apr 2005 01:10:10 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DHbpg-00006Z-W6 for qemu-devel@nongnu.org; Sat, 02 Apr 2005 01:10:09 -0500 Received: from [80.247.70.7] (helo=smtp-out2.email.it) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DHblH-00075a-RS for qemu-devel@nongnu.org; Sat, 02 Apr 2005 01:05:36 -0500 Date: Sat, 2 Apr 2005 08:05:28 +0200 From: Massimo Callegari Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] [QEMU] Windows 2000 image Startup Problems Reply-To: Massimo Callegari , 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 Hi, I'm facing a problem not yet fully documented or experienced in the mailing lists I navigated 'till now, and, in any case, not really solved = so far, for what I know. Here is the description of the situation. I installed a Windows 2000 Image with Qemu (0.6.0-3.1 and qemu-0.6.1-3.1 released via rpm package) under different Linux installations (a Suse PRO 9.2 distribution and a Fedora Core 2/3 versions). The steps performed to obtain this are the following: * Creation of a qcow image: $ qemu-img create -f img Win2000.img 10000M or $ qemu-mkcow create Win2000.qcow 10G * Copy of the installation CD of Windows 2000 on the local hard disk $ dd if=3D/dev/cdrom of=3DWin2000.iso * Installation of Windows 2000 on the Qemu image: $ qemu -boot d -cdrom Win2000.iso -hda Win2000.qcow/img The installation proceeeds without (almost) any problem and ends successfully, but, when I try to load the newly created image ($ qemu Win2000.qcow/img) the system boot ends up with an error message ("Booting from Hard Disk ... Disk Read Error. Press CTRL+ALT+CANC to restart") like= if the mbr of the image were not present or if the partition table didn't recognize a bootable sector on the "virtual" disk. Notice that the problem doesn't appear 'till the boot of the system is ba= sed on the cdrom-based install process as far as windows warm boots (in other words the first time I face the problem is when I cold boot and start my Windows 2000 image with the Qemu command "$ qemu Win2000.qcow/img". The s= ame doesn't happen if I rely on the newly made installation and on the relate= d command "$ qemu -boot d -cdrom Win2000.iso -hda Win2000.qcow/img". In tha= t case the error message is the one reported above). I tried to boot the system from cdrom with "qemu -boot d -cdrom Win2000.i= so -hda Win2000.qcow/img" like during installation and in that case the erro= r message is the same. I noticed that 'till now the only way to have a good bootable image is vi= a the creation of the Qemu image file with the qemu-mkcow command (for me i= t was the only case in which it worked for the windows 2000 installation an= d cold boot) on the Suse 9.2 installation with the qemu-0.6.0-3.1 rpm packa= ge installed. All other tests failed. Did anyone afford and solve this issue (apart from modifying by commentin= g out line 1896 in hw/ide.c) ? I think a definitive solution could made the Emulator more stable and usable. Thanks in advance for your cooperation. Massimo