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-devel

Re: [Xen-devel] Re: Failure to load the most recent 2.6.32.21 pvops unde

To: Bill McGonigle <bill@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Failure to load the most recent 2.6.32.21 pvops under Xen 4.0.1
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Thu, 30 Sep 2010 09:21:45 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 30 Sep 2010 06:23:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CA3AD16.1010007@xxxxxxxxxxxxxxxx>
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>
References: <306337.78392.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <4C9CF5F9.4020005@xxxxxxxx> <4CA3AD16.1010007@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Wed, Sep 29, 2010 at 05:18:14PM -0400, Bill McGonigle wrote:
> On 09/24/2010 03:03 PM, Jeremy Fitzhardinge wrote:
> > > Please don't truncate oops/BUG messages like this.  It removes a lot of
> > > useful information.
> > > 
> > > Dom0 or domU?  32 or 64 bit?  Are you using maxmem?  Can you send a
> > > complete boot log for the domain (or system if dom0)?
> > > 
> > > I suspect this bug has been fixed later on, but hasn't made it into
> > > stable-2.6.32.x yet.
> I think I'm seeing the same thing here.  I'll append a serial log.
> 
> x86_64 dom0
> 
> grub is:

Workaround is to specify dom0_mem=max:2GB (or whatever is half your physical 
memory).

> 
>  kernel /xen.gz dom0_max_vcpus=1 dom0_vcpus_pin loglvl=all guest_loglvl=all 
> com1=9600,8n1 sync_console console_to_ring conring_size=65536 console=com1    
>         
>  module /vmlinuz-2.6.32.21-168.xendom0.fc12.x86_64 ro 
> root=LABEL=librescu-root selinux=0 SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 
> KEYTABLE=us rootflags=data=journal acpi=off earlyprintk=xen console=hvc0 
> nomodeset                                                                     
>                                                  
>  module /initramfs-2.6.32.21-168.xendom0.fc12.x86_64.img
> 

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