Displaying 20 results from an estimated 20000 matches similar to: "Processed: sets some xcp-api bug severities"
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
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 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 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 Nov 04
2
Last round of XCP bug squashing in Debian Wheezy, before the release
Hi,
I've been trying to fix several bugs in XCP, before the Debian 7
release. It's not bug free yet, but it's going into that direction. I
would need some help to fix the remaining!
1/ The new 1.3.2-12 release
The Debian release team has already accepted an unblock for this new
version that I uploaded in Debian SID. Here's the debian/changelog:
* Fixes bashism in
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 Jul 03
4
Processed: your mail
Processing commands for control at bugs.debian.org:
> reopen 678923
Bug #678923 {Done: George Shuklin <george.shuklin at gmail.com>} [xcp-xapi] xcp-xapi: host-disable and host-reboot make host disable forever
Bug reopened
Ignoring request to alter fixed versions of bug #678923 to the same values previously set
>
End of message, stopping processing here.
Please contact me if you need
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 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 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)
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 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
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 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 Jun 20
2
"No text console available" when trying to get the console of a just created VM from a template on XCP
Hi there,
I am trying to set up XCP on Ubuntu 12.04. I went through the
procedure given in the README file of the xcp-xapi package and reached
the point where the hypervisor seems to be running fine. I set up a VM
using the Debian Squeeze (64bit) template and started it, giving a
Debian mirror URL as install-repository.
Running "xe vm-list" reports that the machine is running, but when
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 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 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 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 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,