Migrate physical equipment or from vmware to proxmox

[ocerda]

Good Morning,

I read that in proxmox 5.0 you can migrate vmware machines to proxmox. I would like to know how I should do it, since I have tried it in many ways and it has not worked for me.

How do I migrate a physical machine (windows or linux) to a virtual machine (proxmox)?

How do I migrate a virtual machine (vmware) to a virtual machine (proxmox)?

 

[tom]

Start reading here:

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE

 

[ocerda]

Start reading here:

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE

Hello,

That page I have already looked at it, and it is not for proxmox 5.0, it is for previous versions, since proxmox 4.4 changed the site images and following that page I have not been able to convert my images of physical machines or vmware machines to proxmox.

 

[LnxBil]

The page describes the process very well. Maybe you can specify what

I have not been able to convert my images of physical machines or vmware machines to proxmox.

means. What commands did you run and at which step is it not working?

 

[ocerda]

The page describes the process very well. Maybe you can specify what



means. What commands did you run and at which step is it not working?

I used vmware converter to convert the physical machine to virtual (vmdk).

Once I have my machine in vmdk format, I mount the disk in proxmox and do the following:

qemu-img convert <MYVMname> -flat.vmdk -O raw <MYVMname> .raw

dd if = Windows10.raw of = / dev / pve / vm-105-disk-1

When it finishes, if I use lvdisplay, I see that it has copied my image well.

When I boot the computer, booting hard disk comes out.

I have changed the hardware of the machine in proxmox, and the same message comes out.

I used this: vmware-vdiskmanager -r whatever.vmdk -t 2 whatever-pve.vmdk and I have repeated the previous steps and the same error.

In version 5 of proxmox, how do you migrate from vmware to proxmox, or from physical machine to proxmox?

 

[LnxBil]

Your process is correct (even rather long, I'd combine the dd and qemu-img into one command by using the volume path directly as the output file) and if your virtual machine does not startup correctly, you have to fix it beforehand as it was described here:

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Windows_systems_specific_P2V_issues

Converting the virtual harddisk is the easiest step, getting all the drivers correct is much harder - if we're talking about Windows. All-in-all these are all guest-os problems not and not strictly PVE problems. PVE does its job admirably.

 

[ocerda]

Your process is correct (even rather long, I'd combine the dd and qemu-img into one command by using the volume path directly as the output file) and if your virtual machine does not startup correctly, you have to fix it beforehand as it was described here:

https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Windows_systems_specific_P2V_issues

Converting the virtual harddisk is the easiest step, getting all the drivers correct is much harder - if we're talking about Windows. All-in-all these are all guest-os problems not and not strictly PVE problems. PVE does its job admirably.

My problem has already been solved, the hardware problem, in proxmox I had to tell him that windows 10, was EFI and already started correctly.

How would the command to make it shorter and not so long?

Thank you.

 

[LnxBil]

You way:

qemu-img convert <MYVMname> -flat.vmdk -O raw Windows10.raw.raw
dd if=Windows10.raw of=/dev/pve/vm-105-disk-1

One step:

qemu-img convert <MYVMname> -flat.vmdk -O raw /dev/pve/vm-105-disk-1

 

[Jarvar]

What if I don't have a /dev/pve/ directory? I am using local-zfs storage. Does this make a difference?
Thank you in advance.
also followed the wiki page https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Physical_.28running.29_Windows_server_to_Proxmox_VE_.28KVM.29_using_VMware_Converter which suggested
/var/lib/vz/images/100/
but I don't have that folder as well. my images folder was empty, unless I created a specific folder for my disk.

 

[LnxBil]

What if I don't have a /dev/pve/ directory? I am using local-zfs storage. Does this make a difference?

Yes, that makes a difference, please check if this blockfile exists:

/dev/zvol/<poolname, e.g. rpool>/<dataset, e.g. proxmox>/vm-<vmid>-disk-1

 

[spirit]

What if I don't have a /dev/pve/ directory? I am using local-zfs storage. Does this make a difference?
Thank you in advance.
also followed the wiki page https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Physical_.28running.29_Windows_server_to_Proxmox_VE_.28KVM.29_using_VMware_Converter which suggested
/var/lib/vz/images/100/
but I don't have that folder as well. my images folder was empty, unless I created a specific folder for my disk.

use "qm importdisk" command, you can choose your targetstorage directly.

 

[Jarvar]

Thank you. I don't know how to import the disk directly using the file location. I eventually resorted to using : qm importdisk <vmid> <path to disk> local-zfs

But then again I read somewhere that this is the preferred method since the last couple versions of Proxmox. Is this correct? Or just with ZFS volumes?