Hey Guys,

When I try to deploy a Xen HVM VM I got the following message:

Wed Dec 7 11:51:29 2016 [Z0][VMM][I]: libxl: error: libxl_dm.c:717:libxl__build_device_model_args_new: qemu-xen doesn't support read-only disk drivers
Wed Dec 7 11:51:29 2016 [Z0][VMM][I]: libxl: error: libxl_dm.c:1393:device_model_spawn_outcome: (null): spawn failed (rc=-3)
Wed Dec 7 11:51:29 2016 [Z0][VMM][I]: libxl: error: libxl_create.c:1188:domcreate_devmodel_started: device model did not start: -3
Wed Dec 7 11:51:29 2016 [Z0][VMM][I]: libxl: error: libxl_dm.c:1489:kill_device_model: unable to find device model pid in /local/domain/100/image/device-model-pid
Wed Dec 7 11:51:29 2016 [Z0][VMM][I]: libxl: error: libxl.c:1437:libxl__destroy_domid: libxl__destroy_device_model failed for 100
Wed Dec 7 11:51:29 2016 [Z0][VMM][E]: Unable
Wed Dec 7 11:51:29 2016 [Z0][VMM][I]: ExitCode: 3
Wed Dec 7 11:51:29 2016 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Wed Dec 7 11:51:29 2016 [Z0][VMM][E]: Error deploying virtual machine: Unable
Wed Dec 7 11:51:29 2016 [Z0][VM][I]: New LCM state is BOOT_FAILURE

Any idea how I can fix it?

Imported from: http://dev.opennebula.org/issues/3750

Contains patch

If xen (4.4.1) VM has dynamically attached disk and do live migration, then attached disk is lost in VM.
If we detach disk and do live migration, then VM fails (go to UNKNOWN state).

The cause of problem is that attach/detach doesn't update VM config file deployment.X - live migration use it when restoring.

If we poweroff and resume VM before live migration, then it works as expected, because VM config file deployment.X is updated/regenerated.

The same problem could be for NICs and cold migration and suspend/resume.

Imported from: http://dev.opennebula.org/issues/4230

Mostly http://docs.opennebula.org/4.14/administration/hosts_and_clusters/host_guide.html#importing-wild-vms

Imported from: http://dev.opennebula.org/issues/4164

Error:

Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/xen4/deploy '/home/jfontan/work/one/install-4.14.2/var//datastores/0/6/deployment.1' '10.3.3.88' 6 10.3.3.88
Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: libxl: error: libxl_create.c:478:libxl__domain_make: domain creation fail
Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: libxl: error: libxl_create.c:743:initiate_domain_create: cannot make domain: -3
Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: libxl: error: libxl.c:1384:libxl__destroy_domid: non-existant domain -1
Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: libxl: error: libxl.c:1348:domain_destroy_callback: unable to destroy guest with domid 4294967295
Tue Nov 17 12:12:27 2015 [Z0][VMM][I]: libxl: error: libxl_create.c:1320:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation
VM is undefined after poweroff.

First of all let me thank you for the work on OpenNebula!
I wondered about the status of OpenNebula/addon-xen .

Will addon-xen work with current (5.4) OpenNebula?
Is it still maintained and there simply where no open issues in the last 14 month, or is it dormant?
Cheers and thanks once again!

I am trying to upgrade a 4.12 nebula installation to 5.2 and i have been facing this issue with openvswitch

i want to use the openvswitch because of the support for vlans amongst other functions (eventually using a lot of SDN features)
now when i insantiate a vm, i see a boot failure and the following error on the logs
[[Z0][VMM][I]: No tap device found for nic 0

it goes into boot_failure state but when i login to the node and startup the vm using xl creatte, it comes up normally and i am able to recover the state to running

so my obvious question is whether the ovswitch implementation in opennebula 5 is specific to kvm in this case or am i doing something obviously wrong here ?

i had already posted this on nebula forums as well...Its at https://forum.opennebula.org/t/opennebula-5-xen-and-openvswitch-issues/2409/7

Please let me know if there is any further debugging info required here..

Xen's Domain-0 should not appear on the list of wild VMs as it is the hypervisor itself. Not sure what happens when it is imported and a user tries to run operations on it (black holes? inception?.. I don't want to find out)..

From: http://dev.opennebula.org/issues/4233

I am using OpenNebula 5.0.1 and added a Xen node with

onehost create localhost -i xen -v xen -c 0

The output of onehost is

onehost show 1

HOST 1 INFORMATION
ID : 1
NAME : localhost
CLUSTER : default
STATE : MONITORED
IM_MAD : xen
VM_MAD : xen
LAST MONITORING TIME : 07/22 14:28:02

HOST SHARES
TOTAL MEM : 0K
USED MEM (REAL) : 0K
USED MEM (ALLOCATED) : 0K
TOTAL CPU : 0
USED CPU (REAL) : 0
USED CPU (ALLOCATED) : 0
RUNNING VMS : 0

MONITORING INFORMATION
IM_MAD="xen"
RESERVED_CPU=""
RESERVED_MEM=""
VM_MAD="xen"

When I try to instantiate a VM the scheduler does not find a host:

Fri Jul 22 14:31:12 2016 [Z0][HOST][D]: Discovered 1 enabled hosts.
Fri Jul 22 14:31:13 2016 [Z0][SCHED][D]: Match-making results for VM 3:
Cannot schedule VM, there is no suitable host.

Imported from: http://dev.opennebula.org/issues/4232

In

src/vmm_mad/remotes/poll_xen_kvm.rb

there is a function:

    def self.get_vm_disk_stats(doms)
        dom_disk_stats = {}
...
        return dom_disk_stats     
    end

However, the "dom_disk_stats" variable is never updated with any disk information which is extracted. This results in no disk information being returned by the poll script.

Additionally, the function makes assumptions about the naming of the disks as being in the form of "disk.3" and extracts a disk_id ("path.split(".")[-1]"). When processing wild VMs, the disks will not be named in this form and this will lead to unexpected results.

Additionally, although the JSON output format for "qemu-img info" is only available in Xen >=4.2, although with earlier versions of Xen the code silently fails earlier and this section is never reached.

Github link to file/line: https://github.com/OpenNebula/one/blob/master/src/vmm_mad/remotes/poll_xen_kvm.rb#L707

I'm trying to configure a new node host with xen and having some trouble.. This log appears in oned.log. Someone else already had this problem?

Error parsing host information: syntax error, unexpected VARIABLE, expecting EQUAL or EQUAL_EMPTY at line 1, columns 7:16. Monitoring information: