Fwd: Re: Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

Fwd: Re: Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

[Michal Novotny]

On 03/01/2010 03:25 PM, Ian Campbell wrote:

>  On Mon, 2010-03-01 at 14:21 +0000, Michal Novotny wrote:
>
>>  Hi,
>>  well, I tried reverting this patch and both applying and not applying
>>  the new one from Ian but there is still kernel oops. Error image is
>>  attached. Also, I tried disabling CONFIG_SPARSE_IRQ (i.e. setting this
>>  to n) but no luck. Still the same issue.
>>
>  This isn't the same panic, this is failing to mount a root filesystem.
>  Probably a missing driver modules or an incorrect initrd or something
>  like that.
>
>  Ian.
>
>
>
Yeah, I can see that now but this root was working fine with
kernel-2.6.18.8 for xen so may be a missing driver is the real issue
because it's after initrd already and even booting to single user mode
or emergency mode is not working so this seems that is cannot see the
root because of missing driver but the driver should be there I guess
(this should be a SAS drive). Well, needs a little more investigation.

Thanks,
Michal

-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat

Re: Fwd: Re: Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!

[Ian Campbell]

On Mon, 2010-03-01 at 17:17 +0000, Michal Novotny wrote:
> On 03/01/2010 03:25 PM, Ian Campbell wrote:
> 
> >  On Mon, 2010-03-01 at 14:21 +0000, Michal Novotny wrote:
> >
> >>  Hi,
> >>  well, I tried reverting this patch and both applying and not applying
> >>  the new one from Ian but there is still kernel oops. Error image is
> >>  attached. Also, I tried disabling CONFIG_SPARSE_IRQ (i.e. setting this
> >>  to n) but no luck. Still the same issue.
> >>
> >  This isn't the same panic, this is failing to mount a root filesystem.
> >  Probably a missing driver modules or an incorrect initrd or something
> >  like that.
> >
> >  Ian.
> >
> >
> >
> Yeah, I can see that now but this root was working fine with
> kernel-2.6.18.8 for xen so may be a missing driver is the real issue
> because it's after initrd already and even booting to single user mode
> or emergency mode is not working so this seems that is cannot see the
> root because of missing driver but the driver should be there I guess
> (this should be a SAS drive). Well, needs a little more investigation.

Many of the SATA/PATA device drivers changed name between 2.6.18 and a
more modern kernel. Something to do with the libata transition IIRC.

I recommend you get a modern kernel booting natively on your system
before worrying about pvops domain 0.

Ian.