similar to: xl create bug on first-attempt with passthrough

When I try to start hvm qemu-xen I get this error It seems that the path my be off. Can someone point me were in source 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:

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

Package: xen-utils-common Version: 4.4.1-6 Severity: normal Dear Maintainer, (There appear to be several reports on the BTS with concerns relating to this report. Some unarchiving/merging may be necessary. Reassignment may be needed as well since I'm not sure which package this problem would fall under. Ultimately decided to file with xen-utils-common with 'xl' being the frontend

When xl is called to create a domU and there is not enough memory available, then the autoballooning is called to extract memory from dom0. During the ballooning a loop in libxl_wait_for_free_memory() waits unless enough memory is available to create the domU. But because of a variable-underflow the loop can finish too soon and xl finally aborts with the message: xc: error: panic:

Hello Xen Users, Been experimenting with upstream-qemu and wanted to try out the OVMF bios option, but I seem to be missing something. Are there additional steps to installing OVMF beyond compiling Xen? I saw notes on patching back in february, but I thought the package was included with Xen 4.2 on release. When I attempt to set it as my bios option, the machine boots then immediately closes.

Package: xen-utils-4.3 Version: 4.3.0-3 Severity: normal II'm install xen-4.3 from official repository. When i try create virtulal machine got error: xl -vvvv create /etc/xen/xlexample.hvm Parsing config from /etc/xen/xlexample.hvm libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x19811c0: create: how=(nil) callback=(nil) poller=0x1981220 libxl: verbose:

Hello, After saving and restoring a DomU (teste on the same server), doing a reboot to the newly restored domU will cause it to crash. This happens on PV and PVHVM domUs. I am using qemu upstream for the HVM guests, but I don''t really think it matters as long as PV guests behave the same. I want to confirm this if possible, before submitting a bug report and more details. I am using

Good day - This is my first post to this list , and I''m new to Xen - any help on this issue would be much appreciated . I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on an x86_64 ArchLinux box updated to latest software as of today. I am trying to bring up a Linux guest from a remote iSCSI disk. The iSCSI-initiator (open-iscsi) logs in to the remote target OK and

Hi, I was wondering if there is any documentation on how to write a bare metal application for Xen. I don''t need to parse the device tree and such yet, a simple booting "Hello World" would be fine :-) We wrote one and when trying to boot we get ( this was an uncompressed binary, no image): libxl: notice: libxl_numa.c:451:libxl__get_numa_candidate: NUMA placement failed,

On Mon, Jan 07, 2019 at 08:44:50AM +0000, Colin Watson wrote: > On Mon, Jan 07, 2019 at 01:58:19AM +0100, Hans van Kranenburg wrote: > > Ok great. Since I'm not using (and probably not going to use) the > > multi-stage multiboot things, this is harder for me to help with. > > With any luck I should be able to work that bit out myself, since I > think stable's Xen

I''m unable to start xl console on latest xen-unstable (build with commit 8e0da8c07f4f80e14314977a11f738bd74a5b62b). > xl -vvv console sid > xenconsole: Could not read tty from store: No such file or directory I also tried "xl create -c", and it shows console from pygrub but when the "xl create" reaches the end I got the same error: > xenconsole: Could not

Hi it is possible to use xen and spice already? If yes is there any howto or doc how? If I turn on spice in cfg of a hvm domU, I get this error: Parsing config from /etc/xen/marax.cfg libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: base group enabled libxl: detail: libxl_dom.c:238:hvm_set_viridian_features: freq group enabled libxl: detail:

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

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

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,

This patch introduces support for two new parameters in libxl: smbios_firmware=<path_to_smbios_structures_file> acpi_firmware=<path_to_acpi_tables_file> The changes are primarily in the domain building code where the firmware files are read and passed to libxc for loading into the new guest. After the domain building call to libxc, the addresses for the loaded blobs are returned and

Source: xen Version: 4.6.0-1 Severity: important Dear Maintainer, I attempted to create a HVM domU - using a config that previously worked on xen 4.4 (on Jessie). When I execute "xl create <vm config>", 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

Anthony PERARD (3): libxl_qmp: Use GC instead of CTX as parameter for _initialize. Provide dm_vnc() as a in libxl helper. libxl: Set VNC password through QMP tools/libxl/libxl_create.c | 2 +- tools/libxl/libxl_dm.c | 32 ++++++++++++++---------- tools/libxl/libxl_internal.h | 7 ++++- tools/libxl/libxl_qmp.c | 55 ++++++++++++++++++++++++++++++----------- 4 files

This patch introduces support for two new parameters in libxl: smbios_firmware=<path_to_smbios_structures_file> acpi_firmware=<path_to_acpi_tables_file> The changes are primarily in the domain building code where the firmware files are read and passed to libxc for loading into the new guest. After the domain building call to libxc, the addresses for the loaded blobs are returned and