Re: [Xen-devel] Xen BUG at mm-locks.h:118 in 4.2.1 - mm locking order violation - Dom0 reboot

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2013-02-18 at 16:31 +0000, Sylvain Munaut wrote:
> Hi Ian,
> 
> >> memory = 1536
> >> maxmem = 2048
> >
> >
> > This is the cause of your second "Dom1 out of PoD memory" bug.
> >
> > If you aren't running at least a balloon driver inside the guest then
> > this isn't valid, since you have requested a different initial memory
> > allocation to what you are actually giving the guest and something needs
> > to bridge that gap. Initially this is PoD but eventually a balloon
> > driver must come along, PoD is not intended for use other than during
> > boot until a balloon driver can be started.
> 
> Indeed this fixed it.

Good.

> Interestingly, it seems to avoid the first issue as well ...

If memory == maxmem then PoD (the crashing subsystem) is never activated
so that is to be expected.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel