Yes, this domain has: - Current memory allocation: 8192 MB - Maximum memory allocation: 10240 MB.
I have changed the maximum to 8192 MB as a possible workaround; the current memory is rarely up/down scaled anyway. The PVH setting for dom0 has been removed. If you don't here from me anymore, then this is the workaround. :) Thanks in advance. On 30 October 2017 at 09:37, Juergen Gross <jgr...@suse.com> wrote: > On 30/10/17 09:05, Arthur Borsboom wrote: > > Hi Juergen, > > > > I needed to wait until the VM guest crashed again, so that caused this > > delay. > > I have extracted the hypervisor dmesg and the dom0 dmesg which can be > > found in the PasteBins. > > It is always the same domain crashing, if that is of any help. > > > > Xen hypervisor dmesg: https://pastebin.com/Y9fv0Ey0 > > Aah, interesting. Do you happen to configure your domains with maxmem= > larger than memory= ? > > I'm asking because the error messages seem to be related to another > problem introduced in kernel 4.13 which is fixed in 4.14. This problem > should be avoidable by setting maxmem= to the same value as memory= > in the domain config of HVM domains. > > BTW: your hypervisor parameters are containing "dom0pvh=1". You should > remove it as PVH support has been reworked and is not yet working for > dom0. > > > Juergen > -- Arthur Borsboom Mob: +31629089953 Email: arthurborsb...@gmail.com [image: View Arthur's LinkedIn profile] <http://uk.linkedin.com/in/arthurborsboom>
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
