search for: domain_destroy_callback

...tus 1 libxl: error: libxl_device.c:1084:device_hotplug_child_death_cb: script: ip link set vif38.0 name vNIC1 failed libxl: error: libxl_create.c:1381:domcreate_attach_vtpms: unable to add nic devices libxl: error: libxl.c:1591:libxl__destroy_domid: non-existant domain 38 libxl: error: libxl.c:1549:domain_destroy_callback: unable to destroy guest with domid 38 libxl: error: libxl.c:1476:domain_destroy_cb: destruction of domain 38 failed When removed the vifname settings the domU starts just fine. vif = [ '' ] Same error when used wi classic Bridge for networking. Is vifname setting still supported? On...

...Success): Internal error libxl: error: libxl_create.c:820:libxl__xc_domain_restore_done: restoring domain: Success libxl: error: libxl_create.c:902:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain 9 libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy guest with domid 9 libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to destroy domain 9 following failed creation xl save/restore and other details can be attached if needed. Regards, Cristian Tomoiaga _______________________________________________ Xen...

...model: spawn failed (rc=-3) libxl: error: libxl_create.c:1340:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1959:kill_device_model: Device Model already exited libxl: error: libxl.c:1580:libxl__destroy_domid: non-existant domain 29 libxl: error: libxl.c:1538:domain_destroy_callback: unable to destroy guest with domid 29 libxl: error: libxl.c:1465:domain_destroy_cb: destruction of domain 29 failed (xen-4.6rc3-4.el7.x86_64) -- --------- Greetz

...ernel libxl: error: libxl_dom.c:638:libxl__build_dom: xc_dom_parse_image failed: No such file or directory libxl: error: libxl_create.c:1223:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl.c:1575:libxl__destroy_domid: non-existant domain 8 libxl: error: libxl.c:1534:domain_destroy_callback: unable to destroy guest with domid 8 libxl: error: libxl.c:1463:domain_destroy_cb: destruction of domain 8 failed (I get the same with your recipe based on upstream master, so I don't think it's a bug in my backport.) I can upgrade this host to buster at some point in the nearish futur...

...c=-3) > libxl: error: libxl_create.c:1340:domcreate_devmodel_started: device model > did not start: -3 > libxl: error: libxl_dm.c:1959:kill_device_model: Device Model already exited > libxl: error: libxl.c:1580:libxl__destroy_domid: non-existant domain 29 > libxl: error: libxl.c:1538:domain_destroy_callback: unable to destroy guest > with domid 29 > libxl: error: libxl.c:1465:domain_destroy_cb: destruction of domain 29 > failed > > (xen-4.6rc3-4.el7.x86_64) > > -- > --------- > Greetz > _______________________________________________ > CentOS-virt mailing list > Cen...

...: error: libxl_create.c:1896:domcreate_devmodel_started: Domain 8:device model did not start: -26 libxl: error: libxl_aoutils.c:646:libxl__kill_xs_path: Device Model already exited libxl: error: libxl_domain.c:1183:libxl__destroy_domid: Domain 8:Non-existant domain libxl: error: libxl_domain.c:1137:domain_destroy_callback: Domain 8:Unable to destroy guest libxl: error: libxl_domain.c:1064:domain_destroy_cb: Domain 8:Destruction of domain failed I started digging around in this QMP stuff and installed Xen freshly on another server with the actual bookworm iso, but the problem is the same there, too. After reading t...

...ate: how=(nil) callback=(nil) poller=0x119c920 libxl: error: libxl_create.c:420:libxl__domain_make: domain creation fail libxl: error: libxl_create.c:646:initiate_domain_create: cannot make domain: -3 libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain -1 libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy guest with domid 4294967295 libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to destroy domain 4294967295 following failed creation libxl: debug: libxl_event.c:1499:libxl__ao_complete: ao 0x119c890: complete, rc=-3 libxl: debug: libxl_create.c:1187:do_domain_cre...

...libxl_dm.c:1956:kill_device_model: unable to find device model pid in /local/domain/5/image/device-model-pid libxl: error: libxl.c:1628:libxl__destroy_domid: libxl__destroy_device_model failed for 5 libxl: error: libxl.c:1591:libxl__destroy_domid: non-existant domain 5 libxl: error: libxl.c:1549:domain_destroy_callback: unable to destroy guest with domid 5 libxl: error: libxl.c:1476:domain_destroy_cb: destruction of domain 5 failed An example config that triggers this issue: name='router.internal.tomjepp.uk' builder='hvm' vcpus=2 memory=512 disk=[ 'format=raw, vdev=hda, access=rw, target=...

On 1/6/19 11:21 AM, Colin Watson wrote: > On Sat, Jan 05, 2019 at 10:51:13PM +0100, Hans van Kranenburg wrote: >> On 1/5/19 8:04 PM, Colin Watson wrote: >>> I think I'm OK with cherry-picking the relevant patch stack. Presumably >>> this would need to be in new grub-xen-pvh-bin / grub-xen-pvh binary >>> packages, as is usual for separate platform builds?

...r: libxl_dm.c:1956:kill_device_model: unable to find device model pid in /local/domain/1/image/device-model-pid libxl: error: libxl.c:1628:libxl__destroy_domid: libxl__destroy_device_model failed for 1 libxl: error: libxl.c:1591:libxl__destroy_domid: non-existant domain 1 libxl: error: libxl.c:1549:domain_destroy_callback: unable to destroy guest with domid 1 libxl: error: libxl.c:1476:domain_destroy_cb: destruction of domain 1 failed The directory "/usr/lib/xen" does not exist on my system ! And no "hvmloader" program as in previous versions. The /usr/lib/xen-4.6 directory does not even contain...

This is problem 1 of 3 problems we are having with live migration and/or ACPI on Xen-4.3 and Xen-4.2. Any help would be appreciated. Detailed description of problem: We are using Xen-4.3-rc1 with dom0 running Ubuntu Precise and 3.5.0-23-generic kernel, and domU running Ubuntu Precise (12.04) cloud images running 3.2.0-39-virtual. We are using the xl.conf below on qemu-upstream-dm and HVM and