similar to: Re: [Xen-devel] Bug: /proc/xen Doesn't Mount

Good evening everyone, I am attempting to compile Xen 4.2.1 from source on Ubuntu 12.10 and cannot for the life of me figure out what I am doing wrong. This is the script I wrote that I am running on a brand new install from ubuntu-12.10-server-amd64.iso apt-get update apt-get -y upgrade apt-get -y dist-upgrade reboot (uname -r returns back 3.5.0-23-generic) apt-get install -y build-essential

Hi everyone, I''m trying to start up domU on xen for ARM (Cortex-A15 Fast models). I follow the instructions to build xen-tools with this link: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling. But there seems to be something wrong when I start up domU. First, I get errors in create domU with xl: root@(none):/home/xiaogw# xl create domU-config xc: error:

# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1326564288 -3600 # Node ID 259112aee618753552056e398f940d1fd9fcc6f7 # Parent f581bb82fecd51e8fbd9c2e4ae9e76b08a695587 libxl: fix mutex initialization The macro PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP is not defined on NetBSD, so define mutex attributes manually. Changes since v1: * Fix leak of mutex attr.

Hello, I build and installed Xen (4.1.3) from source, and I think I have got it working. Well, almost. I am using unmodified kernel of Fedora16 as my dom0 kernel. So this is what happened. I am able to boot into Xen, but the "xl info" failed with the standard error message mentioned in the tutorial. "libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to

Hello, I build and installed Xen (4.1.3) from source, and I think I have got it working. Well, almost. I am using unmodified kernel of Fedora16 as my dom0 kernel. So this is what happened. I am able to boot into Xen, but the "xl info" failed with the standard error message mentioned in the tutorial. "libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r 8d6edc3d26d2 -r cfb49fe940fd tools/hotplug/Linux/init.d/xencommons --- a/tools/hotplug/Linux/init.d/xencommons Sat Aug 13 10:14:58 2011 +0100 +++ b/tools/hotplug/Linux/init.d/xencommons Tue Aug 16 16:56:16 2011 -0700 @@ -29,11 +29,9 @@ XENCONSOLED_PIDFILE=/var/run/xenconsoled.pid shopt -s extglob -if test

Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version 3.2.12-1, package blktap-dkms and all dependency packages for xen, spice and usb redirection. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- hg clone http://xenbits.xen.org/xen-unstable.hg (in this build changeset is 25194:6b72eb3b40cf) # Qemu

I just downloaded Xen-4.1.1 from xen.org, compiled it, and installed it. I then compiled kernel 3.0.0 and added the hypervisor and dom0 kernel in a grub 2 entry. After booting, I executed "xl list," to confirm the hypervisor was running. I was greeted with this message: libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to stat /var/run/xenstored.pid: No such

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r cfb49fe940fd -r 81f75ed45ec2 tools/hotplug/Linux/init.d/xencommons --- a/tools/hotplug/Linux/init.d/xencommons Tue Aug 16 16:56:16 2011 -0700 +++ b/tools/hotplug/Linux/init.d/xencommons Tue Aug 16 17:05:18 2011 -0700 @@ -29,12 +29,18 @@ XENCONSOLED_PIDFILE=/var/run/xenconsoled.pid shopt -s extglob -if [

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:

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'm testing the xen-4.2 package from experimental and I've hit a problem trying to use the installed libxenlight library-- I hope this is the right place to discuss it. xen itself seems to be ok, I can start/stop domains with 'xl'. I notice that 'xl' is statically linked so has no problem finding libxenlight. I'm trying to compile libvirt-1.0.3, also from

# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1324385575 -3600 # Node ID 716d6d48e647d1d4352f7206e74e693152a4f8fa # Parent f72b99fccfca694674259cc1c03c526a827b67ec libxl: add support for yajl 2.x This patch adds support for yajl versions 2.x, while retaining 1.x compatibility. This patch adds quite a lot of #ifdefs all over the json code, so I''m open

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:

The xencommons runlevel script has a few modprobe calls to load drivers for dom0. Recently also the backend drivers for vbd and vif were added. Unfortunately without an explanation why that is (suddenly) needed. Now that I have been hitting such missing backend driver issue as well with a xenlinux based dom0 kernel I wonder how to handle the situation. The pvops kernel has 3 backend drivers

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, 4.2 and 4.1 suffers from SEGV during xl network-attach in libxl__device_nic_add. In 4.3-unstable it is fixed by: 5420f2650 libxl: Set vfb and vkb devid if not done so by the caller So either the patch need to be backported to 4.1 and 4.2, or fixed by this one: - ------ libxl: Fix SEGV in network-attach When "device/vif" directory

flight 8091 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8091/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 12 guest-localmigrate/x10 fail REGR. vs. 8071 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 9

YaST2 sysconfig can logically group the various sysconfig settings if the files are tagged. Add the missing (YaST specific) tags to xencommons. See for a description http://old-en.opensuse.org/Packaging/SUSE_Package_Conventions/Sysconfig Signed-off-by: Olaf Hering <olaf@aepfle.de> --- Resending: http://lists.xen.org/archives/html/xen-devel/2012-10/msg01140.html

My server was installed as a "minimal install" in text mode, so there may be some difference between my setup and your laptop. Are you able to email the output of "systemctl list-unit-files" to me so that I can see what services are enabled? I tried installing a couple of the other drivers mentioned in the log file... # dnf install libvirt-daemon-driver-lxc # dnf install

Hello, When destroying a guest (xl destroy <domid>) on NetBSD I get the following error on the log file: Waiting for domain test (domid 1) to die [pid 11675] Domain 1 is dead Unknown shutdown reason code 255. Destroying domain. Action for shutdown reason code 255 is destroy Domain 1 needs to be cleaned up: destroying the domain do_domctl failed: errno 3 libxl: error: