search for: device_model_spawn_outcom

...0000000000100000->000000000019bae4 TOTAL: 0000000000000000->000000003c000000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001df 1GB PAGES: 0x0000000000000000 libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory Daemon running with PID 3912 ========================================================================================= My Windows2003.cfg file is above....

...0000000000100000->000000000019bae4 TOTAL: 0000000000000000->000000003c000000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001df 1GB PAGES: 0x0000000000000000 libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory Daemon running with PID 3912 ========================================================================================= My Windows2003.cfg file is above....

...: 0000000000100000->000000000019bae4 TOTAL: 0000000000000000->000000003c000000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001df 1GB PAGES: 0x0000000000000000 libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3) libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No such file or directory Daemon running with PID 3912 ========================================================================================= My Windows2003.cfg file is above. b...

...detail: 4KB PAGES: 0x0000000000000200 xc: detail: 2MB PAGES: 0x00000000000003f7 xc: detail: 1GB PAGES: 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:...

...0000000000000000->0000000000000000 TOTAL: 0000000000000000->000000003e000000 ENTRY 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 amd...

...or in its dependencies. With gfx_passthru=0 (default), I'm able to boot a domU and access its interface using 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 'upst...

...00000000000200 > xc: detail: 2MB PAGES: 0x00000000000003f7 > xc: detail: 1GB PAGES: 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-exis...

...s: 0000000000000000->0000000000000000 TOTAL: 0000000000000000->000000000f800000 ENTRY 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...

...0000000000000000->0000000000000000 TOTAL: 0000000000000000->000000003e000000 ENTRY 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...

...pe=ioemu,bridge=ovsbr0"] device_model_version = "qemu-xen-traditional" If I didnot add " 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" "...

...00000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003f7 1GB PAGES: 0x0000000000000002 xc: error: panic: xc_dom_boot.c:388: xc_dom_gnttab_hvm_seed: failed to add gnttab to physmap [errno=22] : Internal error libxl: error: libxl_dm.c:1218:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3) libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge add [4567] exited with error status 1 libxl: error: libxl_create.c:1116:domcreate_attach_pci: unable to add nic devices libxl: error: libxl_dm.c:1251:libxl__destro...

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):

The first patch is a leftover from the switch to libxl__create_qemu_logfile, and while there it also handles possible errors when opening /dev/null. The second one is a fix for the issues present in do_daemonize. Thanks, Roger.

...info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000005fb 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_devi...

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

...see this error? The server is going live. Currently I cannot test anything as the server is moving back to data center. I would rather use ''final'' version of XEN because the server goes live, I cannot risk downtime/crashes that much... > >> libxl: error: libxl_dm.c:1218:device_model_spawn_outcome: domain 1 >> device >> model: spawn failed (rc=-3) >> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: >> /etc/xen/scripts/vif-bridge add [4567] exited with error status 1 >> libxl: error: libxl_create.c:1116:domcreate_attach_pci: unable to add >> n...

...: 0000000000100000->000000000017c328 TOTAL: 0000000000000000->000000017f800000 ENTRY ADDRESS: 0000000000100608 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000003fb 1GB PAGES: 0x0000000000000004 libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 8 device model: spawn failed (rc=-3) libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge add [504] exited with error status 1 libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge add [527] exited with error status 1...

...0xf90360 wpath=/local/domain/0/device-model/3/state token=3/0: event epath=/local/domain/0/device-model/3/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: com...

Hi- I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device model. On boot I see the following error: MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h) A list search yielded (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172), however there was no solution for an HVM VM. I''ve