Hello,
After a long time i figured it out.
The disks are not encrypted. The names are generated by OpenNebula without the .qcow2 or .raw termination.
You just have to take the disk and change the name to the disk in Proxmox and start the VM.
Thank you for your assistance.
Hello,
Sorry for the late response and thank you for your solution but there is a problem.
I have an identical VM on my Proxmox and after the import the hard disk is not bootable.
/mnt/pve/Array3-NFS1# qm importdisk 103 9055c0eb00a190a455ff9adaf838b52b Array3-NFS1 --format qcow2
Formatting...
the real filename path for a qemu process is:
where from /var/lib/one/datastores/168/789ac20a57c5ca7d745d443c33f913b6 - 168 is the ID of the datastore and from /var/lib/one//datastores/131/1349/ - 1349 is the ID for the VM
Hello,
I need to migrate from OpenNebula to Proxmox VE. Given that they both use KVM in the back, it should be pretty easy. Even if we have to recreate the VMs, that shouldn’t be too big of a deal. The problem is that the disks (.qcow2 or .raw, depending on how old is the machine created) are...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.