Displaying 20 results from an estimated 4000 matches similar to: "Bug#682979: xcp-xapi: VM not starting, tasks not cancellable"
2012 Jul 06
1
Bug#680499: xcp-xapi: Http_client.Http_request_rejected during upgrade
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: [
2012 Jul 19
1
Bug#682122: xcp-xapi: README.Debian has a few misleading commands
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
2012 Jul 03
1
Bug#680102: xcp-xapi: xcp fails eject host from pool (no /etc/firstboot.d found)
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,
2012 Jul 07
1
Bug#680588: xcp-xapi: startup race condition between xcp-xapi and xcp-networkd on slave
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:
2012 Jul 06
4
Bug#680528: xcp-xapi: /etc/init.d/xendomains cause xapi to hand during boot
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
2012 Jul 12
2
Bug#681343: xcp-xapi: wait_for_xapi() function in init.d script does not work
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.
2012 Jul 20
2
Bug#682202: xcp-squeezed not started on boot
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
2013 Aug 30
1
Bug#721345: xcp-xapi: xl pci-attach is called by xapi in a PCI passthrough attempt. An error is raised due to the use of xapi and the PCI device cannot be attached to the VM.
Package: xcp-xapi
Version: 1.3.2-15
Severity: normal
I am trying to pass an SRIOV virtual function in a virtual machine but the attempt fails with the following errors shown in the xcp-xapi.log
[20130829T19:29:17.909Z|debug|sriov1|314 UNIX /var/lib/xcp/xapi|VM.start R:9e8e10bd31bb|pciops] PCI devices from other-config:pci to attach: 0/0000:04:00.1
[20130829T19:29:18.012Z|debug|sriov1|314 UNIX
2012 Sep 05
3
Bug#686778: xcp-xapi: what user should xapi run as
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
2012 Jun 14
2
Bug#677509: xcp-xapi: migration of PV linux does not produce grace ARP
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
2012 Jun 15
1
Bug#677614: xcp-xapi: someone should create /etc/default/xen
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}
2012 Jun 24
1
Bug#678723: xcp-xapi: vif-interfaces added to database as PIF's
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
2012 May 29
2
Bug#675050: xcp-xapi: /usr/lib/xcp/lib/bin/xe-edit-bootloader uses wrong path to the 'xe'
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
2012 Sep 27
1
Bug#688961: xcp-xapi: xe host-set-hostname-live fails (debian is not centos!)
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
2012 May 29
1
Bug#675052: xcp-xapi: xe vm-memory-target-set does not write target to xenstore
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)
2012 May 23
2
Bug#674088: xcp-xapi: vbd-plug to dom0 does not creates /dev/xvd* devices in dom0
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
2012 Jun 25
4
Bug#678923: xcp-xapi: host-disable and host-reboot make host disable forever
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:
2012 Jun 13
2
Bug#677395: xcp-xapi: xe pif-configure-ip does not remove old ip from interface
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
2012 May 23
4
Bug#674161: xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start)
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
2012 Dec 05
4
Bug#695221: xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet netmask
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