Re: kernel-2.6.32-131.2.1.el6.x86_64 Xen DomUs.

2011-06-14 Thread Stephan Wiesand
Hi Steven,

On Jun 14, 2011, at 0:04, Steven Haigh wrote:

 In the latest batch of updates, I installed kernel-2.6.32-131.2.1.el6.x86_64 
 via a 'yum -y update'.
 
 It seemed all of my 5 Xen DomUs running SL6 failed to boot upon rebooting. It 
 looks like all of these systems failed at roughly where switchroot is called.
 
 Interestingly, I could recover from this by shutting down the DomU, mounting 
 then chrooting the DomUs filesystem and issuing:
   # rpm -ivh --force kernel-2.6.32-131.2.1.el6.x86_64.rpm
 
 Not sure how widespread this issue is, but I had a 100% failure rate on Xen 
 DomUs. The one bare metal system I updated did so with no errors.

no problems here on the two Xen domUs we're currently running. But then, we're 
still updating kernels with rpm -i rather than yum.

Just a data point.

Regards,
Stephan

-- 
Stephan Wiesand
DESY -DV-
Platanenallee 6
15738 Zeuthen, Germany


Re: kernel-2.6.32-131.2.1.el6.x86_64 Xen DomUs.

2011-06-14 Thread Steven Timm

How are you booting the xen domU's, with pygrub, pvgrub, or
with external kernel?
Smells like either the mkinitrd failed to run at all, or
ran in such a way that it didn't put some required xen block
device into the ramdisk.

For that matter--what hypervisor host are you using for the SL6 xen 
domU's--is it an SL6 guest on an SL5 hypervisor?  I thought SL6 didn't

support being a xen host anymore.

Steve Timm


On Tue, 14 Jun 2011, Stephan Wiesand wrote:


Hi Steven,

On Jun 14, 2011, at 0:04, Steven Haigh wrote:


In the latest batch of updates, I installed kernel-2.6.32-131.2.1.el6.x86_64 
via a 'yum -y update'.

It seemed all of my 5 Xen DomUs running SL6 failed to boot upon rebooting. It 
looks like all of these systems failed at roughly where switchroot is called.

Interestingly, I could recover from this by shutting down the DomU, mounting 
then chrooting the DomUs filesystem and issuing:
# rpm -ivh --force kernel-2.6.32-131.2.1.el6.x86_64.rpm

Not sure how widespread this issue is, but I had a 100% failure rate on Xen 
DomUs. The one bare metal system I updated did so with no errors.


no problems here on the two Xen domUs we're currently running. But then, we're still 
updating kernels with rpm -i rather than yum.

Just a data point.

Regards,
Stephan




--
--
Steven C. Timm, Ph.D  (630) 840-8525
t...@fnal.gov  http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Group Leader.
Lead of FermiCloud project.


Re: kernel-2.6.32-131.2.1.el6.x86_64 Xen DomUs.

2011-06-14 Thread J. Ryan Earl
On Tue, Jun 14, 2011 at 8:57 AM, Steven Timm t...@fnal.gov wrote:

 For that matter--what hypervisor host are you using for the SL6 xen
 domU's--is it an SL6 guest on an SL5 hypervisor?  I thought SL6 didn't
 support being a xen host anymore.
 It seemed all of my 5 Xen DomUs running SL6 failed to boot upon rebooting.
 It looks like all of these systems failed at roughly where switchroot is
 called.


 Interestingly, I could recover from this by shutting down the DomU,
 mounting then chrooting the DomUs filesystem and issuing:
# rpm -ivh --force kernel-2.6.32-131.2.1.el6.x86_64.rpm

 Not sure how widespread this issue is, but I had a 100% failure rate on
 Xen DomUs. The one bare metal system I updated did so with no errors.


DomUs are guests.  TUV and SL6 do pv-ops, so the same kernel will run
baremetal or PV.

-JR


Re: kernel-2.6.32-131.2.1.el6.x86_64 Xen DomUs.

2011-06-14 Thread Steven Haigh

On 14/06/2011 11:57 PM, Steven Timm wrote:

How are you booting the xen domU's, with pygrub, pvgrub, or
with external kernel?
Smells like either the mkinitrd failed to run at all, or
ran in such a way that it didn't put some required xen block
device into the ramdisk.


I'm using pygrub. This way each system has its own kernel. I believe the 
ramdisk failed - either in including a module, or through a silent 
error. Either way, it failed.



For that matter--what hypervisor host are you using for the SL6 xen
domU's--is it an SL6 guest on an SL5 hypervisor? I thought SL6 didn't
support being a xen host anymore.


I use a self-compiled Xen 4.1.0 with a self-compiled 2.6.32.40 kernel. 
I'm looking at making them all into RPMs and hosting a Xen repo for 
kernel + xen - but I'm not that experienced in creating RPMs as yet. In 
time, I'll get around to it.


--
Steven Haigh

Email: net...@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299


kernel-2.6.32-131.2.1.el6.x86_64 Xen DomUs.

2011-06-13 Thread Steven Haigh

Hi all,

In the latest batch of updates, I installed 
kernel-2.6.32-131.2.1.el6.x86_64 via a 'yum -y update'.


It seemed all of my 5 Xen DomUs running SL6 failed to boot upon 
rebooting. It looks like all of these systems failed at roughly where 
switchroot is called.


Interestingly, I could recover from this by shutting down the DomU, 
mounting then chrooting the DomUs filesystem and issuing:

# rpm -ivh --force kernel-2.6.32-131.2.1.el6.x86_64.rpm

Not sure how widespread this issue is, but I had a 100% failure rate on 
Xen DomUs. The one bare metal system I updated did so with no errors.


--
Steven Haigh

Email: net...@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299