similar to: Processed: Retitle and reassign "xcp-xapi fails to start" to xen-utils-common as "xend shouldn't start if TOOLSTACK is not xm"

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-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-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-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 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-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: > retitle 674137 Please make bind port configurable Bug #674137 [xcp-xapi] xcp-xapi: default ports in xapi Changed Bug title to 'Please make bind port configurable' from 'xcp-xapi: default ports in xapi' > severity 674137 wishlist Bug #674137 [xcp-xapi] Please make bind port configurable Ignoring request to change severity

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:

On 12/22/2011 01:37 AM, Mike McClurg wrote: > Hi Thomas, Jon, > > I was hoping that you could both comment on this github pull request: > > https://github.com/jonludlam/xen-api/pull/12 > > Mike > In Debian, /etc/default/xen is there to select xm vs xl. So we could do: if ! [ -f /etc/default/xen ] ; then TOOLSTACK=xm else . /etc/default/xen if ! [

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.

Package: xcp-xapi Version: 1.3-15 Severity: normal My packages were initially installed from the deb repository at download.xensource.org. Eventually, I upgraded them to the debian repository ones. Right now, xcp-xapi fails to start with the following messages. lnx200-39:~# /etc/init.d/xcp-xapi start Error: Connection refused (calling connect ) lnx200-39:~# -- System Information: Debian

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

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

On 10/26/2011 05:29 AM, Mike McClurg wrote: > Perhaps you could send us a private deb file to test? I'm worried that > this might not be the right version that we need. Can you point us at > the upstream code you used? I used what was in the Git at: http://github.com/jonludlam/blktap.git The clone was made about a month ago, and it would be hard for me to tell when exactly. Adding

Processing commands for control at bugs.debian.org: > reassign 677614 xen-utils-common 4.1.2-6 Bug #677614 [xcp-xapi] xcp-xapi: someone should create /etc/default/xen Bug reassigned from package 'xcp-xapi' to 'xen-utils-common'. No longer marked as found in versions xen-api/1.3.2-6. No longer marked as fixed in versions 4.1.2-7. Bug #677614 [xen-utils-common] xcp-xapi: someone

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 +++

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

Processing commands for control at bugs.debian.org: > reassign 677614 xen-utils-common/4.1.2-6 Unknown command or malformed arguments to command. > fixed 677614 4.1.2-7 Bug #677614 [xcp-xapi] xcp-xapi: someone should create /etc/default/xen There is no source info for the package 'xcp-xapi' at version '4.1.2-7' with architecture '' Unable to make a source version

Hello, I installed the last version of Xen (xenserver-core-0.9.0-9.x86_64 from yum) and I'm trying to manage my VMs with virsh. The version that I installed is using the Xapi/xe toolstack. The problem I have is that I'm not seeing the VM that is started with "virsh -c xen:/// list --all". Here is what I have: root# xe vm-list uuid ( RO) :