similar to: Processed: reassign 702338 openxenmanager

Package: xcp-xe Version: 1.3.2-14 Severity: important I created an internal network using xe network-create name-label='Private NAT network' Looking with brctl, I could see xapi0 had been created by the tools. However, the network does not appear in openxenmanager. I even restarted openxenmanager, it still didn't appear. Then I deleted the network and created it again from

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

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

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: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 399073 src:xen 3.0.3-0-2 Bug #399073 [xen-hypervisor-3.0.3-1-i386] xen-hypervisor-3.0.3-1-i386: dom0 crashes with a domU that define more than 6 vdb Warning: Unknown package 'xen-hypervisor-3.0.3-1-i386' Bug

Processing commands for control at bugs.debian.org: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 514918 src:xen 3.3-unstable+hg17961-1 Bug #514918 [xen-utils-unstable] xen-utils-unstable: xend starts with errors Warning: Unknown package 'xen-utils-unstable' Bug reassigned from package

Processing commands for control at bugs.debian.org: > reassign 745419 src:xen 4.1.4-3+deb7u1 Bug #745419 [xen-utils-4.1] xen-utils-4.1: Pygrub fails to boot from LVM LV when something installed in the volume boot record Bug reassigned from package 'xen-utils-4.1' to 'src:xen'. No longer marked as found in versions xen/4.1.4-3+deb7u1. Ignoring request to alter fixed versions of

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

Hi, After reading XenServer documents and debugging, I found the previous configuration is correct, here is the one I've configured to work: In XCP, as in XenServer, system's network configuration doesn't really matter, it only make sense before XCP starts and handles the network settings. So there is no need to configure VLAN on host machine, and you only need a minimal one active

Processing commands for control at bugs.debian.org: > reassign 804993 libjs-pie-doc 1.0.0+dfsg-1 Bug #804993 {Done: Michael Fladischer <fladi at debian.org>} [libjs-pie-doc,python-django-classy-tags-doc] python-django-classy-tags-doc and libjs-pie-doc: error when trying to install together Bug reassigned from package 'libjs-pie-doc,python-django-classy-tags-doc' to

Thanks for all the help... XVP seems quite high on requirements. Like it needs an SMTP server set up. I''m not sure I like that. I found a tool called BixData, it''s proprietary but with a free license for a limited number of managed servers. Being a fully fledged cloud management system, it''s true overkill for me and my 3-4 virtual machines, but at least it seems quite

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream /usr/lib/xcp/bin/xe-edit-bootloader failing with following message: /usr/lib/xcp/bin/xe-edit-bootloader -u 19f66083-e776-70d1-1808-3712688ad138 Creating dom0 VBD: 0fdb952e-92ff-4b53-dd49-8d54b2268787 Plugging VBD: Waiting for /dev/sm/backend/4c15ea03-5d70-938e-8265-d5424c0fda5e/963afb9a-9ceb-410f-8554-8be9fb70e7e0: . done

Processing commands for control at bugs.debian.org: > merge 697407 697409 697412 697417 Bug #697407 [xen-utils-4.1] xen-utils-4.1: pygrub doesn't find extlinux.conf in default Debian location Bug #697409 [xen-utils-4.1] xen-utils-4.1: pygrub does not correctly distinguish between "disk with partitions" and "partition" Bug #697412 [xen-utils-4.1] xen-utils-4.1: pygrub

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

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: > reopen 678923 Bug #678923 {Done: George Shuklin <george.shuklin at gmail.com>} [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever Bug reopened Ignoring request to alter fixed versions of bug #678923 to the same values previously set > End of message, stopping processing here. Please contact me if you need

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 808624 src:xen 4.4.1-9+deb8u3 Bug #808624 [xen-hypervisor-4.4-amd64] Invalid argument while starting daemon Bug reassigned from package 'xen-hypervisor-4.4-amd64' to 'src:xen'. Ignoring request to alter found versions of bug #808624 to the same values previously set Ignoring request to alter fixed versions of bug

Processing commands for control at bugs.debian.org: > reassign 583155 logcheck Bug #583155 {Done: Hannes von Haugwitz <hannes at vonhaugwitz.com>} [amavisd-new] logcheck-database: Please create rules for amavis(d-new) Bug #590965 {Done: Hannes von Haugwitz <hannes at vonhaugwitz.com>} [amavisd-new] amavisd-new: Please reprovide logcheck rules Bug reassigned from package

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