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

[Xen-users] Xen 4.1.1 crash when manipulating cpupools.

Hi all!

I've been trying to make use of the credit2 scheduler for my guests running real-time (audio) applications, and to facilitate this I'm using cpupools to separate Domain-0 and less time critical guests which run fine under the regular credit scheduler, and the others which need to use credit2.  However, I seem to be able to reliably crash the hypervisor when I try to move virtual cpus (hyperthreads) or domains between cpupools.  Sometimes it even crashes when I simply try to set the credit2 scheduler weight for a domain.  All domains are fully virtualized and running CentOS 5.  Dom-0 is running Fedora 13 with pvops kernel.

The panic message displays a register dump and stack trace, as well as:
(XEN) Panic on CPU 0:
(XEN) Xen BUG at sched_credit.c:991

Hardware is a Dell R810 server with one 10-core Xeon E7, 128 GB RAM and the guests reside on NAS storage. 

If I simply use Pool-0 for everything and set the default scheduler to credit2 in the Xen boot string everything runs fine, but this workaround is not ideal since it removes some flexibility for me.

Any ideas where I should look to determine how to resolve this?


Xen-users mailing list



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