similar to: Processed (with 5 errors): Lowering severity

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}

Package: xcp-xapi Version: 1.3.2-14 Severity: important I chose the Open vSwitch (ovs) networking mode when I installed XCP # cat /etc/xcp/network.conf openvswitch Whenever I boot a VM, I notice that the vif interface is created (e.g. vif1.0) on dom0, and the vif is added to the ovs bridge (I can see it in the output of ovs-vsctl show) However, there is no connectivity, I can't ping the

Dear Debian maintainer, On Thursday, March 15, 2012, I sent you a notification about the beginning of a review action on debconf templates for xen-api. Then, I sent you a bug report with rewritten templates and announcing the beginning of the second phase of this action: call for translation updates. Translators have been working hard and here is now the result of their efforts. Please

libxenapi-ocaml-dev_1.3.2-2_amd64.deb to main/x/xen-api/libxenapi-ocaml-dev_1.3.2-2_amd64.deb python-xenapi_1.3.2-2_all.deb to main/x/xen-api/python-xenapi_1.3.2-2_all.deb (new) xcp-networkd_1.3.2-2_amd64.deb extra admin daemon to manage network configuration for xcp-xapi The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, with

Processing commands for control at bugs.debian.org: > severity 702337 serious Bug #702337 [xcp-xapi] xen-xapi / Open vSwitch not really working Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 702337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702337 Debian Bug Tracking System Contact owner at

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 674137 Please make bind port configurable Bug #674137 [xcp-xapi] xcp-xapi: default ports in xapi Changed Bug title to 'Please make bind port configurable' from 'xcp-xapi: default ports in xapi' > severity 674137 wishlist Bug #674137 [xcp-xapi] Please make bind port configurable Ignoring request to change severity

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

Accepted: libxenapi-ocaml-dev_1.3.2-9_amd64.deb to main/x/xen-api/libxenapi-ocaml-dev_1.3.2-9_amd64.deb python-xenapi_1.3.2-9_all.deb to main/x/xen-api/python-xenapi_1.3.2-9_all.deb xcp-networkd_1.3.2-9_amd64.deb to main/x/xen-api/xcp-networkd_1.3.2-9_amd64.deb xcp-squeezed_1.3.2-9_amd64.deb to main/x/xen-api/xcp-squeezed_1.3.2-9_amd64.deb xcp-v6d_1.3.2-9_amd64.deb to

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

Processing commands for control at bugs.debian.org: > severity #674137 wishlist Bug #674137 [xcp-xapi] xcp-xapi: default ports in xapi Severity set to 'wishlist' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 674137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674137 Debian Bug Tracking System Contact owner at

Package: xcp-networkd Version: 1.3.2-11 Severity: normal Given that openvswitch is one of the networking modes, it should be in the Recommends: than being in the Depends: -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64

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: > severity 655303 wishlist Bug #655303 [xcp-xapi] xcp-xapi: document network configuration in README.Debian Severity set to 'wishlist' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 655303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655303 Debian Bug Tracking

Processing commands for control at bugs.debian.org: > severity 682979 normal Bug #682979 [xcp-xapi] xcp-xapi: VM not starting, tasks not cancellable Severity set to 'normal' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 682979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682979 Debian Bug Tracking System Contact

Hi I install the xcp from the http://wiki.xen.org/wiki/XAPI_on_Ubuntu. But I got this error while configuring xcp-xapi: xcp-networkd (1.3.2-1ubuntu1~oneiric1) wird eingerichtet ... Starting the XCP networking daemon: .............................. * failed to start xcp-networkd. invoke-rc.d: initscript xcp-networkd, action "start" failed. when I comment the

Processing commands for control at bugs.debian.org: > severity 675052 normal Bug #675052 [xcp-xapi] xcp-xapi: xe vm-memory-target-set does not write target to xenstore Severity set to 'normal' from 'important' > severity 678923 normal Bug #678923 [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever Severity set to 'normal' from

It appears that this issue may be a result of documentation problems When I was having this problem, I had xenbr0 declared in my /etc/network/interfaces file. I have now stripped out everything in the interfaces file except the loopback interface, rebooted, and now my xcp+openvswitch system appears to be adding domUs to the bridge automatically, so the problem is no longer there. Specifically,

Package: xcp-xapi Version: 1.3.2-15 Severity: important New wheezy box Follow the setup instructions for xcp-xapi, choosing openvswitch networking Only loopback is defined in /etc/network/interfaces (the way it should be for XCP) IP address, router, DNS has been configured statically with pif-reconfigure-ip After reboot, the IP address is assigned correctly on the bridge interface but some

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