qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Massimo Callegari <e_mc2@email.it>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [QEMU] Windows 2000 image Startup Problems
Date: Sat, 2 Apr 2005 08:05:28 +0200	[thread overview]
Message-ID: <cf842ed7e60a056f1b8a9afc0622b511@82.48.219.111> (raw)

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

             reply	other threads:[~2005-04-02  6:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-02  6:05 Massimo Callegari [this message]
2005-04-02 19:02 ` [Qemu-devel] [QEMU] Windows 2000 image Startup Problems 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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cf842ed7e60a056f1b8a9afc0622b511@82.48.219.111 \
    --to=e_mc2@email.it \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).