P2V info
- Thread starter tonycav
- Start date
I'd try VMware converter first.
However I have not used it for a long time and in the end you might run into the same issues as with clonezilla.
The biggest point here is the virtual hardware. You need to make sure that your windows installation will have the right drivers included for disk and network.
So the vmconfig will be critical.
For best compatibility I'd use
- i440fx chipset
- e1000 NIC
- SATA disk
Once you have installed the KVM guest tools you can switch to paravirtualized devices which allow better performance/less overhead
However I have not used it for a long time and in the end you might run into the same issues as with clonezilla.
The biggest point here is the virtual hardware. You need to make sure that your windows installation will have the right drivers included for disk and network.
So the vmconfig will be critical.
For best compatibility I'd use
- i440fx chipset
- e1000 NIC
- SATA disk
Once you have installed the KVM guest tools you can switch to paravirtualized devices which allow better performance/less overhead
Thank you very much, i converted with vmware and then i imported the disk with qm import. I fixed some things and now it works
I am curious, is there any reason that the virtio drivers could not be installed into Windows environment in precedence to performing a Clonezilla migration of the disk image? I know that VMware will insert and configure its own drivers whence it performs a conversion/migration of a VM but I do not think Clonezilla performs any such activity and that as it just copies raw images of disks.
What say you?
Stuart
For me this simlly didnt work.
Only having the driver installed still left my OS unbootable after the migration.
Once there was a virtio disk (and the driver "properly loaded") I was able to switch the bootdisk type to virtio too.
I have spent quiet some time figuring things out during my migration back then - it drove me nuts as the windows VMs gave me so much trouble while Linux just worked fine...
Maybe things have relaxed since then but I can't tell
For me this simlly didnt work.
Only having the driver installed still left my OS unbootable after the migration.
Once there was a virtio disk (and the driver "properly loaded") I was able to switch the bootdisk type to virtio too.
I have spent quiet some time figuring things out during my migration back then - it drove me nuts as the windows VMs gave me so much trouble while Linux just worked fine...
Maybe things have relaxed since then but I can't tell
Fair enough, experience speaks volumes!
The problem I have is that it is not that I need to virtualize this Windows installation, it is that I have applications on there and I do not feel like reinstalling them all and Windows won't update because some DLLs or something are jacked up. I tried doing repair installs and other things, but I fear I will need to reinstall it and all the applications and such. I have backups, but I had rotated the older ones out before I realized there was a problem with the OS.
Stuart