If you have this system set up how you want and it required a lot of configuration, one option might be to do a full backup (including system state) of the configured system, then install windows on an hvm and do a full restore, I have read that this is a good p2v (and vice versa) method for Windows, as the system state backup apparently doesn't replace drivers. I have never tried it, so I can't tell you the caveats, but depending on your situation, it might be worth a shot (I have read similar articles about moving from one piece of hardware to another). Also, in Windows, all drivers are loaded the same way, so if the right driver can be installed from the initial hardware configuration, Windows will boot in the new configuration. I have done this many times to change HD controllers in the same system for performance reasons (going to a separate IDE controller was a big performance boost on old IDE computers). I never had much luck doing that, though, unless I could put the hardware in to install the drivers for, that may mean that it won't automatically use a driver just because it is there, it has to be associated with the specific piece of hardware. Nonetheless, depending on how much time you want to spend, you might have some options. Dustin -----Original Message----- From: fedora-xen-bounces@xxxxxxxxxx [mailto:fedora-xen-bounces@xxxxxxxxxx] On Behalf Of Jeff Layton Sent: Wednesday, December 19, 2007 09:55 To: John Summerfield Cc: Fedora Xen Subject: Re: kvm crash on f8 On Tue, 18 Dec 2007 17:58:24 +0900 John Summerfield <debian@xxxxxxxxxxxxxxxxxxxxxx> wrote: > John Summerfield wrote: > > Richard W.M. Jones wrote: > >> John Summerfield wrote: > > > > > The good news is that the system now boots grub sans menu. I typed > > in the necessary information to boot windows: > > chainloader (hd0,0)+1 > > boot > > > > and windows boots all the way to a BSOD and the stuff on the screen > > recommends "chkdsk /f." > > > > Hmm. Type to find a rescue system. > > fwiw same happens when I boot directly from the partition. Ideas > welcome. > Windows is picky about hard disk drivers. The initial installation seems to install some drivers that get loaded early for your disk hardware. QEMU emulates a different type of hardware than what you probably have and so it can't find the root disk once the kernel has booted. If you change the main disk controller on a real machine, you'll probably have the same problem. I'm not aware of a way to fix that, unfortunately. I've generally had to install my windows images from scratch. -- Jeff Layton <jlayton@xxxxxxxxxx> -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
