Hi all,
I have a problem with a migration of a windows server vm (vmdk) from vmware to pve.
I try this:
First on the vmware machine I installed from https://fedoraproject.org/wiki/Windows_Virtio_Drivers all drivers.
Conversion
qemu-img convert -c -p -O qcow2 Z:\VMWARE-VM.vmdk Z:\PVE-VM.qcow2
Upload to local server disk and create a vm with same charateristics (equal ram cpu and virtio for network).
So now the first question:
At this step if I read on this post: https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE - in
Adapt the new KVM Virtual Machine section it tells that:
Thanks in advance,
Emanuele Al Koudsi
I have a problem with a migration of a windows server vm (vmdk) from vmware to pve.
I try this:
First on the vmware machine I installed from https://fedoraproject.org/wiki/Windows_Virtio_Drivers all drivers.
Conversion
qemu-img convert -c -p -O qcow2 Z:\VMWARE-VM.vmdk Z:\PVE-VM.qcow2
Upload to local server disk and create a vm with same charateristics (equal ram cpu and virtio for network).
So now the first question:
At this step if I read on this post: https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE - in
Adapt the new KVM Virtual Machine section it tells that:
- Go to the hardware tab on the web interface and remove the default harddisk file
- Add the migrated harddisk as IDE for windows (only IDE works for windows) or SCSI for Linux
- 2012-09-24: virtio now also works for windows, but it can not boot from it the first time. So boot as IDE, then shutdown, add or change a 2. harddisk as virtio, then boot up. Then shut down. Then change the ide0 to virtio0, I do that using vi in the console. Then you can boot up windows again, and it will change to the virtio driver, and say that the driver is from RedHat.
- Start the new Virtual Machine via the management interface
- First boot takes some time as some drives has to be loaded
- Do not forget to install Paravirtualized_Network_Drivers_for_Windows
- Finished!
Thanks in advance,
Emanuele Al Koudsi