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

[Sylvain Munaut <s.munaut@xxxxxxxxxxxxxxxxxxxx>]

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.

Interestingly, it seems to avoid the first issue as well ... I guess
this is why nobody hit that before. Although hard rebooting the dom0
might be a severe punishement for a config mistake :p

Cheers & thanks to all.

    Sylvain

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