similar to: ITP for XCP toolstack (xapi) on Debian

Package: wnpp Severity: wishlist Owner: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org> * Package name : blktap-dkms Version : 2.0.90 Upstream Author : Jon Ludlam <jonathan.ludlam at eu.citrix.com> * URL : http://www.xen.org/ * License : GPL-2 Programming Lang: C Description : Xen blktap kernel component DKMS package This package

Processing commands for control at bugs.debian.org: > retitle 655301 xend shouldn't start if TOOLSTACK is not xm Bug #655301 [xcp-xapi] xcp-xapi fails to start Changed Bug title to 'xend shouldn't start if TOOLSTACK is not xm' from 'xcp-xapi fails to start' > reassign 655301 xen-utils-common Bug #655301 [xcp-xapi] xend shouldn't start if TOOLSTACK is not xm Bug

Hello, I installed the last version of Xen (xenserver-core-0.9.0-9.x86_64 from yum) and I'm trying to manage my VMs with virsh. The version that I installed is using the Xapi/xe toolstack. The problem I have is that I'm not seeing the VM that is started with "virsh -c xen:/// list --all". Here is what I have: root# xe vm-list uuid ( RO) :

Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit : > According to [1] it seems that libvirt is using Xend daemon to communicate. After reading more documentation it seems that Xend is mandatory. As everything is not up to date I'd like to know if it is still the case or if there are some possibilities to use XL instead of Xend? Best regards, Guillaume

"Daniel P. Berrange" <berrange@redhat.com> a écrit : > On Mon, Sep 30, 2013 at 10:49:10AM +0200, Guillaume Thouvenin wrote: >> Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit : >> >> >According to [1] it seems that libvirt is using Xend daemon to communicate. >> >> After reading more documentation it seems that Xend is

# HG changeset patch # User john.levon@sun.com # Date 1161090130 25200 # Node ID afeef751f9dafa771726bcfb00b29a10b0baeabd # Parent 7147e57f18552bbb8d25155cc1c635315283ee31 On Solaris, GCC is configured to use Sun''s LD. Fix the build to use the correct flags, and link against libsocket where necessary. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/config/Linux.mk

On Mon, Sep 30, 2013 at 10:49:10AM +0200, Guillaume Thouvenin wrote: > Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit : > > >According to [1] it seems that libvirt is using Xend daemon to communicate. > > After reading more documentation it seems that Xend is mandatory. As > everything is not up to date I'd like to know if it is still the > case or

Guillaume Thouvenin <guillaume.thouvenin@polymtl.ca> a écrit : > "Daniel P. Berrange" <berrange@redhat.com> a écrit : >> If you have new enough libvirt and Xen >= 4.2 then libvirt will >> automatically >> use the libxl APIs instead of XenD. I have compiled a version 1.1.2 (with xapi and xl support) and installed it in /usr/local. I started the

Package: xcp-xapi Version: 1.3-15 Severity: normal By default, xapi listens on the loopback interface. To make it available over the network, its inventory needs to be updated with the bridged interface details. For example, if xenbr0 is the bridged interface, it needs to be set it: lnx200-39:~# cat /etc/xcp/inventory BUILD_NUMBER='0' CURRENT_INTERFACES='xenbr0'

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}

On 12/22/2011 01:37 AM, Mike McClurg wrote: > Hi Thomas, Jon, > > I was hoping that you could both comment on this github pull request: > > https://github.com/jonludlam/xen-api/pull/12 > > Mike > In Debian, /etc/default/xen is there to select xm vs xl. So we could do: if ! [ -f /etc/default/xen ] ; then TOOLSTACK=xm else . /etc/default/xen if ! [

Your message dated Sat, 06 Apr 2013 13:00:07 +0000 with message-id <E1UOSj1-0002As-63 at franck.debian.org> and subject line Bug#693137: fixed in swift-plugin-s3 1.7-1 has caused the Debian Bug report #693137, regarding ITP: swift-plugin-s3 -- swift3 (S3 compatibility) middleware plugin for swift to be marked as done. This means that you claim that the problem has been dealt with. If this

Hello, I have two questions regarding a survival analysis I have been working on. Below is the code to date. The variables: 1) recidivism$intDaysUntilFVPO are the number of days before an violent offence was committed - if no offence was committed than the days between court hearing and end of data collection was recorded. 2) recidivism$intDaysUntilFNVPO are the number of days before a

Processing commands for control at bugs.debian.org: > owner 693137 pkg-xen-devel at lists.alioth.debian.org Bug #693137 [wnpp] ITP: swift-plugin-s3 -- swift3 (S3 compatibility) middleware plugin for swift Owner changed from Thomas Goirand <zigo at debian.org> to pkg-xen-devel at lists.alioth.debian.org. > End of message, stopping processing here. Please contact me if you need

On Thu, 2012-05-24 at 09:08 +0900, Charles Plessy wrote: > Le Fri, May 11, 2012 at 04:17:39PM +0100, Ian Campbell a ?crit : > > > > Can I just check I understand the motivation for this script properly. > > > > There are two ways of setting up the disk for a VM. > > > > The first is the "whole disk" scheme. In this configuration the VM > >

Hi! I was running lintian on our package... Among the copious errors and warnings there are: W: xen-utils: manpage-has-errors-from-man usr/share/man/man1/xm.1.gz 668: warning: can't find numbered character 160 Should we try to fix this, perhaps? E: xen-hypervisor-pae: unstripped-binary-or-object ./boot/xen_pae-syms-3.0.1 E: xen-hypervisor: unstripped-binary-or-object ./boot/xen-syms-3.0.1

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: blktap Version: 2.0.90-2 Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. Please note that we use our research compiler tool-chain (using tools from the cbmc package), which permits extended reporting on type inconsistencies at link time. [...] libtool: link: gcc -shared -fPIC

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

On 12/05/2014 15:22, Tom Stellard wrote: > On Mon, May 12, 2014 at 08:41:36AM +0200, Sylvestre Ledru wrote: >> Hello, >> >> With the release of 3.4.1, the LLVM library has been renamed from >> libLLVM-3.4.so to libLLVM-3.4.1.so. In parallel, the soname has been >> updated to >> reflect this change. >> >> AFAIK, we kept the ABI compatible from 3.4