public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alberto Treviño" <alberto@byu.edu>
To: kvm-devel@lists.sourceforge.net
Subject: Chaning disks from IDE to SCSI on a Windows VM
Date: Mon, 14 Apr 2008 12:07:05 -0600	[thread overview]
Message-ID: <200804141207.07061.alberto@byu.edu> (raw)

Anthony Liguori provided patches that allowed booting from SCSI disks 
back in December of 2005.  He also reported the following:

> I have successfully booted Linux, Win2k, and WinXP from SCSI with
> this patch.  Windows takes a bit of prep work to be able to boot from
> SCSI. For win2k, you just need to make sure you have the right driver
> installed.  WinXP, however, seems to require that it be installed on
> SCSI to boot from SCSI.  If anyone knows how to modify WinXP after
> the fact, please let me know.

I think I figured it out for both Windows XP and 2003 server.  It's 
pretty straight forward.

1. Create a new HD image.  It doesn't have to be very big (8 MB will
   do) and you don't have to format it.

2. Start the Windows VM and add this second hard drive to the VM:

   qemu-system-x86_64 -m 256 -hda hda.img \
     -drive file=new.img,if=scsi,bus=0,index=0,media=disk,boot=off ...

   At this point, Windows should start, find the new drive, and install
   all the drivers for it.

3. Shut down the VM.  This time, don't include the new temporary image 
   from step 1 and define your disk(s) as SCSI disks:

   qemu-system-x86_64 -m 256 \
     -drive file=hda.img,if=scsi,bus=0,index=0,media=disk,boot=off ...

   At this point, the Windows VM should boot from the SCSI drive without
   a blue screen.  Verify that the drive is now a SCSI disk by going to
   the Device Manager and making sure the model of the hard drive
   includes the word SCSI.

That's it.  If anyone can attest to this procedures and report, it would 
be greatly appreciated.

Along those lines, if anyone knows how to grab an existing Windows VM 
that was set up in VMware and make it run in Qemu (KVM), I would 
really, really appreciate it.  Everytime I try I get blue screens. :-(

-- 
Alberto Treviño
alberto@byu.edu

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

             reply	other threads:[~2008-04-14 18:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 18:07 Alberto Treviño [this message]
2008-04-15  6:41 ` Chaning disks from IDE to SCSI on a Windows VM Felix Leimbach
2008-04-15  6:57   ` Jun Koi
2008-04-15 16:29     ` Alberto Treviño
2008-04-16  1:28       ` Jun Koi
2008-04-16  6:09         ` Felix Leimbach
2008-04-16  7:58 ` Elmar Haneke

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=200804141207.07061.alberto@byu.edu \
    --to=alberto@byu.edu \
    --cc=kvm-devel@lists.sourceforge.net \
    /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