WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Boot errors on RHEL 4.1 system

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Boot errors on RHEL 4.1 system
From: Brian Koontz <brian@xxxxxxxxxxxxx>
Date: Mon, 15 May 2006 09:23:46 -0500
Delivery-date: Mon, 15 May 2006 08:23:32 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <22705635.2191147442080345.JavaMail.root@zimbra>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <22705635.2191147442080345.JavaMail.root@zimbra>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.5.1i
> The other issue is that the module errors you're seeing look like
> their coming from long after the initrd is loaded, they look like
> they are coming after boot more or less, which means the kernel
> modules themselves are having problems, not the initrd. Could be
> wrong, since I don't have the entire outpout of the boot sequence,
> but its a guess. 

Any way to capture the output?  Other suggestions?  I think I'm close,
just not quite there yet!

  --Brian

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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