search for: domcreate_rebuild_done

...e code path to qemu pid is defined .It seems that qeum-xen points to loacation I don''t see were it is defined. xc: detail: elf_load_binary: phdr 0 at 0x0x7f71cac72000 -> 0x0x7f71cad079d5 libxl: error: libxl_dom.c:612:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:885:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1250:libxl__destroy_device_model: could not find device-model''s pid for dom 14 libxl: error: libxl.c:1414:libxl__destroy_domid: libxl__destroy_device_model failed for 14 libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x1bcc300...

...: xc_dom_boot.c:161: xc_dom_boot_mem_init: can''t allocate low memory for domain: Out of memory libxl: error: libxl_dom.c:430:libxl__build_pv: xc_dom_boot_mem_init failed: Device or resource busy libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)build domain: -3 The variable-underflow happens when freemem_slack is larger then info.free_pages*4, because the solution of this operation is converted implicit to a unsigned int to match the type of memory_kb. The problem is fixed by a proper casting. Signed-off-by: R...

...e giving me the same error so I do not believe it is related to a change in Xen. The first attempt to pass a PCI device after booting the system gives me these messages (on "xl create"): libxl: error: libxl_dom.c:557:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1239:libxl__destroy_device_model: could not find device-model''s pid for dom 1 libxl: error: libxl.c:1427:libxl__destroy_domid: libxl__destroy_device_model failed for 1 The baffling part is that all subsequent attempts are successful....

...g now xc: error: 0-length read: Internal error xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal error xc: error: read: p2m_size (0 = 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 creat...

Did something had chaqnged with spice code or settings. I just compiled latest git of 4.4 unstable and I get is a black screen all I see is the green boot image from server 2012 but I dont get blue windows logo and window does not resize it stays black. I reverted back to older git revision of 4.4 and everything is working fine with. _______________________________________________ Xen-users

...bxl__get_numa_candidate: NUMA placement failed, performance might be affected xc: error: panic: xc_dom_core.c:587: xc_dom_find_loader: no loader found: Invalid kernel libxl: error: libxl_dom.c:380:libxl__build_pv: xc_dom_parse_image failed: No such file or directory libxl: error: libxl_create.c:908:domcreate_rebuild_done: cannot (re-)build domain: -3 I attached the code ( it''s very small). Thanks _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

.... So it seems it doesn't quite have enough PVH support. I get: xc: error: panic: xc_dom_core.c:702: xc_dom_find_loader: no loader found: Invalid kernel 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...

...libxl_bootloader.c:634:bootloader_finished: bootloader failed - consult logfile /var/log/xen/bootloader.14.log 2018-05-27 11:24:36.666+0000: libxl: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader [183216] exited with error status 1 2018-05-27 11:24:36.667+0000: libxl: libxl_create.c:1259:domcreate_rebuild_done: cannot (re-)build domain: -3 /var/log/xen/bootloader.14.log: -> Traceback (most recent call last): File "/usr/lib64/xen/bin/pygrub", line 896, in <module> part_offs = get_partition_offsets(file) File "/usr/lib64/xen/bin/pygrub", line 113, in get_partition_offs...

...libxl: notice: libxl_numa.c:491:libxl__get_numa_candidate: NUMA placement failed, performance might be affected xc: error: Could not open kernel image (2 = No such file or directory): Internal error libxl: error: libxl_dom.c:620:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1300:libxl__destroy_device_model: could not find device-model's pid for dom 3 libxl: error: libxl.c:1416:libxl__destroy_domid: libxl__destroy_device_model failed for 3 libxl: debug: libxl_event.c:1569:libxl__ao_complete: ao 0x19811c0: compl...

...nfig from /vm/arch1/arch1.conf libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader failed - consult logfile /var/log/xen/bootloader.85.log libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus: bootloader [-1] died due to fatal signal Killed libxl: error: libxl_create.c:1022:domcreate_rebuild_done: cannot (re-)build domain: -3 This is the vm conf that I use when booting with the arch install iso after loop mounting it /mnt. name = "arch1" kernel = "/mnt/arch/boot/x86_64/vmlinuz" ramdisk = "/mnt/arch/boot/x86_64/archiso.img" extra = "archisobasedir=arch ar...

...nfig>", I get: Parsing config from router.internal.tomjepp.uk xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' (2 = No such file or directory): Internal error libxl: error: libxl_dom.c:1006:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:1142:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:2004:libxl__destroy_device_model: xs_rm failed for /local/domain/0/device-model/5 libxl: error: 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__de...

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?

...nconsoled.pid So I try : xl create neoload Parsing config from neoload xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' (2 = No such file or directory): Internal error libxl: error: libxl_dom.c:1006:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:1142:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:2004:libxl__destroy_device_model: xs_rm failed for /local/domain/0/device-model/1 libxl: error: 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__destr...

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB

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