On Fri, Mar 4, 2011 at 6:16 AM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:

On Tue, Mar 01, 2011 at 05:59:54PM +0800, Teck Choon Giam wrote:
> On Tue, Mar 1, 2011 at 12:20 AM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
>
> > > This is just an update from my testing.
> > >
> > > I tried with latest xen/next-2.6.32.x and same bug still there:
> >
> > Grrrrrrrr..
> >
> > Let me setup a machine to reproduce this. Is the distro you are using
> > still CentOS 5?
> >
>
> Yes.

OK, I got a machine with CentOS 5.5 installed. Had some trouble getting
the kernel to boot - a different issue that the one you are seeing however.

What arguments are you using for your dom0 and Xen hypervisor?

Example in one of my test server:

title CentOS (2.6.32.29-0.xen.pvops.choon.centos5)
    root (hd0,0)
    kernel /xen.gz dom0_mem=1024M loglvl=all guest_loglvl=all cpuidle=0 cpufreq=none
    module /vmlinuz-2.6.32.29-0.xen.pvops.choon.centos5 ro root=/dev/md1 panic=5 panic_timeout=5
    module /initrd-2.6.32.29-0.xen.pvops.choon.centos5.img