[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Re: OpenSUSE 11.2 Xen HVM guest crash causing BUG() in dom0



>>> Pasi KÃrkkÃinen<pasik@xxxxxx> 23.01.10 20:14 >>>
>Just to be more clear, Mike used 2.6.32-41.1 x86_64 kernel from 
>http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.2/x86_64/ 
>
>and it seems he doesn't get BUG() and traceback in dom0 anymore when 
>HVM guest crashes:
>
>http://pastebin.com/m5aff9158 
>
>(XEN) Domain 3 reported crashed by domain 0 on cpu#0:
>
>lots of these still though:
>
>(XEN) domain_crash called from p2m.c:1091
>(XEN) p2m_pod_demand_populate: Out of populate-on-demand memory!
>
>and then
>
>[  233.171451] BUG: soft lockup - CPU#0 stuck for 61s! [qemu-dm:3722]
>
>So I guess that's OK now..

Hmm, OK is probably not the right statement with there still being
lockups. However, I take your wording as the lockups not being
connected to the domain crashes anymore. Disabling C-state
management (cpuidle=0 or max_cstate=0 on the Xen command line)
might be worth trying (based on recent observations reported on
xen-devel).

Of course, fixing the underlying config problem might help the user
even more: Apparently they configure the guest with mem!=maxmem,
and either the balloon driver is not being loaded at all or isn't getting
its target set low enough (we're apparently having the latter problem
in SLE11SP1, so it's not impossible for it to also exist in 11.2).

Jan

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.