similar to: Bug#680102: xcp-xapi: xcp fails eject host from pool (no /etc/firstboot.d found)

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:

Package: xcp-xapi Version: 1.3.2-8 Severity: minor During upgrade from 1.3.2-7 to 1.3.2-8 got follwing message on slave host (upgrade was simulatanious on slave and master): ... Setting up xcp-xapi (1.3.2-8) ... The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: INTERNAL_ERROR: [

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

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.

Accepted: libxen-4.1_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/libxen-4.1_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb libxen-dev_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to main/x/xen/libxen-dev_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb libxen-ocaml-dev_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1_amd64.deb to

Processing commands for control at bugs.debian.org: > close 680479 4.1.3~rc1+hg-20120614.a9c0a89c08f2-1 Bug #680479 [xen-utils-4.0] xen-utils-4.0: pygrub does not support grub2 submenus There is no source info for the package 'xen-utils-4.0' at version '4.1.3~rc1+hg-20120614.a9c0a89c08f2-1' with architecture '' Unable to make a source version for version

Processing commands for control at bugs.debian.org: > close 609689 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 Bug #609689 [xen-utils-4.0] xen-utils-4.0: Missing xentrace_format python script in /usr/lib/xen-4.0/bin/ There is no source info for the package 'xen-utils-4.0' at version '4.1.3~rc1+hg-20120614.a9c0a89c08f2-2' with architecture '' Unable to make a source version for

FYI: The status of the xen source package in Debian's testing distribution has changed. Previous version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 Current version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See

FYI: The status of the xen source package in Debian's testing distribution has changed. Previous version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4 Current version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See

Processing commands for control at bugs.debian.org: > close 391606 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 Bug #391606 [xen-utils-common] xen-utils-common: doesn't ship referenced man pages Marked as fixed in versions xen/4.1.3~rc1+hg-20120614.a9c0a89c08f2-2. Bug #391606 [xen-utils-common] xen-utils-common: doesn't ship referenced man pages Marked Bug as done > thanks Stopping

Processing commands for control at bugs.debian.org: > close 407299 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 Bug #407299 [xen-utils-common] xen-utils-common: man 1 xm: warning: can't find numbered character 160 Marked as fixed in versions xen/4.1.3~rc1+hg-20120614.a9c0a89c08f2-2. Bug #407299 [xen-utils-common] xen-utils-common: man 1 xm: warning: can't find numbered character 160 Marked Bug

Processing commands for control at bugs.debian.org: > reassign 444000 src:xen 4.1.3~rc1+hg-20120614.a9c0a89c08f2-4 Bug #444000 [xen-3] Wrong path for dump files Warning: Unknown package 'xen-3' Bug reassigned from package 'xen-3' to 'src:xen'. No longer marked as found in versions 3.1-2. Ignoring request to alter fixed versions of bug #444000 to the same values

Subject: xen-utils-4.1: /usr/lib/xen-default missing Package: xen-utils-4.1 Version: 4.1.3-1 Severity: important Dear Maintainer, when using paravirtualization with xen and libvirt the path for pygrub is: /usr/lib/xen-default/bin/pygrub But this path is not provided with xen-utils-4.1 and will brake upgrades to wheezy. With xen-utils-4.0 and debian squeeze this path is provided with

tags 671018 +patch thanks This issue has been fixed upstream for 4.2 by using the same hotplug scripts for tap devices as for vif devices rather than using a special qemu-ifup script. I don't think this is an appropriate thing to backport to 4.1 for wheezy so therefore I think the right fix is as Pierre suggests to set the MAC address in the qemu-ifup script. In terms of a patch to the

FYI: The status of the xen source package in Debian's testing distribution has changed. Previous version: 4.1.2-6 Current version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See

(CC'ing George Shulkin, and the #680102 bug list) On Sat, Jul 7, 2012 at 4:37 PM, Thomas Goirand <thomas at goirand.fr> wrote: > Hi Mike and Jon, > > It would be really nice if you could have a look at these 3 pending > issues in the Debian bug tracker: > > #675052: xe vm-memory-target-set does not write target to xenstore > #678723: vif-interfaces added to database

Package: xcp-xapi Version: 1.3.2-6 Severity: important I done normal reboot: xe host-disable host=this_host xe host-reboot host=this_host After reboot host stays in 'disable' state and when I've tried to make it enable I got: xe host-enable uuid=ab523ee3-0546-5400-e2db-32f340292fff The specified host is disabled and cannot be re-enabled until after it has rebooted. host:

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-5 Severity: important I updated from xen-hypervisor-4.0-amd64 to xen-hypervisor-4.1-amd64 and the system did not boot anymore (Xen panic). A downgrade made the system work again. I cannot paste the boot error messages but the main message was: Xen BUG at pci_amd_iommu.c:33 The bug appears for Linux images 3.2.0.2