similar to: Programmatic management alternatives of Xen domains

This fixes the xapi test case 02 with those parts that currently do not work disabled with ''if 0:'' Signed-off-by: Stefan Berger <stefanb@us.ibm.com> Index: root/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py =================================================================== --- root.orig/xen-unstable.hg/tools/xm-test/tests/xapi/02_xapi-vbd_basic.py +++

On Wed, Oct 16, 2013 at 6:41 PM, Celelibi <celelibi at gmail.com> wrote: > 2013/9/26, Ciprian Dorin Craciun <ciprian.craciun at gmail.com>: >> On Tue, Sep 24, 2013 at 11:57 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Sun, Sep 22, 2013 at 3:09 PM, Celelibi <celelibi at gmail.com> wrote: >>>> And (a bit out of scope) if I get my old

On Tue, Sep 24, 2013 at 11:57 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Sep 22, 2013 at 3:09 PM, Celelibi <celelibi at gmail.com> wrote: >> And (a bit out of scope) if I get my old kernel to boot in EFI mode, >> will the driver efivars have access to the EFI variables? Or does the >> kernel need to be recompiled specially for EFI? > > Doubtful.

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:

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-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}

2013/9/26, Ciprian Dorin Craciun <ciprian.craciun at gmail.com>: > On Tue, Sep 24, 2013 at 11:57 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Sun, Sep 22, 2013 at 3:09 PM, Celelibi <celelibi at gmail.com> wrote: >>> And (a bit out of scope) if I get my old kernel to boot in EFI mode, >>> will the driver efivars have access to the EFI variables?

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

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: ftp.debian.org Severity: normal Hi, Writting this message saddens me, but no choice... Because upstream authors (eg: Citrix) have explained that they cannot maintain the current version of XenAPI, or upgrade it to a newer version, we have no choice but to remove completely XenAPI from both Unstable and Testing. Quoting Euan Harris from Citrix (it's not needed for the FTP masters

Hello all! I found a little bug in the rsync v3.0.2 install, that is if you separate the build (output) folder from the source folder, the man files fail to install because they are generated in the output folder, but the install target searches them in the source folder. I attach a small patch that solves this problem. Thanks all, Ciprian Craciun. P.S.: I'm not on the

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

Package: xcp-xapi Version: 1.3.2-14 Severity: important I chose the Open vSwitch (ovs) networking mode when I installed XCP # cat /etc/xcp/network.conf openvswitch Whenever I boot a VM, I notice that the vif interface is created (e.g. vif1.0) on dom0, and the vif is added to the ovs bridge (I can see it in the output of ovs-vsctl show) However, there is no connectivity, I can't ping the

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-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 all, I am pleased to announce "libxenlight", a new small and lightweight C library that refactors existing code in a coherent and easy to use API to interface to the hypervisor and xenstore to perform operations such as domain creation and destruction, suspend/restore and pci passthrough. The goals of libxenlight are: - be easy to use and to extend - provide a simple and robust API

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