similar to: XCP installing debian woes

I have just run into the following error when trying to create a debian lenny vm in XCP 0.5.0 from the command line. This used to work in 0.1.1 as far as I can remember. Here is what I did: [root@xcp1 ~]# UUID=`xe vm-install template="Debian Lenny 5.0 (32-bit)" new-name-label=lenny-test-1` VIF=`xe vif-create network-uuid=0c94af8b-da04-5417-cdd6-f4c6236aea8b vm-uuid=$UUID device=0` xe

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-11 Severity: normal xe host-set-hostname-live host-uuid=68878163-7c93-17af-7911-5a2726fefc66 host-name=xapi-xh3 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Subprocess exitted with unexpected code 2; stdout = [ ]; stderr = [ sed: can't read

Package: xcp-storage-managers Version: 0.1.1-3 Severity: normal XCP cannot use iscsi block devices. Fails with iscsiadm: No active sessions. I ran the following commands trying to diagnose the problem: First introducing a SR and then creating a PBD with the needed configuration for the iscsi block device. These steps work fine but when I tried to plug the PBD I got the error: root at

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-9 Severity: grave Justification: renders package unusable I've following mostly the xcp-xapi/README.Debian instructions after installing it with apt-get -t wheezy network.conf is configured for bridge, xenbrN are functioning and shown with xe network-list A single SR is present, created with ext on a local LVM. For debugging purposes, all ISO and local ISO

Hi. I executed the following steps to instal a Debina Lenny Vm (as the manual describe): 1)- xe vm-install template="Debian Lenny 5.0 (32-bit)" new-name-label=vmlenny_1 UUID = dd29fd58-9ed2-0d53-5a71-dea5bf0d613b 2)- xe vm-param-set uuid=dd29fd58-9ed2-0d53-5a71-dea5bf0d613b other-config:install-repository=http://ftp.br.debian.org/debian 3)- xe vm-start

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

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream vbd plug to PV domain cause following error: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760)) (same error

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

Hello, When trying to start VM I am getting the following error: # --- [root@xcp-dev01 ~]# xe vm-start uuid=f535e5bd-6540-3745-d494-14f776da85e5 Error code: INVALID_SOURCE Error parameters: Unable to access a required file in the specified repository: file:///tmp/cdrom-repo--2OF-Z/install.amd/xen/vmlinuz., , # --- I have used last xen server documentation to prepare the VM installation from

Package: xcp-storage-managers Version: 0.1.1-2 Severity: important Dear Maintainer, I can not create an iSCSI storage resource using the following command: xe sr-create host-uuid=<my-host-uuid> content-type=user name-label="LVM over iSCSI SR"> shared=true device-config:target=192.168.10.100 device-config:targetIQN=<here-target-iqn>

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,

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Function wait_for_xapi in /etc/init.d/xcp-xapi does not work as intented. Symptoms: (on slave) /etc/init.d/xcp-xapi restart [....] Restarting The XenAPI server: xapiThe host toolstack is still initialising. Please wait. Cause: Line 'xe pif-scan host-uuid=${INSTALLATION_UUID}' called before xapi is fully synced with master.

Title: HOWTO-FreeBSD-on-XCP Author: John D. "Trix" Farrar Date: 2012-02-09 * The Challenge - ParaVirtualized FreeBSD 9.0-RELEASE under XCP 1.1.0 The idea here is to create a PV FreeBSD VM under Xen Cloud Platform (XCP) without starting with an HVM first. The documentation I''''ve been able to find on-line is at least a year old and is mostly written for Xen (under

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'

Hi, all I''m totally new to XCP, so maybe i misunderstood the documentation. I tried to create Debian Squeeze (64-bit) and Ubuntu 10.04 from templates and install them from network installation. For Debian Squeeze (64-bit), I did the followings: 1. First ssh login into XCP host 2. xe vm-install template="Debian Squeeze (64-bit)" new-name-label=lenny-64-netinstall

Hello, Is it required to install an additional VNC server on XCP 1.1.0 dom0 box (ip 192.168.1.50)to get access to VNC-windows for installing domU guests? As I don''t use m$ / XenCenter so I need VNC for installation of new guests. The VM is running (s. below) *but* I was not able to open VNC window to continue the installation (s. error message further below) # --- uuid ( RO)

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: