I have change from vmware to Proxmox on my server.
I first export every VM I have into OVF file.
After that I clear the server and install proxmox and also change som HW RAID.
Now after I have import OVF file I get error
Warning: /dev/VolGroup/lv_root does not exist
Warning: /dev/VolGroup/lv_swap does not exist
Warning /dev/mapper/Volgroup-lv-root does not exist
What I have found I can try to update or repare but I can’t even access Rescue or Emergency Mode.
It stop at same place and when I type exit to exit the shell it froze.
It would have been easier to just copy over the .vmdk file and convert that with Proxmox to the .qcow2 or .raw formats… qemu-img convert -O qcow2 image.vmdk image.qcow2
Do you have any backups of NethServer?
You could create a new VM with approximately the same specs as you had on ESXi, then install a plain NethServer. Then restore from Backup…
Tip: Use the default KVM64 CPU. If you need to move to different hardware, you won’t have any issues with Proxmox, even Intel to AMD!
In any case, keep the OVF file safe for the moment!
Thanks for the replay
No backup more then OVF file
I maybe can create a new vmware or Viritual box and import OVF file and then export it again?
Right now I have import one windows 2019 server and many debian/ubuntu server with no problem.
Well not more then I have to change the interface for network in debian and ubuntu
Anyways, your best bet is install VMWare ESXi again and import that OVF file - it should work in the same version of ESXi.
Test it!
Then shutdown the VM, and copy the .vmdk file to a NAS or USB stick…
Reinstall Proxmox.
Use either XFS or ZFS as file system.
Create a new VM with the GUI, with the same Specs as in VMWare. Don’t use CPU sockets, use only cores in Proxmox. And leave the CPU to the default in Proxmox, KVM64. Deactivate the firewall in the new VMs NIC.
When the VM is created, don’t start it!
Copy the .vmdk file into the storage where Proxmox creates it’s VM
(eg: /var/lib/vz/images/vmid)
Rename the original Proxmox VMdisk (eg vm-100-disk-0.raw to vm-100-disk-0.raw_old
run the convert command:
qemu-img convert -O raw image.vmdk image.raw
Adapt the disk names accordingly.
As the target (image.raw) use the original name Proxmox used…
Since the converted disk has the same name proxmox used - it’s all correctly in the VM config of Proxmox and should now boot up…
Yes
I have two servers lying in two different places that run backup every night.
But I must admit it is a bit worse when it comes to operating systems as vmware then requires that you have to shut down to run a copy and I did not want that.
But I going to look into to convert vmdk into raw and see if I can get it to work.
But it have to be later, is late here in sweden now
Install veeam linux agent, make backup, and than restore on proxmox. Or ReaR backup, can do the same thing alike veeam… And you are good to go. Much faster.