qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [QEMU] Windows 2000 image Startup Problems
@ 2005-04-02  6:05 Massimo Callegari
  2005-04-02 19:02 ` Struan Bartlett
  0 siblings, 1 reply; 4+ messages in thread
From: Massimo Callegari @ 2005-04-02  6:05 UTC (permalink / raw)
  To: qemu-devel

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=/dev/cdrom of=Win2000.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 based
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 same
doesn't happen if I rely on the newly made installation and on the related
command "$ qemu -boot d -cdrom Win2000.iso -hda Win2000.qcow/img". In that
case the error message is the one reported above).

I tried to boot the system from cdrom with "qemu -boot d -cdrom Win2000.iso
-hda Win2000.qcow/img" like during installation and in that case the error
message is the same.

I noticed that 'till now the only way to have a good bootable image is via
the creation of the Qemu image file with the qemu-mkcow command (for me it
was the only case in which it worked for the windows 2000 installation and
cold boot) on the Suse 9.2 installation with the qemu-0.6.0-3.1 rpm package
installed. All other tests failed.

Did anyone afford and solve this issue (apart from modifying by commenting
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

^ permalink raw reply	[flat|nested] 4+ messages in thread
* Re: [Qemu-devel] [QEMU] Windows 2000 image Startup Problems
@ 2005-04-07 20:18 Massimo Callegari
  2005-04-07 22:45 ` Struan Bartlett
  0 siblings, 1 reply; 4+ messages in thread
From: Massimo Callegari @ 2005-04-07 20:18 UTC (permalink / raw)
  To: Struan Bartlett, qemu-devel

> Did you try the NT-BOOT-MAIN patch? (copy attached) It works for me 
> routinely.

Thanks for your tip, but I have a further (maybe) silly question: stated
that the qemu version I mainly use is an rpm for qemu-0.6.1-3.1 on a Fedora
Core 2 installation, where should I find the qemu/hw/ide.c file ? I looked
for it over the whole filesystem without finding it.


Regards. Massimo

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-04-07 22:22 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-04-02  6:05 [Qemu-devel] [QEMU] Windows 2000 image Startup Problems Massimo Callegari
2005-04-02 19:02 ` Struan Bartlett
  -- strict thread matches above, loose matches on Subject: below --
2005-04-07 20:18 Massimo Callegari
2005-04-07 22:45 ` Struan Bartlett

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).