similar to: Processed: reassign 677614 to xen-utils-common, fixed 677614 in 4.1.2-7

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

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

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 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: > # Automatically generated email from bts, devscripts version 2.9.26 > package xen-utils-common Ignoring bugs not assigned to: xen-utils-common > reassign 489323 xen-3 Bug#489323: [xen-utils-common] XenAPI authentification needs python-pam to work Bug reassigned from package `xen-utils-common' to `xen-3'. > reassign 489325

Processing commands for control at bugs.debian.org: > reassign 702338 openxenmanager Bug #702338 [xcp-xe] can't create network from xe command line Bug reassigned from package 'xcp-xe' to 'openxenmanager'. No longer marked as found in versions xen-api/1.3.2-14. Ignoring request to alter fixed versions of bug #702338 to the same values previously set > End of message,

Processing commands for control at bugs.debian.org: > reassign 555902 xen-utils-common 3.3.1-2 Bug #555902 {Done: Bastian Blank <waldi at debian.org>} [xen-utils-3.4] xen-utils-3.4: /etc/init.d/xend - $DAEMON variable at xend_stop() Bug reassigned from package 'xen-utils-3.4' to 'xen-utils-common'. Bug No longer marked as found in versions xen-3/3.4.0-2. Bug No longer

Processing commands for control at bugs.debian.org: > reassign 628912 xen-utils-common 4.0.1-2 Bug #628912 [xen-utils-4.0] xenconsoled and xenstored stopping unhandled by init script Bug reassigned from package 'xen-utils-4.0' to 'xen-utils-common'. No longer marked as found in versions xen/4.0.1-2. Ignoring request to alter fixed versions of bug #628912 to the same values

Processing commands for control at bugs.debian.org: > reassign 596765 xen-utils-common Bug #596765 [xen] xen: can't create a VM : no module named xmlproc Bug reassigned from package 'xen' to 'xen-utils-common'. No longer marked as found in versions xen/4.0.1-2 and xen/4.0.1-1. Ignoring request to alter fixed versions of bug #596765 to the same values previously set >

Processing commands for control at bugs.debian.org: > reassign 489325 xen-utils-common Bug #489325 [xen-3] [xen-utils-common] xm new requires python-xml to work Warning: Unknown package 'xen-3' Bug reassigned from package 'xen-3' to 'xen-utils-common'. Ignoring request to alter found versions of bug #489325 to the same values previously set Ignoring request to alter

Processing commands for control at bugs.debian.org: > reassign 489323 xen-utils-common Bug #489323 [xen-3] [xen-utils-common] XenAPI authentification needs python-pam to work Warning: Unknown package 'xen-3' Bug reassigned from package 'xen-3' to 'xen-utils-common'. Ignoring request to alter found versions of bug #489323 to the same values previously set Ignoring

Processing commands for control at bugs.debian.org: > reassign 709103 xen-utils-common 4.1.4-3+deb7u1 Bug #709103 [xen-linux-system-amd64] xen-linux-system-amd64: Xen installation FAILS from Debian repository Bug reassigned from package 'xen-linux-system-amd64' to 'xen-utils-common'. No longer marked as found in versions linux-latest/46. Ignoring request to alter fixed versions

Processing commands for control at bugs.debian.org: > reassign 711273 xen-utils-common Bug #711273 [xen-hypervisor-4.2-amd64] xen-hypervisor-4.2-amd64: Acn't re-create domains after migration from 4.1 to 4.2 Bug reassigned from package 'xen-hypervisor-4.2-amd64' to 'xen-utils-common'. No longer marked as found in versions xen/4.2.1-2. Ignoring request to alter fixed

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: 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-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 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: 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: 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: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream Normally (in 'iso-based' XCP) is possible to attach VDI to dom0. That operation usually looks like: xe vbd-create vdi-uuid=... vm-uuid=(dom0 uuid) device=N xe vbd-plug I done those steps in xcp-xapi and got success (no error), but no xvd* device found. Here operations log: # xe vbd-create