Hello,
I am trying to move my last several VMs from ESXi, the linux ones were a cinch but Windows7 ones are giving me some trouble.
On ESXi, I use the "ghettoVCB" backup tool which under the hood, uses "vmkfstools -i" to clone the VMs and make a "thin" .vmdk backup (which is a .vmdk text file, and a vm-flat.vmdk large file which appears to be a sparse file, for example allocated 200gb but ls -s will show the used sized of 65 gb).
Since I have this same backup location mounted (Read-only) to proxmox node, I did this:
qemu-img convert /nfs/vmbackup.vmdk -O qcow2 /var/lib/vz/qemu-server/images/125/vm-125.qcow2
This runs without error, outputs a 65 gb qcow2 file as I would expect, and the VM boots OK at first in proxmox but then Windows goes into a repair mode and says "Fixing disk issues" for about 2 hours, then it says it cannot fix it.
The *only* steps I did in preparation for the VM on windows guest beforehand:
I installed mergeide.zip
VMwaretools was never installed on these VMs
I powered off the VM before making the .vmdk backup.
I accepted the default settings on proxmox, which uses the virtio scsi driver, and I selected qcow2 format of 200gb disk. In the 125.conf file it says "ide0"
I did *not* try to match the UUID or Mac address or anything yet, should I?
Thanks for any help.
And yes I did read the migration wiki page .. but if I missed something I dont know. I am not using the desktop vmware, it is ESXi server on the same LAN as proxmox nodes in the datacenter .. I can scp, rsync, or NFS files across, but the NFS of the thin .vmdk backup is by far the fastest method.
I am trying to move my last several VMs from ESXi, the linux ones were a cinch but Windows7 ones are giving me some trouble.
On ESXi, I use the "ghettoVCB" backup tool which under the hood, uses "vmkfstools -i" to clone the VMs and make a "thin" .vmdk backup (which is a .vmdk text file, and a vm-flat.vmdk large file which appears to be a sparse file, for example allocated 200gb but ls -s will show the used sized of 65 gb).
Since I have this same backup location mounted (Read-only) to proxmox node, I did this:
qemu-img convert /nfs/vmbackup.vmdk -O qcow2 /var/lib/vz/qemu-server/images/125/vm-125.qcow2
This runs without error, outputs a 65 gb qcow2 file as I would expect, and the VM boots OK at first in proxmox but then Windows goes into a repair mode and says "Fixing disk issues" for about 2 hours, then it says it cannot fix it.
The *only* steps I did in preparation for the VM on windows guest beforehand:
I installed mergeide.zip
VMwaretools was never installed on these VMs
I powered off the VM before making the .vmdk backup.
I accepted the default settings on proxmox, which uses the virtio scsi driver, and I selected qcow2 format of 200gb disk. In the 125.conf file it says "ide0"
I did *not* try to match the UUID or Mac address or anything yet, should I?
Thanks for any help.
And yes I did read the migration wiki page .. but if I missed something I dont know. I am not using the desktop vmware, it is ESXi server on the same LAN as proxmox nodes in the datacenter .. I can scp, rsync, or NFS files across, but the NFS of the thin .vmdk backup is by far the fastest method.