similar to: Bug#738322: RM: xen-api and friends -- ROM; non maintained upstream

Package: xcp-xapi Version: 1.3.2-6 Severity: important Looks like on Wheezy, /etc/default/xen is not created by xen-utils-common. Since xcp-xapi depends on its existence and further declaration of the toolstack in it, it should take extra care to ensure that it is present. root at debian:~# aptitude install xcp-xapi The following NEW packages will be installed: blktap-dkms{a} blktap-utils{a}

Dear Debian maintainer, On Thursday, March 15, 2012, I sent you a notification about the beginning of a review action on debconf templates for xen-api. Then, I sent you a bug report with rewritten templates and announcing the beginning of the second phase of this action: call for translation updates. Translators have been working hard and here is now the result of their efforts. Please

(new) libxenapi-ocaml-dev_1.3-13_amd64.deb extra ocaml OCaml bindings for the Xen API The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, with support for a range of guest operating systems, Linux network and storage support. . XCP addresses the needs of cloud providers, hosting services and data centers by combining the

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

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.

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:

I have a couple of questions regarding XCP: First, there were rumblings that there are issues upgrading XCP (1.5 -> 1.6)? Any further detail on these potential issues, or what needs to be done to get around them? Second, it previous versions of XCP there were tricks that had to be played (documented on the Wiki) to make XenCenter believe that XCP was actually a modern version of XenServer,

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

Hi there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Thu, 27 Dec 2012 13:05:06 +0000 Source: xen-api Binary: xcp-xapi python-xenapi xcp-squeezed xcp-v6d libxenapi-ocaml-dev xcp-xapi-debug xcp-xe xcp-networkd Architecture: source amd64 all Version: 1.3.2-14 Distribution: unstable Urgency: low Maintainer: Pkg Xen <pkg-xen-devel at lists.alioth.debian.org> Changed-By:

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sat, 03 Nov 2012 19:12:36 +0000 Source: xen-api Binary: xcp-xapi python-xenapi xcp-squeezed xcp-v6d libxenapi-ocaml-dev xcp-xapi-debug xcp-xe xcp-networkd Architecture: source amd64 all Version: 1.3.2-13 Distribution: unstable Urgency: low Maintainer: Pkg Xen <pkg-xen-devel at lists.alioth.debian.org> Changed-By:

Thanks Jon, it worked, I was able to build all the packages for xenserver on CentOS 6.6 final version. Here is the package list: https://gist.github.com/gautammaloo/7616cccbe8f5c85c196e I was wondering what packages would be necessary to use Xen with xapi, I already have xen with xl installed. Could we have a package like http://packages.ubuntu.com/precise/xcp-xe with which we can have

Hi, After reading XenServer documents and debugging, I found the previous configuration is correct, here is the one I've configured to work: In XCP, as in XenServer, system's network configuration doesn't really matter, it only make sense before XCP starts and handles the network settings. So there is no need to configure VLAN on host machine, and you only need a minimal one active

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

Hi Mike and Jon, If I do this: dpkg -S /usr/lib/python2.7/dist-packages/XenAPI.py then I can see that the XenAPI python package is in fact xcp-xapi. This is quite annoying, because I will need it when building OpenStack nova, but xcp-xapi depends on the Xen hypervisor, which I don't care about when building Openstack. Said in another way: I'd like to avoid having to put

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

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: [

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

libxenapi-ocaml-dev_1.3-14_amd64.deb to main/x/xen-api/libxenapi-ocaml-dev_1.3-14_amd64.deb (new) python-xenapi_1.3-14_all.deb extra python XCP XenAPI Python libraries The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, with support for a range of guest operating systems, Linux network and storage support. . XCP addresses the

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