similar to: XCP pool upgrade

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 there, I am trying to set up XCP on Ubuntu 12.04. I went through the procedure given in the README file of the xcp-xapi package and reached the point where the hypervisor seems to be running fine. I set up a VM using the Debian Squeeze (64bit) template and started it, giving a Debian mirror URL as install-repository. Running "xe vm-list" reports that the machine is running, but when

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-15 Severity: normal By default, xapi listens on the loopback interface. To make it available over the network, its inventory needs to be updated with the bridged interface details. For example, if xenbr0 is the bridged interface, it needs to be set it: lnx200-39:~# cat /etc/xcp/inventory BUILD_NUMBER='0' CURRENT_INTERFACES='xenbr0'

Package: xcp-xapi Version: 1.3.2-11 Severity: normal We need to have a separate user/group privilege for xapi and its dependent processes. At the moment, everything runs as root -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux

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-15 Severity: normal My packages were initially installed from the deb repository at download.xensource.org. Eventually, I upgraded them to the debian repository ones. Right now, xcp-xapi fails to start with the following messages. lnx200-39:~# /etc/init.d/xcp-xapi start Error: Connection refused (calling connect ) lnx200-39:~# -- System Information: Debian

Package: xcp-xapi Version: 1.3-15 Severity: wishlist The current initscript has the possibility of slowing down the boot process by 50 seconds. If this is required, it probably should be backgrounded. # Wait for xapi to write its "init complete" cookie: after here it's safe to modify templates. wait_for_xapi() { MAX_RETRIES=50 RETRY=0 while [ ${RETRY} -lt ${MAX_RETRIES}

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-squeezed Version: 1.3.2-9 Severity: important When trying to start a guest I get: # xe vm-start name-label=squeeze-2 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Failure("The ballooning daemon is not running") If I then manually run "/etc/init.d/xcp-squeezed

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

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

Hello there, i am trying to create a VM using xcp on my system, with os Ubuntu 11.10. I’ve got 3 server on my testbed and in the near future i am going to try a VM live migration from a server to another, but actually I am having few problems.  The first one : i installed the xcp-xapi on 2 of my servers, and when i give the command #xe template-list One of the server gives me the list, while the

Package: xcp-xapi Version: 1.3.2-13 Severity: critical I get this bug when installing XCP and configuring the network portion of it. When I issue the following command: xe pif-reconfigure-ip uuid=$PIF_UUID mode=static IP=10.0.0.10 netmask=255.255.255.240 gateway=10.0.0.1 DNS=10.5.1.2,10.5.1.3 My network interface looks like this (Broken): eth2 Link encap:Ethernet HWaddr 00:50:ec:24:c7:43

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

Dear all, How to make XCP cannot management by XenCenter? We have an environment about 10 XCP host, and provide about 50 vm for users, We notice that some users want to use XenCenter to connect the XCP host, even they don’t have password, so we want to make XCP cannot use XenCenter and only for console management, is it possible? Sorry for the strange question,

Package: xcp-xapi Severity: important The README doc mentions: 4/ Configuring Xen and XCP -------------------------- 4.1/ Switch using xl instead of xm and xend to control Xen As of writing, you should do that: sed -i "s/TOOLSTACK=/TOOLSTACK=xl/" /etc/default/xen Where as the init script checks for: # Exit cleanly if TOOLSTACK != xapi if [ "${TOOLSTACK}" !=

Package: xcp-xapi Version: 1.3.2-8 Severity: important During startup /etc/init.d/xendomains script is called. That script is installed with xen-utils-common witch xcp-xapi is depends on. That script calls /usr/sbin/xen as xen list &> /dev/null This 'xen' seems to call xapi: xen list ^Z [1]+ Stopped xen list root at lab-xh3:~# ps f PID TTY STAT TIME

Hi there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being