Existing Windows XP partition required as Virtual Machine

[Alexvk]

Hi,

I am running Debian Lenny using GRUB boot manager to handle my multiboot Debian and Windows XP.

I am trying to get my existing windows XP partition and ALL its installed applications to install under VirtualBox.

QUESTIONS:-

1.) Is there any way in which VirtualBox can read / parse the windows XP registry and create an equivalent virtual machine under VirtualBox?

2.) If not how do I create some sort of file that VirtualBox can use to install the relevant structure for VirtualBox?

3.) Why must I create a new VDI file, thus using MORE of my precious hard disk real estate than the diskfill trash from microsoft already consumes?

4.) Why can I not just get a virtual machine to use the existing windows environment on the existing windows partition, thus keeping ALL my application specific data and settings in the one place - typically Palm Hotsync where some alarms may go off under the VM which may or may not be running at the time, since, presumably the directory /Program Files/Palm/username from the last Hotsync may now be situated inside the VDI ??? etc. file? If I happened to be running windows or straight Debian (not VirtualBox) then would I not be missing all my appointments and reminders if I last did a Hotsync under VirtualBox?

5.) If VirtualBox cannot run from my existing windows partition keeping all the application specific data and settings in the original place, then please can you recommend or point me to some other virtual machine software that will run under Debian Lenny?

Thanking you in anticipation
Alex

[Sasquatch]

Check the sticky in the Windows Guests forum, that describes nicely how to do it. You have to keep a few things in mind, and that is the kernel you're booting in (the Windows kernel), if you have a dual core CPU, it will be problematic when booting in VB. It's covered in the howto. Also the point of Windows activation is dealt with.

As for point 5), what do you think? We're not going to recommend a different virtualization program here, that's like shooting yourself in the foot.

[vbox4me2]

As for point 5), what do you think? We're not going to recommend a different virtualization program here, that's like shooting yourself in the foot.

Well sort of....
1. if it works you must be using VBox
2. if it almost works you have to keep trying VBox
3. if it doesn't work, go via bugtracker to get VBox working.
So really there are some choices

[Sasquatch]

We're still not recommending the competitor .