Displaying 20 results from an estimated 100000 matches similar to: "xe integration"
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)
2010 Aug 23
1
XCP, XCCS, xe, and XVP, random thoughts
Well, that was a lot of alphabet soup acronyms :).
I''ve just been thinking about the claim in a prior post that using the
xe cli with XCP abnormally increases the XCP server load. The only way I
could see this happening is to be running xe from the servers command
line. I use xe extensively to do the grunt work of XCCS (Xen Cloud
Control System). I don''t see the loading
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 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 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
2011 Aug 23
1
XCP: disk2vhd -> xenconvert (to ovf) -> xe vm-import
Hi all,
I`m evaluating methods for nightly "snapshot" a physical win2003 to
xcp vm.
I know it would be a lot easier and reliable just to to one convert
one time and start to generate real vm snapshots, but at this time I
cannot use this method.
I tested the sequence: disk2vdh -> xenconvert (to xcp), but a big
deal of using this method is that xenconvert does not send
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 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 May 04
1
Fwd: xe CLI: Error code: MEMORY_CONSTRAINT_VIOLATION - trial XenServer 6.0.2 image has a bug
I have encountered the same problem on XCP 1.1 and XCP 1.5 beta.
I tried "xe vm-memory-limits-set" command, and what I get is like
[root@xcp11 ~]# xe vm-memory-limits-set static-min=1GiB dynamic-min=4GiB
dynamic-max=4GiB static-max=4GiB --multiple
operation failed on 9587c557-39b0-4cb1-a0e7-f2e701f287ac: You attempted an
operation on a VM that was not in an appropriate power state at
2011 Oct 11
2
Wanted: XCP 1.1 tutorial for creating VMs from scratch using xe CLI
Hello,
It is nearly not possible to use XCP without a tutorial, in particular
if ones has to use the xe CLI.
Reading of reference.pdf and guests.pdf of XenServer and different wiki
pages didn''t help enough.
Even *XCP seems to be a very good software* it will be useless without
good documentation because of it''s complexity.
Thank you in advance for any hints.
Regards, Mark
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
2012 Sep 17
3
Bug#687936: xcp-xe: 'xe console' command undocumented
Package: xcp-xe
Version: 1.3.2-11
Severity: minor
xe did not prove help in autocomplete for xe console command.
Steps to reproduce:
xe console[tab]
Output (help) does not contains xe console command.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/8 CPU cores)
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 Jul 06
1
Bug#680511: xcp-xe: autocomplete for sr-probe type=nfs does not provide hints for device-config
Package: xcp-xe
Version: 1.3.2-8
Severity: minor
XCP 0.5,1.0 and 1.1 provides hints for device-config depends on type field in sr-probe, xcp-xapi (xcp-xe) does not.
Difference:
XCP 1.1 behavior:
xe sr-probe type=nfs device-config:[Tab]
device-config: device-config:serverpath=
device-config:server=
xcp-xe behavior:
xe sr-probe type=nfs device-config:[Tab]
(nothing)
Other arguments
2013 Dec 08
1
Bug#731718: after run: xe vm-import filename=... The VM could not be imported
Package: xcp-xe
Version: 1.3.2-15
after run: xe vm-import filename=debserv.ovf
i get messages:
The VM could not be imported.
msg: INTERNAL_ERROR: [ Failure("int_of_string") ]
In /var/log/xcp-xapi.log, i get the lines:
|5239 INET 127.0.0.1:80|VM import R:d700155bd1f0|import] Importing (as new VM)
|5239 INET 127.0.0.1:80|VM import R:d700155bd1f0|import] Reading XML
|5239 INET
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
2013 Oct 14
14
spice issue
Did something had chaqnged with spice code or settings. I just compiled
latest git of 4.4 unstable and I get is a black screen all I see is the
green boot image from server 2012 but I dont get blue windows logo and
window does not resize it stays black. I reverted back to older git
revision of 4.4 and everything is working fine with.
_______________________________________________
Xen-users