similar to: libxl build errors in xen-unstable

* Introduce new variants of the logging functions which include errno values (converted using strerror) in the messages passed to the application''s logging callback. * Use the new errno-including logging functions everywhere where appropriate. In general, xc_... functions return errno values or 0; xs_... functions return 0 or -1 (or some such) setting errno. * When

I always failed to build the xen in my enironment, with following error (my gcc version is 4.1.2): > gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g > -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value > -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD > -MF .libxenlight.so.1.0.0.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -Werror

Hi, George sent a patch on this problem before, but it was not completed. This patch makes libxl use xenbus to communicate with xenstored if libxl cannot open a socket. There''s a place that does not close fd in the case of failure, which is also fixed in this patch. -----------------------------------------Patch------------------------------------------------------ diff -r eff592364826

Hi, Centos 7 Xen4CentOS - 4.6.1 Open vSwitch When i specify custom name of the domU NIC than it refues to start vif = [ 'vifname=vNIC1' ] libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-openvswitch online [10168] exited with error status 1 libxl: error: libxl_device.c:1084:device_hotplug_child_death_cb: script: ip link set vif38.0 name vNIC1 failed

Hi, I seem to have an interesting issue with vif-route. This is after an update to Xen 4.2.1, switching from xm to xl. I have 10 PV domUs on the host and two FreeBSD ones. All the PV domUs are now working nicely. Since FreeBSD has always been just slightly broken as PV I chose a HVM domU for those, but with PV drivers. Those PV drivers all blew up now after the upgrade. I''m now trying

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: important Dear Maintainer, After upgrading to Debian 8, auto-starting of domUs via /etc/xen/auto fails with errors like this Sep 09 09:29:21 host xendomains[948]: Starting Xen domain domU (from /etc/xen/auto/domU.cfg)...failed. Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus:

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.

This is a Fedora Core 13 environment and I just noticed this as I update the xen-unstable tree: make -C libxl install make[3]: Entering directory `/home/konrad/ssd/xtt/xen-unstable/tools/libxl'' rm -f _libxl_paths.h.tmp.tmp; echo "SBINDIR=\"/usr/sbin\"" >> _libxl_paths.h.tmp.tmp; echo "BINDIR=\"/usr/bin\"" >> _libxl_paths.h.tmp.tmp;

Dear all, I followed the steps described in the wiki in order to get an Arnadle board running Xen, but I''m having trouble in starting a domU. Let me describe you the steps I followed. Sorry for such a long mail, but I think that a verbose description is necessary so you can point me what I''m doing wrong. I couldn''t boot properly over the network. This is why I

hi, i am trying to create hvm in xen via libvirt but i am facing some error. i installed the packages like bltap-utils, blktap-dkms in my dom0. virsh create tiny_core.xml p11-kit: invalid config filename, will be ignored in the future: /etc/pkcs11/modules/gnome-keyring-module error: Failed to create domain from tiny_core.xml error: internal error: libxenlight failed to create new domain

--------------------------------------------------------------------------- The following patch when applied on top of: libxl: attempt to cleanup tapdisk processes on disk backend destroy. Establishes correct cleanup behavior for blktap devices. This patch implements the release of the backend device before calling for the destruction of the userspace component of the blktap device. Without

--------------------------------------------------------------------------- Backport of the following patch from development: # User Ian Campbell <[hidden email]> # Date 1309968705 -3600 # Node ID e4781aedf817c5ab36f6f3077e44c43c566a2812 # Parent 700d0f03d50aa6619d313c1ff6aea7fd429d28a7 libxl: attempt to cleanup tapdisk processes on disk backend destroy. This patch properly terminates the

Changes since v1: - Fix a double-free bug introduced by v1, pointed out by Stefano where internal pointer was being passed back to caller from libxl_create_stubdom() 8<---------------------------------------------------------------------- Currently scratch variables allocated by libxl have the same lifetime as the context. While this is suitable for one off invocations of xl. It is not

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

Hi everybody, my background: I'm doing Xen since 10++ years, many years with DRBD for high availability, since some time I'm using preferable GlusterFS with FUSE as replicated storage, where I place the image-files for the vms. In my current project we started (successfully) with Xen/GlusterFS too, but because the provider, where we placed the servers, uses widely CEPH, we decided to

On Thu, 2015-09-10 at 09:06 +0200, Wolfgang Karall-Ahlborn wrote: > After upgrading to Debian 8, auto-starting of domUs via /etc/xen/auto > fails with errors like this > > Sep 09 09:29:21 host xendomains[948]: Starting Xen domain domU (from /etc/xen/auto/domU.cfg)...failed. > Sep 09 09:29:21 host xendomains[948]: libxl: error: libxl_exec.c:129:libxl_report_child_exitstatus:

Matthew Daley (13): libxl: fix unsigned less-than-0 comparison in e820_sanitize libxl: check for xc_domain_setmaxmem failure in libxl__build_pre libxl: correct file open success check in libxl__device_pci_reset libxl: don''t leak p in libxl__wait_for_backend libxl: remove unsigned less-than-0 comparison libxl: actually abort if initializing a ctx''s lock fails libxl:

Howdy, I'm having an issue with the console for CentOS 6 domUs. When I boot the domU I can see the console just fine. After grub has made its selection I get these errors: xenconsole: Could not open tty `': No such file or directory libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 2 After that the boot process continues fine and

Hi, I am unable to build libxl from the tools. I am getting always the following error. Disabling Werror did not solve the problem: === PCI passthrough capability has been enabled === === PCI passthrough capability has been enabled === make[4]: Entering directory `/usr/src/xen-unstable.hg/tools/ioemu-remote/i386-dm'' /usr/src/xen-unstable.hg//tools/cross-install -d -m0755 -p

Hi guys, I''m running Xen 4.2.1, compiled manually so I can play with Remus and DRBD, running on Ubuntu 12.10. I keep getting this error when trying to start up my first VM to run the Ubuntu netboot installer. ----------------------------------------------------------------- root@left:/home/eross# xl create /etc/xen/ubuntu.cfg -c Parsing config from /etc/xen/ubuntu.cfg Daemon running