Update:
Sadly the my productive system froze in the early afternoon today again
with the older kernel as well (4.9.30-2+deb9u5). so that wasn't a temp
workaround. Paradoxically nothing showed up on the xl console (within a
screen) at dom0. No errors, nothing, the vm just stopped responding. As
I was monitoring the system, there where still two open shell
connections. Some basic stuff still worked, but as soon as tried to open
a file, the shell got unresponsive. I tried a shutdown on the other
shell, but that didn't got very far.
Searching the net for that issue I found this post at the xen project
mailing list:
https://lists.xen.org/archives/html/xen-users/2017-07/msg00057.html
which sounds similar. He got some traces out of it, but no answer on the
mailing list.
Some information about my setup:
hardware:
xeon E5-2620 v4
board supermicro X10SRi-F
32gb ecc ram
two 10tb server disk
two I350 network adapter (onboard)
dom0:
debian stretch (up to date), kernel 4.9.51-1, xen-hypervisor
4.8.1-1+deb9u3,
the two network as adapter as a bond in a bridge
the discs: gpt, 4 part (1M, 256M esp, 256M md mirror with boot, rest as
md mirror for lvm)
domu:
memory: 8192, 2 vcpus
uses a network interface on the bridge
several (thin)lvm volumes as phys devices
debian stretch (up to date)
issue with both kernel versions: 4.9.30-2+deb9u5 and 4.9.51-1
Some other domu's (wheezy, jessie and a windows 7) seem to run fine
Next I'll try some newer kernels for the domu, starting with the stretch
backport kernels.
