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] 2.6.29-rc7 pv_ops dom0 BUG / unable to handle kernel pag

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] 2.6.29-rc7 pv_ops dom0 BUG / unable to handle kernel paging request
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sat, 21 Mar 2009 22:16:52 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 21 Mar 2009 13:17:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49C3DC02.7010903@xxxxxxxx>
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: <20090307175856.GL15052@xxxxxxxxxxxxxxx> <49B3610C.2090101@xxxxxxxx> <20090308115400.GR15052@xxxxxxxxxxxxxxx> <20090311205250.GJ15052@xxxxxxxxxxxxxxx> <20090311212622.GK15052@xxxxxxxxxxxxxxx> <49B84BE8.4020103@xxxxxxxx> <20090312083242.GM15052@xxxxxxxxxxxxxxx> <49C3DC02.7010903@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Fri, Mar 20, 2009 at 11:10:10AM -0700, Jeremy Fitzhardinge wrote:
> Pasi Kärkkäinen wrote:
> >Ok. I'll try that later.. I'll be away for 1,5 weeks (going to a 
> >vacation), so can't try right now. 
> >
> >One difference just came to my mind.. when booted on baremetal, whole 2G of
> >ram is available.. when booted as dom0 I've limited dom0 memory to 1G. 
> >  
> 
> That shouldn't be necessary any more.
> 

Ok. I'm just used to always limiting dom0 memory to avoid ballooning :)

> >I guess I should try with the same amount of memory available for both
> >dom0 and baremetal.
> >  
> 
> I would expect the results to be the same, though the xen case might 
> fail more readily.
> 

Baremetal is not failing.. ie. I don't see this BUG when I run the same
kernel on baremetal.  

> Also, do you see this problem before you've started any other domains?  
> Or does it only happen once you've run a domU (or only while a domU is 
> running)?
> 

I'm not running any other domains.. Only dom0 is running.

Steps to reproduce this BUG on my pv_ops dom0 testbox:

1) Reboot the box to pv_ops dom0 kernel
2) Login to dom0 via ssh
3) Start kernel compilation on dom0 (make bzImage && make modules)
4) Wait some minutes and pv_ops dom0 kernel BUGs

So no other domains has been or is running when this happens..

I'll try disabling CONFIG_HIGHPTE now, and see if that makes any difference.

-- Pasi

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

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