similar to: xcp-eliloader REMOVED from testing

FYI: The status of the xcp-storage-managers source package in Debian's testing distribution has changed. Previous version: 0.1.1-3.1 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the

FYI: The status of the xcp-vncterm source package in Debian's testing distribution has changed. Previous version: 0.1-2.1 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for

FYI: The status of the xcp-eliloader source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.1-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 http://release.debian.org/testing-watch/ for

FYI: The status of the xen-api-libs source package in Debian's testing distribution has changed. Previous version: 0.5.2-3.1 Current version: (not in testing) Hint: <http://release.debian.org/britney/hints/mehdi> # 10-12-2013; generated with comigrate -c /srv/release.debian.org/britney/code/b2/britney.conf --migrate ocaml --remove xen-api-libs --remove otags --remove

FYI: The status of the guest-templates source package in Debian's testing distribution has changed. Previous version: 0.1-4 Current version: (not in testing) Hint: <http://release.debian.org/britney/hints/jcristau> # 20130926; done 20130927 The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not

FYI: The status of the xen-api source package in Debian's testing distribution has changed. Previous version: 1.3.2-15 Current version: (not in testing) Hint: <http://release.debian.org/britney/hints/jcristau> # 20130926; done 20130927 The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not

FYI: The status of the xen-unstable source package in Debian's testing distribution has changed. Previous version: 3.0-unstable+hg11561-1 Current version: (not in testing) Hint: <http://ftp-master.debian.org/testing/hints/luk> Bug #395332: xen-unstable - not suitable for a release The script that generates this mail tries to extract removal reasons from comments in the

FYI: The status of the xen-3.0 source package in Debian's testing distribution has changed. Previous version: 3.0.4-1-1 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for

FYI: The status of the xen-3 source package in Debian's testing distribution has changed. Previous version: 3.4.3-1 Current version: (not in testing) Hint: Package not in unstable The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for removing

FYI: The status of the xen-common source package in Debian's testing distribution has changed. Previous version: 4.1.2-1 Current version: (not in testing) Hint: (no removal hint found) The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for

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}

(new) xcp-eliloader_0.1-4.debian.tar.gz extra admin (new) xcp-eliloader_0.1-4.dsc extra admin (new) xcp-eliloader_0.1-4_all.deb extra admin XenAPI's bootloader for EL-based guests The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, with support for a range of guest operating systems, Linux network and storage support. . XCP

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