similar to: Bug#648670: xm was unable determine an actual domU state under some conditions

Package: xen-utils-4.1 Version: 4.1.1-3 I have an HVM domU which was created with xen-utils-4.0 (and Xen 4.0 hypervisor of course). Recently I've upgraded to Xen 4.1 and xen-utils-4.1, but after a reboot I was unable to do anything with it: "xm start" caused "Domain is already running" error, while "xm shutdown" simply hadn't printed any error messages, only

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Hi guys, Just a couple of things I noticed running through /usr/share/doc/xcp-xapi/README.Debian.gz as referenced by http://wiki.debian.org/XCP In "4/ Configuring Xen and XCP": sed -i "s/TOOLSTACK=/TOOLSTACK=xapi/" /etc/default/xen should be sed -i "s/TOOLSTACK=.*/TOOLSTACK=xapi/" /etc/default/xen Otherwise

Package: xcp-xapi Version: 1.3.2-15 Severity: normal I am trying to pass an SRIOV virtual function in a virtual machine but the attempt fails with the following errors shown in the xcp-xapi.log [20130829T19:29:17.909Z|debug|sriov1|314 UNIX /var/lib/xcp/xapi|VM.start R:9e8e10bd31bb|pciops] PCI devices from other-config:pci to attach: 0/0000:04:00.1 [20130829T19:29:18.012Z|debug|sriov1|314 UNIX

Package: xcp-xapi Version: 1.3.2-8 Severity: important During startup /etc/init.d/xendomains script is called. That script is installed with xen-utils-common witch xcp-xapi is depends on. That script calls /usr/sbin/xen as xen list &> /dev/null This 'xen' seems to call xapi: xen list ^Z [1]+ Stopped xen list root at lab-xh3:~# ps f PID TTY STAT TIME

Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log:

There's no date defined yet, but Wheezy freeze will happen soon. How do we plan on concluding on this bug report? Recap for the actual bug I reported: If you want to start xapi, execute the following steps: 1) Start /etc/init.d/xend 2) Stop /etc/init.d/xend 3) Start /etc/init.d/xcp-xapi Step 1 is required because you need access to /proc/xen/ Step 2 is required because xapi cannot run

Package: xcp-xapi Severity: important The README doc mentions: 4/ Configuring Xen and XCP -------------------------- 4.1/ Switch using xl instead of xm and xend to control Xen As of writing, you should do that: sed -i "s/TOOLSTACK=/TOOLSTACK=xl/" /etc/default/xen Where as the init script checks for: # Exit cleanly if TOOLSTACK != xapi if [ "${TOOLSTACK}" !=

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Function wait_for_xapi in /etc/init.d/xcp-xapi does not work as intented. Symptoms: (on slave) /etc/init.d/xcp-xapi restart [....] Restarting The XenAPI server: xapiThe host toolstack is still initialising. Please wait. Cause: Line 'xe pif-scan host-uuid=${INSTALLATION_UUID}' called before xapi is fully synced with master.

Control: tag -1 +patch commit 717323e8f7398d45f8dc923a20a75baa7333adf1 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 16:39:11 2013 +0100 * debian/xen-utils.README.Debian: Document how to change toolstack * debian/changelog: Update diff --git a/xen/debian/changelog b/xen/debian/changelog index 6100e75..9426897 100644 --- a/xen/debian/changelog +++

Package: xcp-xapi Version: 1.3.2-6 Severity: important Looks like on Wheezy, /etc/default/xen is not created by xen-utils-common. Since xcp-xapi depends on its existence and further declaration of the toolstack in it, it should take extra care to ensure that it is present. root at debian:~# aptitude install xcp-xapi The following NEW packages will be installed: blktap-dkms{a} blktap-utils{a}

Processing commands for control at bugs.debian.org: > reassign #680528 xen-utils-common Bug #680528 [xcp-xapi] xcp-xapi: /etc/init.d/xendomains cause xapi to hand during boot Bug reassigned from package 'xcp-xapi' to 'xen-utils-common'. No longer marked as found in versions xen-api/1.3.2-8. Ignoring request to alter fixed versions of bug #680528 to the same values previously

Package: xcp-xapi Version: 1.3.2-6 Severity: important Configuration: Two xcp-xapi hosts (default sid/xcp-xapi installation) in single pool. Network backend is bridge. After migration of 'idle' (doning nothing) virtual machine it stops to reply to ping for long time. AFAIK that caused by mac-learning table on upper level (hardware) switch, which route all frames to wrong port

libxenapi-ocaml-dev_1.3.2-2_amd64.deb to main/x/xen-api/libxenapi-ocaml-dev_1.3.2-2_amd64.deb python-xenapi_1.3.2-2_all.deb to main/x/xen-api/python-xenapi_1.3.2-2_all.deb (new) xcp-networkd_1.3.2-2_amd64.deb extra admin daemon to manage network configuration for xcp-xapi The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, with

Package: xcp-xapi Version: 1.3.2-6 Severity: normal After some time of rebooting and toolstack restart found very funny output in 'xe pif-lis': xe pif-list params=currently-attached,device device ( RO) : vif2.0 currently-attached ( RO): false device ( RO) : vif211.0 currently-attached ( RO): false device ( RO) : eth1

Package: xcp-xapi Version: 1.3.2-9 Severity: grave Justification: renders package unusable I've following mostly the xcp-xapi/README.Debian instructions after installing it with apt-get -t wheezy network.conf is configured for bridge, xenbrN are functioning and shown with xe network-list A single SR is present, created with ext on a local LVM. For debugging purposes, all ISO and local ISO

hi all, i meet a big problem, when i finish install xcp-xapi on ubuntu 12.04, i set grub to go into xen 4.1 kernel when startup and set echo ''TOOLSTACK="xapi"'' > /etc/default/xen when i reboot and login to the system , i got a lot out of memory error and all process be killed, seem like kernel crash. can anyone help me about that ? thanks.

Thanks Jon, it worked, I was able to build all the packages for xenserver on CentOS 6.6 final version. Here is the package list: https://gist.github.com/gautammaloo/7616cccbe8f5c85c196e I was wondering what packages would be necessary to use Xen with xapi, I already have xen with xl installed. Could we have a package like http://packages.ubuntu.com/precise/xcp-xe with which we can have

One of the cluster nodes (XS 5.6 SP2/not master) became unresponsive to XAPI calls being sent from a CloudStack management server. In the past, a simple xe-toolstack-restart would do the trick but the script timed out while restarting the XAPI daemon. I found the process and first tried to use a simple kill command but the process was in a "defunct" state. I tried a kill -9 but no joy.

Waldi, There's a few things I'm intending to look at for the Xen packaging in Jessie, which I thought it might be useful to share with you. If there's anything on this list you explicitly do not want done please let me know so I don't waste my time, likewise if there are any which you intend to work on yourself. Otherwise I shall tackle these as and when I get a chance and post