Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread George Dunlap
On Thu, Jan 21, 2016 at 12:01 PM, Peter 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

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread Phill Bandelow
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

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread Alvin Starr
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 ...

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread Peter
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 problems here. Per

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread George Dunlap
On Thu, Jan 21, 2016 at 1:28 PM, Phill Bandelow 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

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread President
My .02 is to stay the course.  As a server admin, I want to be able to type things like: yum upgrade php not yum upgrade php55-epel-rpmforge-fancy-package Having to remember all the idiosyncrasies of a system is what causes some type of major failure in the future whenever (1) you

[CentOS-virt] DomU Guests not shutting down nicely when Dom0 Hypervisor shuts down

2016-01-21 Thread Francis Greaves
I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen 4.? on CentOS 6.5 on my previous system. I installed using yum install centos-release-xen. On shutting down the Hypervisor it used to wait for the DomUs to shut down gracefully (one can take a minute or more), then on

Re: [CentOS-virt] DomU Guests not shutting down nicely when Dom0 Hypervisor shuts down

2016-01-21 Thread Phill Bandelow
Try this: systemctl start xendomains.service systemctl enable xendomains.service On 21 January 2016 at 08:48, Francis Greaves wrote: > I am using Xen 4.6.0-8.el7 on CentOS 7 with 3 Linux DomUs. I did have Xen > 4.? on CentOS 6.5 on my previous system. I installed using

Re: [CentOS-virt] DomU Guests not shutting down nicely when Dom0 Hypervisor shuts down

2016-01-21 Thread Keith Roberts
Hi Francis. Personally I would gracefully shutdown all the VM’s first, before attempting to shutdown the xen hypervisor. Are you getting any fsck errors when restarting those VM’s? Kind Regards, Keith On 21 Jan 2016, at 08:48, Francis Greaves wrote: > I am using Xen

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread Johnny Hughes
On 01/21/2016 08:02 AM, George Dunlap wrote: > On Thu, Jan 21, 2016 at 1:28 PM, Phill Bandelow 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

[CentOS-virt] Hostname inside lxc container

2016-01-21 Thread C. L. Martinez
Hi all, I have installed a CentOS6 lxc guest under a Debian 8.x LXC host. All it is working ok but I can't change the hostname for the centos6 lxc container (it is using the same hostname from Debian host). I have modifyed HOSTNAME under /etc/sysconfig/network and /etc/hosts file, but it doesn't

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread George Dunlap
On Thu, Jan 21, 2016 at 3:39 PM, Johnny Hughes wrote: > On 01/21/2016 09:29 AM, Johnny Hughes wrote: >> 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

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread Johnny Hughes
On 01/21/2016 09:29 AM, Johnny Hughes wrote: > 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,

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread Johnny Hughes
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

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread Johnny Hughes
On 01/21/2016 09:52 AM, George Dunlap wrote: > On Thu, Jan 21, 2016 at 3:39 PM, Johnny Hughes wrote: >> On 01/21/2016 09:29 AM, Johnny Hughes wrote: >>> This is a community SIG .. and xenproject.org does NOT release XSAs for >>> 4.2. The goal of Xen4centOS was to use an

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread George Dunlap
On Thu, Jan 21, 2016 at 4:17 PM, Alvin Starr wrote: > 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

Re: [CentOS-virt] Hostname inside lxc container

2016-01-21 Thread Scott Dowdle
Greetings, - Original Message - > I have installed a CentOS6 lxc guest under a Debian 8.x LXC host. > All it is working ok but I can't change the hostname for the centos6 lxc > container (it is using the same hostname from Debian host). I have > modifyed HOSTNAME under

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread George Dunlap
On Thu, Jan 21, 2016 at 1:28 PM, Phill Bandelow 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

Re: [CentOS-virt] DomU Guests not shutting down nicely when Dom0 Hypervisor shuts down

2016-01-21 Thread Francis Greaves
Thanks a million for that. All working fine now. Ragards From: "Phill Bandelow" To: "Francis Greaves" , "centos-virt" Sent: Thursday, 21 January, 2016 09:20:40 Subject: Re: [CentOS-virt] DomU Guests not shutting down nicely

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread Peter
On 22/01/16 01:32, George Dunlap wrote: > 1. In the Xen 4.4 packages (first released October 2014), xend was > disabled by default; so anyone using xend at the moment has already > manually intervened to enable deprecated functionality Xen4CentOS was first available in CentOS 6.4 with Xen 4.2, so

Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing

2016-01-21 Thread Sarah Newman
On 01/21/2016 04:32 AM, George Dunlap wrote: > I'm a developer, not a server admin, so I can't gauge how important > this issue is. Before making such a change, I'd like to hear opinions > from other people in the community about how important (or not) it is > to avoid breaking xm, given the