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


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

To: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Fwd: Re: [Xen-devel] Kernel pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!
From: Michal Novotny <minovotn@xxxxxxxxxx>
Date: Mon, 01 Mar 2010 18:17:46 +0100
Delivery-date: Mon, 01 Mar 2010 09:18:47 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20091209 Fedora/3.0-3.fc11 Thunderbird/3.0
On 03/01/2010 03:25 PM, Ian Campbell wrote:

 On Mon, 2010-03-01 at 14:21 +0000, Michal Novotny wrote:

 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.


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.


Michal Novotny<minovotn@xxxxxxxxxx>, RHCE
Virtualization Team (xen userspace), Red Hat

Xen-devel mailing list

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