similar to: 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.

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

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

Thanks, I'll take a look at this. Mike On Sat, Jun 1, 2013 at 12:28 AM, David Su?rez <david.sephirot at gmail.com>wrote: > Source: xen-api > Version: 1.3.2-15 > Severity: serious > Tags: jessie sid > User: debian-qa at lists.debian.org > Usertags: qa-ftbfs-20130529 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages

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

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

1) Misspelled message ''killing umanaged domain'' (must be killing UNmanaged domain) 2) more serious. I found this message after disappearance of virtual machine created early. I restart XAPI tool stack and machine was killed (not shutdowned, but completely removing). Here log (from machine where domain was resident) Main line in log file I suspect:

Source: xen-api Version: 1.3.2-15 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/?PKGBUILDDIR?' > omake phase1 > omake: Symbol `FamErrlist' has different size

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

Hi All I have downloaded the opensource xapi source code. I am not sure what the functins of the follow modules: 1 block_device_io 2 datamodel 3 xiu (I am puzzled by the name "xiu") 4 stats 5 rpc-light 6 rss 7 xb (I think the xapi needs not to talk to xenbus directly) 8 xsrpc (why it writes some "rpc" keys to path of "domain/<domid>" in the

errors from /var/log/xcp-xapi.log: 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xapi] creating device emulator 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] Device.Dm.start domid=10 661Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] qemu-dm: should be running in the background (stdout redirected to syslog) 661Z|debug||1227 UNIX

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

Source: xen-api-libs Version: 0.5.2-3 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130620 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory `/?PKGBUILDDIR?/stdext' > ocamlfind ocamlc -I ../xml-light2 -I ../stdext -I

(CC'ing George Shulkin, and the #680102 bug list) On Sat, Jul 7, 2012 at 4:37 PM, Thomas Goirand <thomas at goirand.fr> wrote: > Hi Mike and Jon, > > It would be really nice if you could have a look at these 3 pending > issues in the Debian bug tracker: > > #675052: xe vm-memory-target-set does not write target to xenstore > #678723: vif-interfaces added to database

This logfile was recorded while the vm-start was running. -------------- next part -------------- [20120727T14:43:34.919Z| info|vh10|1021 UNIX /var/lib/xcp/xapi|session.logout D:dd291648d150|xapi] Session.destroy trackid=e3179eeb95ba96c64ab771d0cb1557b6 [20120727T14:44:02.180Z|debug|vh10|25|Starting periodic scheduler D:641021a392d0|backgroundscheduler] Adding function Logrotate to queue,

Package: xen-api-libs I cannot backport xen-api-libs to an oldstable system. It fails with: $ dpkg-buildpackage -rfakeroot -us -uc dpkg-buildpackage: source package xen-api-libs dpkg-buildpackage: source version 0.5.2-3.1 dpkg-buildpackage: source changed by St?phane Glondu <glondu at debian.org> dpkg-buildpackage: host architecture amd64 dpkg-source --before-build xen-api-libs-0.5.2

Hello XCI developers, I have a HP6930, downloaded xenclient from the git. And by following the instruction in HOWTO, I could get xenclient boot up fine. I try then to start a guest using xenvm.readme as template and nothing shows on the screen for the guest, although xenops shows 2 doms running. Can you point me to how to start a guest. And also, is the tree downloaded from git enough to arrive

Hi David > Hi all, So I have been playing around with XCP and the static/dynamic > memory parameters. I have a few behavioral questions I would like to > pin down: > > -Is the static-max quantity of free memory on the host always > required before the guest vm can be started? I assume so since you > don''t know a-priori if the guest you are booting supports Xen or

Hello everyone, for research purposes I''m working on Xen 3.0.3 and trying to make some modifications to Xen migration. By looking at the documentation, I''ve learned that the part I''m interesting in are handled by two binaries (xc_save and xc_restore), so I thought about modifying just this two binaries instead of recompiling the whole Xen everytime, so what I do is just

Package: xcp-xapi Severity: normal Tags: upstream Are there good reasons why xapi by default prefers to bidn to 80 and 443? This will lead to xapi installation/start failure on every server machine that might (and will probably) have apache installed. I know we can remove apache or change its port or change xapi's port (But I've had a hard time to easily find out where to specify the

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