similar to: CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

This is a community SIG .. and xenproject.org does NOT release XSAs for 4.2. The goal of Xen4centOS was to use an upstream LTS kernel and update those as required to stay on an LTS. Also to do every second point release of xen (ie, 4.2, 4.4, 4.6). All so we are longer term than upstream, BUT we have supported code from upstream. So, the goal is to use supported code for the longest amount of

On Thu, Jan 21, 2016 at 1:28 PM, Phill Bandelow <phill at onapp.com> wrote: > Well when the last upgrade 4.2 > 4.4 went live and XM was disabled by > default it took many hosts down without warning. 4.4 > 4.6 may cause the > same issues. It's a dangerous upgrade for sure. Why can't 4.4 be LTS for C6? > as it's the last build with XM. Any XSA patches should not

On Thu, Jan 21, 2016 at 12:01 PM, Peter <peter at pajamian.dhs.org> wrote: > On 15/01/16 05:57, George Dunlap wrote: >> As mentioned yesterday, Xen 4.6 packages are now available for >> testing. These also include an update to libvirt 1.3.0, in line with >> what's available for CentOS 7. Please test, particularly the upgrade >> if you can, and report any

As mentioned yesterday, Xen 4.6 packages are now available for testing. These also include an update to libvirt 1.3.0, in line with what's available for CentOS 7. Please test, particularly the upgrade if you can, and report any problems here. To upgrade: yum update --enablerepo=centos-virt-xen-testing To install from scratch: * Install centos-release-xen from centos-extras yum install

Well when the last upgrade 4.2 > 4.4 went live and XM was disabled by default it took many hosts down without warning. 4.4 > 4.6 may cause the same issues. It's a dangerous upgrade for sure. Why can't 4.4 be LTS for C6? as it's the last build with XM. Any XSA patches should not be hard to backport. and maybe the optional xen4.6 for C6. On 21 January 2016 at 13:09, President

Its my impression that as a general rule from RH once some software has been released into a major release any further release of that software does not change major version or fundamental features.. For C6 I would argue Xen 4.2 should stay packaged as xen and Xen 4.4 be packaged as xen44 ... I do not believe that Xen has been released for C7 yet so what ever package version is released

My comment was targeted more at naming than support. I appreciate that there are vanishingly few resources to throw at support. I am glad to see any xen support for C7 and am thankful of all those who are putting in time to make things happen. I try to help out when I can but it is all too infrequently. On 01/21/2016 10:29 AM, Johnny Hughes wrote: > This is a community SIG .. and

Just out of annoyance more than curiosity, but ever since I started using Xen 4.2-unstable rev-25467, every time I try to run "sudo xl create <domu_config_file>", or "sudo xl reboot", or "sudo xl destroy", it always gives me this message: "*xend is running, which prevents xl from working correctly. If you still want to force the execution of xl please

Hi - I''m trying to use the instructions here http://xen.pablolibo.com/doku.php to create a new VM but it''s not clear where the .cfg file should go and what to do next. I was thinking xe needs to install the vm from the /mnt/so_xen mount but i''m not sure. Are the steps on the site reasonable? Is there a way to install a vm from USB instead?  I don''t have an

I have the following packages going through the CBS: * A CentOS 7 xen-4.6.1-2, with XSAs 170 and 154 * A CentOS 6 xen-4.6.1-2, with XSAs 170 and 154 * A CentOS 6 xen-4.4.3-11, with XSAs 170 All these should show up in mirrors hopefully sometime later today. As usual, please report any problems here. Xen 4.4 only has XSA 170 because at the time the embargo was lifted, I didn't have a suitable

Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a guest because of what looks like an issue allocating memory even though xm info shows like 5x the amount of free memory needed? We are still unfortunately still using xm... it's on my list, i know.. We've had this happen on a couple hosts now. Only way to resolve seams to be rebooting the host. I'm going to

Hi folks The current package in unstable is able to use xl. It is still a bit edgy but seems to work. Because the old xm with xend and xl clashs and one should only use one, this needs some more setup to provide a proper upgrade path. I propose the following: - Add a script "xen" that wraps xl and xm depending on the config for use by all the scripts. Most parts are command line

Hi, When I rename a domain with xl, the new name shows in xl list but not in xm list, and the other way around. xentop and xl top use the names visible in xm list. -- Hans xen 4.1.1 / 3.0.0-rc7 non hvm _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

On Mon, Sep 21, 2015 at 4:18 PM, Pasi K?rkk?inen <pasik at iki.fi> wrote: > On Mon, Sep 21, 2015 at 01:46:36PM +0300, Pasi K?rkk?inen wrote: >> >> OK. I can now see the libvirt 1.2.15-3.el7 rpms in the virt7-xen-44-testing repo, >> but it seems yum still doesn't pick them up: >> >> # yum clean all >> # yum --enablerepo=virt-xen-44-testing update

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

Recent xen uses xenbus to suspend PV-on-HVM guest domain. The related code in the xen-unstable tree will fall into infinite loop when guest domain failed on suspending one or more devices. The patch attached changes the logic, and raises an XendError after 1 minute waiting. The patch also makes use of "control/shutdown" entry in xenstore, allows guest kernel report the failure of the

Hi, One of the I noticed during migration from XM toolchain to XL in PCI Pass-through was that we used to specify target bdf in HVM guest as pci = [ ''0000:07:11.6=0@1a'' ] However with XL, it now seems like this is the correct syntax: pci = [ ''0000:07:11.6@1a'' ] Is that correct? I''ve verified that it works but what about zero in

Hi, I am in the process of upgrading some xen installations from 3.x to 4.1.1 and got into this: box# xl create vm1.cfg warning: Config file looks like it contains Python code. warning: Arbitrary Python is no longer supported. warning: See http://wiki.xen.org/xenwiki/PythonInXlConfig Failed to parse config file: Invalid argument I''m using python stuff to define vifs and disks

# HG changeset patch # User Jim Fehlig <jfehlig@novell.com> # Date 1288301229 21600 # Branch xend-pci # Node ID 461b9d3a643a2c67c961d9fc468a804891f3770d # Parent 28a16074681582f1209c9077f870ccf44927133e Fix pci passthru in xend interface used by libvirt Attempting to define or create a domain whose XML config contains a passthru PCI device fails with libvirt xen84: # cat win2k8r2.xml ...

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