Import Promox VM

HI all,

I migrated from Proxmox to OpenNebula.
I have set a new OpenNebula Infrastructure with KVM Host, recreate the network configuration.
How can I “convert and import” all existing VM from proxmox to OpenNebula ?
I see the “Wild VM” mechanism, but I don’t understand how I can use it to import proxmox vm ?


1 Like


The answer about “Wild VM”:

The monitoring mechanism in OpenNebula reports all VMs found in a
hypervisor, even those not launched through OpenNebula. These VMs are
referred to as Wild VMs, and can be imported to be managed through
OpenNebula. This includes all supported hypervisors, even the hybrid
ones …

It mean the VMs was created by Virsh or another tools.

Regarding about import Proxmox VM into OpenNebula, which type of datastore on your system? Example LVM, CEPH…

I’ve write a bash script that parse the proxmox vm conf file, create a template and import the vdisk.
This script work as fine and will be shared as soon as possible.

Hi Yannick,

Could you share the reasons why you move from Proxmox to OpenNebua?


Before OpenNebula, I used Proxmox 3.4
Proxmox is a good product, but I need to increase the capability of my hosting plateform.
In fact, the first reason is : with OpenNebula, we don’t manage on which host you must deploy a VM, One do the job for us.
In Proxmox, you must do this job manually.
OpenNebula give more information about the load of the plateform.
In a more technical overview, Proxmox use the RedHat Cluster solution pour manage HA and I think this very complexe to manage HA (for gfs2 and my vms). For one or two host, it could be a good solution, but I currently have 3 hosts and I think to add 2 ou 3 additionnals hosts.

Even if I don’t yet understand some concept in OpenNebula, OpenNebula seems to be more expandable than Promox.

is feature are better in Proxmox :

  • noVNC : capability to send order to the VM from a toolbar in noVNC (start, stop, …)
  • noVNC : capability to send ALT-GR caracters (like @ or # on a french keyboard).
  • Be able to resize a qcow2 disk.

I see Proxmox as an ESXi environnement without VSPHERE.
I see OpenNebula as an ESXi environnement with VSPHERE.

Hi Yannick,

Thank you for sharing. I wish you success with OpenNebula.

Hi Yannick,
Can you share your experience ( and also this script ) to migrate from Proxmox 2.3 to OpenNebula 5.4 ?
My first attempts to run a qcow2 were unsuccessful :-\

in my log :
Sat Aug 26 11:30:25 2017 [Z0][VM][I]: New state is ACTIVE
Sat Aug 26 11:30:25 2017 [Z0][VM][I]: New LCM state is PROLOG
Sat Aug 26 11:33:43 2017 [Z0][VM][I]: New LCM state is BOOT
Sat Aug 26 11:33:43 2017 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/16/deployment.0
Sat Aug 26 11:33:44 2017 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Sat Aug 26 11:33:44 2017 [Z0][VMM][I]: ExitCode: 0
Sat Aug 26 11:33:44 2017 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Sat Aug 26 11:33:46 2017 [Z0][VMM][I]: ExitCode: 0
Sat Aug 26 11:33:46 2017 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy.
Sat Aug 26 11:33:46 2017 [Z0][VMM][I]: ExitCode: 0
Sat Aug 26 11:33:46 2017 [Z0][VMM][I]: Successfully execute network driver operation: post.
Sat Aug 26 11:33:46 2017 [Z0][VM][I]: New LCM state is RUNNING

but in the console :

/dev/vda1: clean, 367186/1970416 files, 2321244/7870464 blocks

Seems a grub problem ? ( os = ubuntu 16.04 )


when i found it :wink:

I share my shell script in Github :
This script was used only for my use, so you can not used it as is,
I used network with mac address (no ip), so the script also add the mac address in opennebula before.

The process is :

  • I read the proxmox vm file and generate a template file.
  • I import the qcow2 vdisk.
  • I import the template in opennebula