similar to: My Xen package plans/thoughts/ideas for Jessie

V4 of the patch, incorporating Bastian's suggestions. Jon --- xen/debian/patches/series | 1 + xen/debian/patches/tools-ocaml-fix-build.diff | 81 +++++++++++++++++++++++++ xen/debian/rules | 5 ++ xen/debian/rules.real | 39 ++++++++++++ xen/debian/templates/control.main.in | 16 +++++

Package: xen-hypervisor-4.2-amd64 Version: 4.2.1-2 Severity: critical Tags: upstream Justification: breaks the whole system Dear Maintainer, After migration from Xen 4.1 to 4.2 all VMs have disapeared and I am unable to "re-create" my VM from the configfiles. When I try "xm new com-web" i get a python message : Using config file "./com-web". Error:

... is actually old & very well known by the maintainer! there is a bug report for exactly this that is 3 years and 124 days old! http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=165505 I can also add my report to this bug and mention that we need a fixed version for our xen packages, but as it looks for me (at the moment) the maintainer is not really interessted in getting this

Here is the latest version of the patches to package the ocaml libraries. Changes since last time: * rename the packages from libxen-4.1-ocaml* to libxen-ocaml* - we wont be looking to install multiple concurrent versions of the same package, so the version doesn't need to be in the package name * Removed superfluous GENCONTROL definitions - dh_ocaml does what we need * Removed

During some discussions and handwaving, including discussions with some experts on the Xenserver/XCP storage architecture, we came up with what we think might be a plausible proposal for an architecture for communication between toolstack and driver domain, for storage at least. I offered to write it up. The abstract proposal is as I understand the consensus from our conversation. The concrete

Package: xen-utils-common Version: 4.1.2-3 Severity: important /etc/default/xen, which carries the TOOLSTACK setting, is not honored by xend init script. The xend initscript doesn't check for the value of TOOLSTACK. It just populates it in its initscript. lnx200-39:/etc/init.d# grep TOOLSTACK * xend:TOOLSTACK=$(/usr/lib/xen-common/bin/xen-toolstack 2>/dev/null) xend: if [ -z

Control: forcemerge 503287 737613 (making $subjet a bit more helpful this time too) On Mon, Nov 24, 2014 at 05:28:59PM +0000, Ian Campbell wrote: > Before investigating any further can either of you confirm whether > this still happens with the version of Xen currently in Jessie, which > is 4.4.1-3 (and the current kernel too). That was a major version > bump, so it is worth

Package: xcp-xapi Severity: important The README doc mentions: 4/ Configuring Xen and XCP -------------------------- 4.1/ Switch using xl instead of xm and xend to control Xen As of writing, you should do that: sed -i "s/TOOLSTACK=/TOOLSTACK=xl/" /etc/default/xen Where as the init script checks for: # Exit cleanly if TOOLSTACK != xapi if [ "${TOOLSTACK}" !=

tags 466683 +patch thanks commit 765ac4708e4dd8a6fea0028d631a7c3363b286b7 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 10:30:17 2013 +0100 * debian/changelog: Update * debian/templates/control.main.in: Update descriptions for some packages. diff --git a/xen/debian/changelog b/xen/debian/changelog index 6100e75..e5b25ef 100644 --- a/xen/debian/changelog +++

QUESTION: What, if anything, can I do so that I can use xl (in place of xm) with libvirt 1.0.2 and Xen 4.2.1 in Ubuntu 13.04? BACKGROUND: I am testing a fully updated (as of March 27) installation of Ubuntu 13.04 that includes the following packages: libvirt - version 1.0.2-0ubuntu9 xen-hypervisor-4.2-amd64 - version 4.2.1-0ubuntu1 Upon setting TOOLSTACK=xm in /etc/default/xen (as well as

There's no date defined yet, but Wheezy freeze will happen soon. How do we plan on concluding on this bug report? Recap for the actual bug I reported: If you want to start xapi, execute the following steps: 1) Start /etc/init.d/xend 2) Stop /etc/init.d/xend 3) Start /etc/init.d/xcp-xapi Step 1 is required because you need access to /proc/xen/ Step 2 is required because xapi cannot run

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

Package: xen-utils-common Version: 4.1.2-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The script /usr/lib/xen-common/bin/xen-toolstack improperly aborts if *either* `xm` or `xl` cannot be found in the xen-dir (/usr/lib/xen-4.0/bin). This means that a default installation (e.g. following Debian wiki on the subject, namely installing xen-linux-system and

Hello, is there a way to start automatically the vncviewer when a domU starts? When I was using the xm toolstack I could use "xm create domain.cfg -vncviewer" or something similar (if I''m not wrong), but I don''t know how to do it with the xl toolstack. At the moment, I have to create the domain using xl create domU.cfg, then xl list to see the domU id and then xl

I''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

Ian Campbell wrote: > + * Expand on the descriptions of some packages. (Closes: #466683) Trivial typo here: > Package: libxen-dev > Section: libdevel > Depends: libxen- at version@ (= ${binary:Version}), libxenstore3.0 (= ${binary:Version}), ${misc:Depends} > Description: Public headers and libs for Xen > This package contains the public headers and static libraries for

Package: xen-utils-common Version: 4.1.2-1 Severity: grave Justification: renders package unusable (Grave because dash is the default /bin/sh) With dash 0.5.5.1-7.4 as /bin/sh, /usr/sbin/xm enters an infinite loop of reexcuting itself. When run with bash, it works correctly. I traced that to /usr/lib/xen-common/bin/xen-toolstack; here's the diff between "/bin/sh -x /usr/sbin/xm"

Hello, I'm a programmer coming back into the mix, over the last couple of months I've been watching over Linux and OpenGL, CL Programming and have been setting my eyes over which open source project to contribute to. I'm mostly into systems programming and I been out of the game so much that while I'm researching the newest internet technologies like Ajax, JavaFX, typescript..

Hello list, is there a way to get more recent libvirt builds for CentOS 7 that include support for the xl (modern Xen) toolstack? I tried to build libvirt from the SRPM, which succeeded, however, without the mentioned Xen parts. I have also found two repos from people who provide upstream libvirt builds for CentOS 7, again, without the Xen parts. -

On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > When you use xl toolstack, you can't reboot domUs. > When you switch back to xm toolstack, than reboot works again. > I think the problem with the debian packaged version is the same as in > this thread: > http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html > I also think it's a security issue,