Booting Virtual XP Mode image in KVM

MimCom

Active Member
Apr 22, 2011
204
3
38
Southwest NM
Successfully converted the VirtualXPVHD image to qcow2, copied that into a new KVM and booted:
Code:
root@pve1:~# cp VirtualXP.qcow2 /var/lib/vz/images/108/vm-108-disk-1.qcow2 
root@pve1:~# ls -lh  /var/lib/vz/images/108/
total 1.1G
-rw-r--r-- 1 root root 1.1G Apr 14 18:39 vm-108-disk-1.qcow2

But hangs here at boot after choosing either normal or Safe Mode.
Screen Shot 2014-04-14 at 18.41.50 .png
Any pointers?

thanks~
 
Hello mhotel

You can clone (also by copying) a windows installation easily when you keep the same type of virtual HW as kvm, vmware etc., but to move a windows installation to another HW type (regardless if it´s a real or virtualized one) is not simple.

Take a look here:

http://blog.loftninjas.org/2009/05/11/migrating-virtual-pc-windows-servers-to-kvm/

After playing around in the past with such stuff I know such screenshots very well - now I prefer to make a fresh install in such a case.

Kind regards

Mr.Holmes
 
I converted the .vdmk to a .qcow2 using qemu-img just like the recent addition to the guide shows. I did not edit the .conf file, but named my .qcow2 file to replace the default .qcow2 file created by the setup dialog. I'm hoping to find someone who has successfully used this XP Mode image under KVM.

Here's my conf file for the record:
Code:
bootdisk: ide0
cores: 2
ide0: local:108/vm-108-disk-1.qcow2,size=32G
ide2: none,media=cdrom
memory: 3096
name: XPtest
net0: virtio=E6:E8:FD:AC:58:5E,bridge=vmbr0
ostype: wxp
sockets: 1
 
I have... repeatedly.
I have to install the mergeid first. Then I run VHD2DISK
I run a qmconvert for the vhd.
Create a new virtual machine for the XP KVM.
Move the original .qcow2 file in command line.
Move the CONVERTED qcow2 file in the same path and filename as the original. Then I boot without problem. The only issue I have is when I resize disk it automatically adds 30gb. No matter what I have as the original size.
 
I have... repeatedly.
Excellent!

I have to install the mergeid first.
Then I run VHD2DISK

You lost me on these two. I'm using the unmodified vhd file extracted from the XP Mode distribution .exe archive.

The only issue I have is when I resize disk it automatically adds 30gb. No matter what I have as the original size.
I did notice that the Proxmox GUI reports a 32G disk even though the qcow2 file is only 1.1G. I'll edit the .conf file and see what that does.

Edit: Entering '1.1G' in the .conf file resulted in the GUI saying 1181116006. I changed the .conf file to the actual size of the .qcow2 file and now the GUI reports 1079M.
 
Last edited:
You lost me on these two. I'm using the unmodified vhd file extracted from the XP Mode distribution .exe archive.

You have to get your original XP Machine up and running again. Run the mergid Registry edit. Then extract the .vhd again.
After you have a new .vhd with the mergeid edit, you can do the convert, and boot a new KVM.
I have been using the program VHD2Disk for all of my hardware Windows machines, but it sounds as if your Windows machine is already in a vhd format. I am not sure how that stack up running in a Windows 7 XP Mode, but I will test that tomorrow. However, I am for sure that my process works. Let me know if anything fails.

Mergeide file ( http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#mergeide )
http://pve.proxmox.com/wiki/File:Mergeide.zip

Disk2VHD file ( http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx )
http://download.sysinternals.com/files/Disk2vhd.zip
 
Gotcha -- makes far more sense now. I was hoping to find a way to boot the virgin XP Mode image inside KVM and just modify from there -- the goal being a bootable minimal, naked, but unregistered XP image from which to create other VMs on ProxMox.

I can probably borrow a Win 7 laptop and experiment on that.
 
@SpiritAre you using the mergeide before running Disk2VHD?If not, then maybe the only thing that needs to be done is to run the Disk2VHD in XP Mode.My assumption is that the vhd provided by Windows 7 for XP Mode does not include the shared resources/files which are needed for XP to run standalone, whereas Disk2VHD should create an image from the perspective of XP. Just an assumption
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!