Displaying 20 results from an estimated 2000 matches similar to: "Bug#688961: xcp-xapi: xe host-set-hostname-live fails (debian is not centos!)"
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 May 01
1
Bug#670988: xcp-xapi: /usr/lib/xcp/bin/xe-mount-iso-sr has wrong path for XE
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)
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 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 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 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
2012 May 29
3
Bug#675055: xcp-xapi: xe-edit-bootloader does not compatible with new /dev/sm
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
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 Apr 05
0
xe vdi-create failure ot local SR type=file and type=ext
Hi,
have permanent failure when try to create VDI on local SR type=file or
type=ext. On both types it failed with the same error:
SR_BACKEND_FAILURE_78
VDI Creation failed [opterr=error 127]
I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian
4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos)
Is it a bug, or am I missing something? Anybody managed to workaround
this problem?
Here is
2012 Apr 05
0
Re: [Xen-API] xe vdi-create failure ot local SR type=file and type=ext
The log snippet doesn''t have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there.
Jon
On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote:
> Hi,
> have permanent failure when try to create VDI on local SR type=file or
> type=ext. On both types it failed with the same error:
> SR_BACKEND_FAILURE_78
> VDI Creation failed
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 Apr 05
0
Re: [Xen-API] (solved) xe vdi-create failure ot local SR type=file and type=ext
Thanks!
I found the problem in SMlog.
/usr/sbin/td-util create vhd 1024
/var/run/sr-mount/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/247b64e4-6b7f-4b2f-bd73-50e848c78d71.vhd
/usr/sbin/td-util: error while loading shared libraries:
libxenctrl.so.4.0: cannot open shared object file: No such file or directory
td-util from blktap-utils 2.0.90-3 (testing) is looking for
libxenctrl.so.4.0, but the package
2013 Jul 06
0
"Operation not permitted" error when using "xe vm-start"
Hey!
I am following the steps at
http://wiki.xenproject.org/wiki/XCP_Beginners_Guide for creating a VM.
I''ve setup my test VM with 1GiB min/max memory. I''ve assigned 2GiB of
memory to dom0 (http://wiki.xen.org/wiki/Xen_Best_Practices) . My box
has 12GB of physical memory and runs Ubuntu 13.04.
When I do "xe vm-start", I get the following:
The server failed to handle
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 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
2013 Sep 27
2
Does libvirt support xapi/xe toolstack?
Hello,
I installed the last version of Xen (xenserver-core-0.9.0-9.x86_64 from
yum) and I'm trying to manage my VMs with virsh. The version that I
installed is using the Xapi/xe toolstack. The problem I have is that
I'm not seeing the VM that is started with "virsh -c xen:/// list
--all". Here is what I have:
root# xe vm-list uuid ( RO) :
2012 Jan 10
2
Bug#655301: xcp-xapi fails to start
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
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 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