Fajar,
thanks for your comments on this.
Here some explanatory notes concerning the case:
I thought it would be a good idea to have the base for production xen-servers
on a stable distribution with presumable stable packages installed, instead of
compiling my own.
In the past I used to compile the needed xen dom0 kernel on top of Centos 5.x
or Fedora but stumbled on not to be compliant to distribution specific update
methods anymore.
Especially compiling new xen kernels on top of the old 2.6.18 kernel in Centos
5.x was a pain. So I switched to Debian Squeeze which has the reputation to be
the distribution with the most actual xen packages integrated.
Another reason for choosing a presumable stable distribution was the long time
support (LTS) one would get...
I will have a closer look on your provided link and hopefully, it will lead to
a stable system with newest and stable xen-kernel, which leaves other installed
packages still uptadeable through distribution specific methods.
regards,
Guido
-----Ursprüngliche Nachricht-----
Von: Fajar A. Nugraha [mailto:list@xxxxxxxxx]
Gesendet: Mittwoch, 23. Februar 2011 09:31
An: Guido Hecken
Cc: Konrad Rzeszutek Wilk; xen-devel@xxxxxxxxxxxxxxxxxxx; Pasi Kärkkäinen
Betreff: Re: [Xen-devel] [Xen-dev] kernel BUG at arch/x86/xen/mmu.c:1860!
On Mon, Feb 21, 2011 at 11:28 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Mon, Feb 21, 2011 at 11:15:39AM -0500, Konrad Rzeszutek Wilk wrote:
>> On Mon, Feb 21, 2011 at 02:58:53PM +0100, Guido Hecken wrote:
>> > Pasi,
>> > thanks for the quick response.
>> >
>> > As mentioned in previous posts, creating and afterwards deleting snapshots
>> > crashes the system.
>> > I can do the following commands only twice, max. three times, before the
>> > server crashes.
>>
>> You need these two patches:
>>
>> b2464c422fb44275deeb5770b668351860f68e0e
>> "x86: hold mm->page_table_lock while doing vmalloc_sync"
>> a8bf92faf72dba6e0dd2130256cb81c3e68f672b
>> "vmalloc: eagerly clear ptes on vunmap".
>>
>
> Sounds like someone should open a bugreport to debian
> to add these patches to their kernel.
>
> Those patches have been in xen/stable-2.6.32.x branch for around 5 months..
It might not be those patches that fixed the bug.
I was testing latest xen/stable-2.6.32.x (currently at 2.6.32.27,
definitely has those patches) with zvol when I got the bug, which
manifests itself when starting 4 domUs at boot using xendomains
service. So I tried xen/next-2.6.32 (which was just updated to
2.6.32.28), works fine so far.
So to Guido, if you have time, please try using both
xen/stable-2.6.32.x and xen/next-2.6.32 to verify which version can
solve your problem. Regarding your concern about non-standard systems,
"make-kpkg" might help
(http://newbiedoc.sourceforge.net/system/kernel-pkg.html).
--
Fajar
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home