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 Dom0 dmesg: https://pastebin.com/CekF7Vhs Hopefully you can find a workaround as long as the patch (kernel 4.14) has not reached our VM Host. Best regards, Arthur. On 28 October 2017 at 09:54, Juergen Gross <jgr...@suse.com> wrote: > On 28/10/17 09:34, Arthur Borsboom wrote: > > Hi Juergen, > > > > I have noticed that a patch has been developed an awaits the upcoming > > Linux kernel 4.14, maybe 4.15. > > In the mean time the server keeps crashing about every 2 days. > > > > Do you know a workaround I can apply? > > Depends on why this happened. > > Can you please look whether there is any hypervisor message issued > at the time of the fault? You might need to set hypervisor boot > parameters "loglvl=all guest_loglvl=all". In case dom0 is still > running you can see the hypervisor messages by running "xl dmesg" > in 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
