Displaying 20 results from an estimated 6000 matches similar to: "Bug#695221: xcp-xapi: xe pif-reconfigure-ip doesn't work with non 255.255.255.0 subnet, netmask"
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 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 Jul 06
1
Bug#680500: xcp-xe: Tab in autocomple of params for 'xe pif-list params=' erase some arguments
Package: xcp-xe
Version: 1.3.2-8
Severity: minor
When autocomplete for bash is activated following misbehavior happens:
xe pif-list params=device,m[Tab]
expected behavior:
autocomplete to xe pif-list params=device,management
actual behavior:
xe pif-list params=management
('device' removed)
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500,
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 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 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
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
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 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 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 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:
2010 Aug 16
3
XCP: xe host-evacuate generates wrong error message
Good day.
XCP 0.5
xe host-evacuate uuid=f9458b0b-5e35-4ee0-adcf-c8945a37868c
You attempted an operation on a VM which requires a more recent version
of the PV drivers. Please upgrade your PV drivers.
vm: a84aaf23-8afe-2ccc-0299-83b9dfd08c35
But at really vm uuid with bad PV-drivers is
42e397c7-3d76-02c0-a1f9-c78d79cac6c6 and no uuid a84aaf23... present in
pool.
I think, it is an error in
2012 Jul 27
1
Bug#682979: xcp-xapi: VM not starting, tasks not cancellable
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
2012 Jul 21
1
xcp-xapi console problems with xencenter
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]
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 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 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