<p>
Raid 1 is mdadm software raid
</p>
<p>
Disk layout on /dev/hd[ab] is
</p>
<p>
md0 = /boot
</p>
<p>
md2 = swap
</p>
<p>
md1 = LVM
</p>
<p>
The root filesystem for dom0 is in LVM along with the root and swap file systems for a number of guests
</p>
<p>
</p>
<p>
I currently use pygrub to boot most of the guests. As I said the guests arent the issue, my Dom0 instance hangs with the most recent kernel.
</p>
<p>
</p>
<p>
Steve
</p>
<p>
</p>
<p>
On Wed, 27 Oct 2010 19:26:29 -0700, Eric Searcy wrote:
</p>
<blockquote style="border-left: 2px solid #1010ff; padding-left: 5px; margin-left: 5px; width: 100%">
<div>
Curious, RAID1 is soft/md, fakeraid or hardware?
</div>
<div>
<br />
</div>
<div>
Also, are you using pygrub and then what is the kernel for the guests, or are you using a kernel from the host/which one?
</div>
<div>
<br />
</div>
<div>
(I'm using almost-latest, ie last week, kernel on host and guest (pygrub) on hardware raid, haven't had any issues to date.)
</div>
<div>
<br />
</div>
<div>
Eric<br />
<div>
<br />
</div>
<div>
Sent from my iPhone. Pardon the top-posting!
</div>
</div>
<div>
<br />
On Oct 27, 2010, at 5:56 PM, Steven Ellis <<a href="mailto:mail_lists@stevencherie.net">mail_lists@stevencherie.net</a>> wrote:<br />
<br />
</div>
<blockquote>
<div>
<p>
I've recently upgraded a Centos 5.3 machine to Centos 5.5. The hardware isn't HVM capabile so I'm only running para-virt guests.
</p>
<p>
Using a vanilla i386 kernel boots without, but the newer kernel-xen locks up the Dom0 after a couple of minute. I'm only booting into single user mode for these tests so no VMs are active.
</p>
<ul>
<li>kernel-xen-2.6.18-128.1.10.el5 - no issues
</li>
<li>kernel-xen-2.6.18-194.17.4.el5 - lock up
</li>
<li>kernel-2.6.18-194.17.4.el5 - no issues
</li>
</ul>
<br />
For the moment I've switched back to the older Xen kernel, athough I'm still running the newer Xen Hypervisor.<br />
<p>
My current Xen packages are
</p>
<ul>
<li>xen-3.0.3-105.el5_5.5</li>
<li>kernel-xen-2.6.18-194.17.4.el5</li>
<li>kernel-xen-2.6.18-128.1.10.el5</li>
<li>kmod-xfs-xen-0.4-2</li>
<li>xen-libs-3.0.3-105.el5_5.5</li>
<li>kernel-xen-devel-2.6.18-194.17.4.el5</li>
<li>kernel-xen-devel-2.6.18-128.1.10.el5</li>
<li>xen-devel-3.0.3-105.el5_5.5</li>
</ul>
<p>
Prior to the upgrade I had the following installed under Centos 5.3
</p>
<ul>
<li>kernel-xen-devel-2.6.18-128.1.6.el5</li>
<li>kernel-xen-2.6.18-128.1.10.el5</li>
<li>xen-libs-3.0.3-80.el5_3.2</li>
<li>xen-devel-3.0.3-80.el5_3.2</li>
<li>kmod-xfs-xen-0.4-2</li>
<li>kernel-xen-2.6.18-128.1.6.el5</li>
<li>kernel-xen-devel-2.6.18-128.1.10.el5</li>
<li>xen-3.0.3-80.el5_3.2</li>
</ul>
<p>
Booting Dom0 with kernel-xen-2.6.18-128.1.10.el5 everything appears to work normally and all of my Guests are up and running.
</p>
<p>
If I boot with kernel-xen-2.6.18-194.17.4.el5 the boot normally gets to around udev and the system locks up. On a couple of occasions it did mange to boot but reported some files were corrupted. I'm worried that there is an issue running this kernel where the root file system is LVM on top of Raid 1.
</p>
<p>
Anyone on this list have tips on diagnosing the issue, or come across a similar problem themselves.
</p>
<p>
Steve
</p>
<p>
</p>
<p>
</p>
</div>
</blockquote>
<blockquote>
<div>
<span>_______________________________________________</span><br />
<span>CentOS-virt mailing list</span><br />
<span><a href="mailto:CentOS-virt@centos.org">CentOS-virt@centos.org</a></span><br />
<span><a href="http://lists.centos.org/mailman/listinfo/centos-virt">http://lists.centos.org/mailman/listinfo/centos-virt</a></span><br />
</div>
</blockquote>
</blockquote>
<p>
</p>