[Pkg-xen-devel] no kernel events on domU creation/failed multicalls

Ferenc Wagner wferi at niif.hu
Mon Mar 7 19:17:04 UTC 2011


Bastian Blank <waldi at debian.org> writes:

> On Fri, Mar 04, 2011 at 04:42:42PM +0100, Ferenc Wagner wrote:
>> I'm pretty uncertain about what to do now or how to gain deeper insight
>> should the problem reappear.  Ideas more than welcome.
>
> You are using bonding? Please test without, I heard about too much
> problems with this.

Hi Bastian,

Thanks for your reply.  I guess you're talking about the final

BUG: scheduling while atomic: ifenslave/11862/0x00000100

part?  That's what concerns me the least (during shutdown the network is
already down anyway), the failed multicalls during bootup are more
worrying.  I could certainly test without bonding, if I could reproduce
this thing.  The problem is that this was a production virtualization
cluster under lenny (with the sarge dom0 kernel and with the same
bonding), which I upgraded, and which exhibits erratic behaviour since
then.  I will certainly stress this system further tomorrow, trying to
reproduce either problem (the missing kernel events, the failed
multicalls or the shutdown bug), do you think the former two could also
be affected by bonding?

Early testing also showed migration problems (flood of "BUG: recent
printk recursion" messages on the migrated domU), which I'm about to
investigate, but in case some wisdom is already collected, I'd be glad
to listen.
-- 
Thanks,
Feri.



More information about the Pkg-xen-devel mailing list