similar to: XCP and access to consoles

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.

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

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

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

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sat, 03 Nov 2012 19:12:36 +0000 Source: xen-api Binary: xcp-xapi python-xenapi xcp-squeezed xcp-v6d libxenapi-ocaml-dev xcp-xapi-debug xcp-xe xcp-networkd Architecture: source amd64 all Version: 1.3.2-13 Distribution: unstable Urgency: low Maintainer: Pkg Xen <pkg-xen-devel at lists.alioth.debian.org> Changed-By:

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

running xen cloud on my ubuntu12.04 box connecting with xencenter - i can create delete and monitor VM''s when i connect to the console i can see the console output but none of my keypresses or mouse clicks are registered in the VM everything i hit a key i get this in my xcp-xapi log [20120721T17:17:20.330Z|debug|xen|509 INET 127.0.0.1:80|Connection to VM console R:73c96b23cdd8|console]

All: I''m currently using the older Python-based Xen tools on a cluster of machines, but we''re looking to transition to XCP as the platform of choice for our applications. However, I''ve run into one issue that''s sort of a blocker: paravirtual Linux domUs boot and run, but the console device is strangely broken. Most of the output reaches the connected user (some

Hi, I am a newb to XCP and somewhat to Linux. I set up XCP on a test machine and used xe to configure a couple of VMs. The VMs are working fine but if I deploy XCP with only xe to manage machines, the others here will want my head on a plate. I set up a Fedora client on a different machine and installed Virtual Machine Manager. When trying to connect via SSH, I get an error that says

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

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)