similar to: changing bandwidth in XCP.

Hi all! I am using XCP pool with 5 members. XCp version is 1.0.0 I want to upgrade my XCP to version XCp 1.1. I read that upgrading from 0.0.1 to 0.5 had some troubles including conflicts between different version of XCP (XCP 0.0.1 and XCP 0.5 conlicted each other in one pool). Does anybody did such upgrade? What troubles can I meet? :) _______________________________________________ Xen-users

As seen on the mailinglist, many have been hit by the issues with the igb driver included in xcp 1.1 and below ( and 5.6 fp* and below as well ), version 2.4.3, which due to a bug prevents VLAN tagging and other features from working correct (sr-iov). This mainly affects systems with Intel 82576 nics. There are work arounds for this, mainly updating the driver from intel, see here:

I knew it couldn''t possibly go right. First attempt at upgrading a 0.1.0 host trashed the networking config majorly. In defense of 0.1.1, I did have an odd networking config (since XCP had problems with the built in Broadcom ports, I pif-forgetted them and let Linux handle them. If it weren''t for the mutant network config, I bet 0.1.1 would have done ok. More seriously,

Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log:

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,

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

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sun, 04 Nov 2012 18:54:52 +0000 Source: xcp-storage-managers Binary: xcp-storage-managers Architecture: source amd64 Version: 0.1.1-3 Distribution: unstable Urgency: low Maintainer: PKG-Xen Devel <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Thomas Goirand <zigo at debian.org> Description:

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 05 Jul 2013 01:52:39 +0200 Source: xcp-vncterm Binary: xcp-vncterm Architecture: source amd64 Version: 0.1-2.1 Distribution: unstable Urgency: low Maintainer: PKG-Xen Devel <pkg-xen-devel at lists.alioth.debian.org> Changed-By: Sebastian Ramacher <sramacher at debian.org> Description: xcp-vncterm -

Package: xcp-storage-managers Version: 0.1.1-3 Severity: normal This was already reported in the archived bug 691805 but I sent an e-mail and I received back permanent delivery failure because this bugs has been archieved. Still the path of "pidof" in the file /usr/lib/xcp/sm/iscsilib.py is wrong on Wheezy. It should be /bin/pidof instead of /sbin/pidof root at xcpcompute2:~# cat

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-networkd Version: 1.3.2-2 Severity: serious User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package

I have a couple of questions regarding XCP: First, there were rumblings that there are issues upgrading XCP (1.5 -> 1.6)? Any further detail on these potential issues, or what needs to be done to get around them? Second, it previous versions of XCP there were tricks that had to be played (documented on the Wiki) to make XenCenter believe that XCP was actually a modern version of XenServer,

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

(new) xcp-storage-managers_0.1.1-2.debian.tar.gz extra libs (new) xcp-storage-managers_0.1.1-2.dsc extra libs (new) xcp-storage-managers_0.1.1-2_amd64.deb extra libs storage backends for XCP 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. .

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