How to import existing VMs (KVM + libvirt) into Opennebula?

Question

KVM

Actually, there are 3 nodes, one of which works as a frontend.
Before the roll-out of Opennebula, virtual machines under KVM were already running on these nodes.
The task, actually, is already sounded in a question. I struggle with connecting existing VMs.
What I did:
0. I set up sunstone on the docks and connected 2 nodes.
1. Created a repository.
Type Image
Base_path /var/lib/libvirt/images
2. Create a VM image. I get an error

[ImM][I]: cat: /var/lib/livbirt/images/pinba-server.vps: No such file or directory
Tue Mar  4 17:29:20 2014 [ImM][I]: stat: cannot stat `/var/lib/livbirt/images/pinba-server.vps': No such file or directory
Tue Mar  4 17:29:20 2014 [ImM][E]: stat: Cannot determine size for /var/lib/livbirt/images/pinba-server.vps
Tue Mar  4 17:29:20 2014 [ImM][I]: ExitCode: 255
Tue Mar  4 17:29:20 2014 [ReM][E]: Req:1856 UID:0 ImageAllocate result FAILURE [ImageAllocate] Cannot determine Image SIZE

The virtual machine image file is located exactly where it is indicated. Permissions to all files 777. The owner of the files is oneadmin.
There is a lot of material on the net, but there is no sensible description of HOW to import KVM virtual machines into OpenNebula.
Empty disks are created, but it does not work from a copy of an existing one.
If I create an empty disk and then replace it with the one I want to use in the VM, I get the error "Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/0/16/deployment.0
" logs for this machine says:

Tue Mar  4 17:59:34 2014 [DiM][I]: New VM state is ACTIVE.
Tue Mar  4 17:59:34 2014 [LCM][I]: New VM state is PROLOG.
Tue Mar  4 17:59:35 2014 [LCM][I]: New VM state is BOOT
Tue Mar  4 17:59:35 2014 [VMM][I]: Generating deployment file: /var/lib/one/vms/16/deployment.0
Tue Mar  4 17:59:35 2014 [VMM][I]: ExitCode: 0
Tue Mar  4 17:59:35 2014 [VMM][I]: Successfully execute network driver operation: pre.
Tue Mar  4 17:59:35 2014 [VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy '/var/lib/one//datastores/0/16/deployment.0' 'vhost003.vps' 16 vhost003.vps
Tue Mar  4 17:59:35 2014 [VMM][I]: error: Failed to create domain from /var/lib/one//datastores/0/16/deployment.0
Tue Mar  4 17:59:35 2014 [VMM][I]: error: cannot open file '/var/lib/one//datastores/0/16/disk.0': No such file or directory
Tue Mar  4 17:59:35 2014 [VMM][E]: Could not create domain from /var/lib/one//datastores/0/16/deployment.0
Tue Mar  4 17:59:35 2014 [VMM][I]: ExitCode: 255
Tue Mar  4 17:59:35 2014 [VMM][I]: Failed to execute virtualization driver operation: deploy.
Tue Mar  4 17:59:35 2014 [VMM][E]: Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/0/16/deployment.0
Tue Mar  4 17:59:36 2014 [DiM][I]: New VM state is FAILED

Does anyone have experience with such manipulations? How do you import cars?

Answer 1

what difference does it make what to import? you make a clean virtulaca with the required volume as in the old one, for example in raw format, and then through dd you roll over the empty image the disk image of the old virtual machine, there should be no problems in general. I’ll even say more, if there is a raw image there, then it will start up with an existing disk in the same way, you just need to add the virtual machine config and that’s it.
And the opennebula is a strange thing, why exactly it? There are other solutions that work much more clearly, the simplest one is proxmox. There is also an ovirt which is essentially redhat's rhev. It is configured normally and clearly and works the same way, and in the opennebule the plugs begin already with the creation of the first hellish account (I looked at 4 versions).