search for: domcreate_devmodel_start

...0x0000000000000000 xc: detail: elf_load_binary: phdr 0 at 0x7fab7190a000 -> 0x7fab719bb151 domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000 libxl: error: libxl_dm.c:1849:device_model_spawn_outcome: domain 29 device 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:1...

Checked out the latest unstable version of Xen 4.4 but failed to create a PVHVM domU Configured Xen with ./configure --prefix=/usr DomU config file: name = "pvhvm" builder=''hvm'' device_model = ''qemu-xen'' memory = ''512'' vcpus = ''4'' pae=1 acpi=1 apic=1 vif = [ ''mac=00:16:3E:51:20:8C, bridge=xenbr0,

...in 8:error on QMP socket: Connection reset by peer libxl: error: libxl_qmp.c:1438:qmp_ev_fd_callback: Domain 8:Error happened with the QMP connection to QEMU libxl: error: libxl_dm.c:3371:device_model_postconfig_done: Domain 8:Post DM startup configs failed, rc=-26 libxl: 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 g...

...ADDRESS: 0000000000100608 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001ef 1GB PAGES: 0x0000000000000000 libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: domain 6 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1075:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1306:libxl__destroy_device_model: Device Model already exited # dpkg -l |grep xen ii libxen-4.3 4.3.0-3+b1 amd64 Public libs for Xen ii libxen-4.4 4.4.0-2 amd64 Public libs for Xen ii libxenstor...

...ing vnc. However if I enable gfx_passthru, the domU fails to boot, and I'm greeted with an error message telling me the device model failed to spawn: libxl: error: libxl_dm.c:1371:device_model_spawn_outcome: domain 16 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1186:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1475:kill_device_model: Device Model already exited According to xl.cfg(5) this is to be expected since the default 'upstream qemu-xen device-model currently does not have support for gfx_passthru.' xl.cfg(5) also mentions tha...

...xc: detail: elf_load_binary: phdr 0 at 0x7fab7190a000 -> 0x7fab719bb151 > domainbuilder: detail: xc_dom_gnttab_hvm_seed: called, pfn=0xff000 > libxl: error: libxl_dm.c:1849:device_model_spawn_outcome: domain 29 device > 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 &...

...TRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x000000000000007b 1GB PAGES: 0x0000000000000000 libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: domain 2 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1075:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1306:libxl__destroy_device_model: Device Model already exited If I follow the suggestions in the warning messages and specify firmware_override and device_model_override like so: firmware_override = "/usr/lib64/xen/boot/hvmloader&quo...

...ADDRESS: 0000000000100608 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001ef 1GB PAGES: 0x0000000000000000 libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: domain 6 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1075:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1306:libxl__destroy_device_model: Device Model already exited >/usr/bin/qemu-system-i386 Could not initialize SDL(No available video device) - exiting >cat mywin7.xm device_model_version = "qemu-xen" device_model_overr...

...ot; device_model_version = "qemu-xen-traditional" " to ubuntu.cfg, I only can add four NICs to VM. If I add five or more,, I got these errors: libxl: error: libxl_dm.c:1371:device_model_spawn_outcome: domain 12 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1186:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1475:kill_device_model: Device Model already exited If I add " device_model_version = "qemu-xen-traditional" " to ubuntu.cfg, I can apply 8 NICs to VM. But, I want to create domU by virsh(libvirt), so How convert &...

...0005fb 1GB PAGES: 0x0000000000000001 libxl: error: libxl_dm.c:1142:libxl__spawn_local_dm: device model /usr/lib/xen-4.3/bin/qemu-dm is not executable: No such file or directory libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: (null): spawn failed (rc=-3) libxl: error: libxl_create.c:1075:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1300:libxl__destroy_device_model: could not find device-model's pid for dom 2 libxl: error: libxl.c:1408:libxl__destroy_domid: libxl__destroy_device_model failed for 2 Exit 3 # cat snaptest.cfg builder='hvm' name = "exam...

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

This patch adds a new option for xen config files for directly mapping hardware io memory into a vm. Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 index 013270d..428da21 100644 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -496,6 +496,17 @@ is given in hexadecimal and may either a span e.g.

Hi, Here is a little patch that attempt to fix the issue regarding xen_platform_pci=0 not been handled. There is one patch left from the previous version. The patch that was adding qemu_machine_override have been removed as it is unnecessary. If someone wants to change the -machine, it can always add it to device_model_args_hvm, as QEMU appear to use the last one. Regards, Anthony PERARD (1):

.../state libxl: debug: libxl_event.c:596:libxl__ev_xswatch_deregister: watch w=0xf90360 wpath=/local/domain/0/device-model/3/state token=3/0: deregister slotnum=3 libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: domain 3 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1075:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1306:libxl__destroy_device_model: Device Model already exited libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0xf8fda0: complete, rc=-3 libxl: debug: libxl_event.c:1541:libxl__ao__destroy: ao 0xf8fda0: destroy xc: debug: hypercal...