similar to: Bug#677614: xcp-xapi: someone should create /etc/default/xen

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Tue, 23 Oct 2012 10:23:57 +0000 Source: blktap Binary: blktap-dev blktap-utils libvhd0 libvhdio-2.0.90 libblktapctl0 Architecture: source amd64 Version: 2.0.90-2 Distribution: unstable Urgency: low Maintainer: PKG Xen Devel <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Thomas Goirand <zigo at

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 05 Sep 2014 10:36:52 +0300 Source: blktap Binary: blktap-dev blktap-utils libvhd0 libvhdio-2.0.90 libblktapctl0 Architecture: source amd64 Version: 2.0.90-3 Distribution: unstable Urgency: high Maintainer: PKG Xen Devel <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Nanakos Chrysostomos <nanakos at

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 30 Jun 2015 12:28:20 +0300 Source: blktap Binary: blktap-dev blktap-utils libvhd0 libvhdio-2.0.90 libblktapctl0 Architecture: source Version: 2.0.90-4 Distribution: unstable Urgency: medium Maintainer: PKG Xen Devel <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Chrysostomos Nanakos <cnanakos at

Package: blktap-utils Version: 2.0.90-2 Severity: important Tapdisk fails to start and exit's silently after failing to detect current kernel version. This happens only on newer kernel versions missing sublevel field. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP

Package: blktap-utils Version: 2.0.90-3 Severity: normal Dear Maintainer, Man pages for blktap-utils are effectively stubs, with no useful content whatsoever. It would have been better to just leave them out (even if lintian and/or ftpmaster would have complained) Will try to follow up with newly-created manpages. Thanks -- System Information: Debian Release: 8.1 APT prefers testing APT

Package: blktap-dev Version: 2.0.90-2 Severity: normal blktap-dev does not pull in uuid-dev which results in the following error when including vhd/libvhd.h: /usr/include/vhd/libvhd.h:37:23: fatal error: uuid/uuid.h: No such file or directory #include <uuid/uuid.h> ^ compilation terminated. Installing uuid-dev fixes the problem, but it seems that blktap-dev should

Package: xcp-xapi Version: 1.3-16 Severity: normal Tags: patch Dear Maintainer, Path to "xe" program in /usr/lib/xcp/bin/xe-mount-iso-sr should be: XE="/usr/bin/xe" HTH, David -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores)

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream If xe pif-configure-ip called twice with different IP, it did not remove old IP from interface (but didn't store both addresses in database). (Checked for management interface) Steps to reproduce: xe pif-reconfigure-ip uuid=... ip=IP1 .... xe pif-reconfigure-ip uuid=(same) ip=IP2 ... 'ip addr show' shows both

Package: xcp-xapi Version: 1.3.2-6 Severity: minor Tags: upstream Builin utility for lowlevel vm boot repairment xe-edit-bootloader contains wrong path to xe. IS: XE="/usr/lib/xcp/bin/xe" MUST BE: XE="/usr/bin/xe" -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux

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-6 Severity: important Tags: upstream xe vm-memory-target-set does not write new target to /local/domain/ID/memory/target. Balloon in guest domain is expecting this value to be changed to do selfballooning. This breaks 'dynamic memory control' feature. Steps to reproduce: 1) Setup any PV virtual machine with static-memory-min < static-memory-max 2)

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-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-7 Severity: normal xcp-xapi fails to eject host from pool with following error: xe pool-eject host-uuid=a6806a39-442d-f17d-b7a0-59161d18f56f WARNING: Ejecting a host from the pool will reinitialise that host's local SRs. WARNING: Any data contained with the local SRs will be lost. Type 'yes' to continue yes The server failed to handle your request,

Package: xcp-xapi Version: 1.3.2-11 Severity: normal xe host-set-hostname-live host-uuid=68878163-7c93-17af-7911-5a2726fefc66 host-name=xapi-xh3 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Subprocess exitted with unexpected code 2; stdout = [ ]; stderr = [ sed: can't read

Package: xcp-xapi Version: 1.3-15 Severity: wishlist The current initscript has the possibility of slowing down the boot process by 50 seconds. If this is required, it probably should be backgrounded. # Wait for xapi to write its "init complete" cookie: after here it's safe to modify templates. wait_for_xapi() { MAX_RETRIES=50 RETRY=0 while [ ${RETRY} -lt ${MAX_RETRIES}

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-11 Severity: normal We need to have a separate user/group privilege for xapi and its dependent processes. At the moment, everything runs as root -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux

Package: xcp-xapi Version: 1.3-15 Severity: normal By default, xapi listens on the loopback interface. To make it available over the network, its inventory needs to be updated with the bridged interface details. For example, if xenbr0 is the bridged interface, it needs to be set it: lnx200-39:~# cat /etc/xcp/inventory BUILD_NUMBER='0' CURRENT_INTERFACES='xenbr0'

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