This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: Fwd: Re: [Xen-devel] Kernel pv_ops freeze on start, No avai

To: Michal Novotny <minovotn@xxxxxxxxxx>
Subject: Re: Fwd: Re: [Xen-devel] Kernel pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Tue, 2 Mar 2010 09:19:32 +0000
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 02 Mar 2010 01:20:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B8BF6BA.1060203@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <4B8BF6BA.1060203@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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- 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.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>