Using qemu to boot a full hardware installed Windows partion on dual boot system
 

This is more a curiosty type question to know if it would be possible.

I have a dual boot system with Linux Mint 12 and Windows XP.

I sometimes find that while I'm under Linux that I also need access to my Windows OS but not able to reboot just to access it.

I know that from a terminal you can run: that will bring up the grub bootloader to select the Windows partion to boot.

The problem I have ran in to is that qemu changes the hardware so that it causes the Blue Screen of Death when windows starts to load.

Is there an option or a way to config qemu to use the same hardware that windows expects when booting?

qemu is a hypervisor. The "hardware" in a virtual machine created by a hypervisor is all, well, virtual.

Unless the hypervisor is able to emulate the exact same hardware you happen to have inside your PC (extremely unlikely), the answer to your question is "no".

However, it may be possible to emulate hardware that Windows XP supports, avoiding the BSOD. Also, you could boot to Windows and install the necessary drivers for the virtualized hardware. In both cases, the same Windows installation should be able to boot successfully in the virtualized environment as well as on the bare metal hardware.

Unfortunately, you'd probably just run in to another problem, as (perceived) changes in the hardware configuration causes OEM versions of Windows to require reactivation. You'd be reactivating at every reboot.

Ser Olmy is correct. MS terms it the HAL.

The only other way is to find a copy of xp and create a new install. Finding xp copies is getting hard.

yes finding copies of windows xp is getting hard but luckly I do have 2 that were used on a couple of machines that are no more. This frees them up to be used for such a case.

I about a month ago I did try to do an install via qemu of windows xp but it gave me an error. As it was just a curiousity thing, I didn't do to much to trouble shoot it.

if qemu -hda /dev/sd* will boot it then what would I need to actauly install from the cd?

Actually, this is not the case. When Windows XP is installed and registered, the product key is locked to that machine. You can change a graphics card, a network card, a disk drive but not a motherboard. Windows XP sees installation in a virtual machine as an installation onto a machine with a new motherboard. So Microsoft expects you to purchase and register a new product key. The perceived change in motherboard is also the cause of the BSOD due to HAL changes that you have observed when trying to access an existing Windows XP install.

You can do a virgin install of Windows XP in a virtual machine and you will get 30 days of use without registration. The nagging to register is annoying.

Microsoft does not like pirate copies of Windows XP that have the registration requirements removed, but with Windows XP official support ending in April 2014, users are being left with no choice if they have essential software that will not run in Windows7 (even in XP emulation).

One random reminiscence - During torrent storms pirates often shelter in bays.

This is technically incorrect. The key is not in any way bound to the hardware. The installation is. When you make a fresh install you can use the old keys. There may be legal restrictions in doing that, but that is dependent on where you live, in some countries you are not allowed to use a key for a different machine, in some countries (for example Germany) there is no problem in using the keys.

OK - Would have been better written as:
When Windows XP is installed and registered, the product key is locked to that machine for the life of the installation.
The definitive statement is here. http://support.microsoft.com/kb/307890

I should also have used the term activation rather than registration.

Member response
 

Hi,

For OEM not retail Xp. If the license is a OEM the EULA states the license dies with that hardware. Retail purchase allows use of Xp on multiple machines. Meaning you can install on more than one machine but must insure that none will operate simultaneously. Retail package Xp would allow the use & registration of a VM install;
You would retire on other licensed machines/insure that no simultaneous use of the licensed product key on multiple machines then re-register for the VM. Same issue as with upgrade equipment i.e; Motherboards, hard disk or sub-system support then the WPA would be activated/invoked therefore requiring registration of the license. Unless you have a corporate license copy or MSDN.

Plus you could legally run two copies (1-2 CPU Xp Pro) on the same multi-core system but not more than two therefore a VM would be possible (but why). Better way;
I can see the advantage of Win7 hosting a WinXp VM. Better too just purchase additional WinXp license for $35/per install for retail tag(not boxed) while you can.

It's getting were you need to be a lawyer or befriend one. :)

"if qemu -hda /dev/sd* will boot it then what would I need to actauly install from the cd" (?)

Generally for qemu you need to add in the -boot option and the added cdrom information. Linux and windows use similar but different terms. See qemu docs for full list of options.

If your only line was -hda /dev/sdx then we assume that the hda is the boot device. We don't know what is on that from here.