Comment 11 for bug 1741409

I was able to observe the crash on a Ubuntu Xenial Xen host which produced the following text on the host console:

(XEN) domain_crash called from hpet.c:387
(XEN) Domain 2 (vcpu#1) crashed on cpu#4:
(XEN) ----[ Xen-4.6.5 x86_64 debug=n Not tainted ]----
(XEN) CPU: 4
(XEN) RIP: 0010:[<ffffffff81532dc1>]
(XEN) RFLAGS: 0000000000010002 CONTEXT: hvm guest (d2v1)
(XEN) rax: 0000000000000032 rbx: ffff880034e41a00 rcx: 0000000000000000
(XEN) rdx: 0000000000000001 rsi: 0000000000000032 rdi: ffffffff821fdfb0
(XEN) rbp: ffff8800e90afc10 rsp: ffff8800e90afbd8 r8: 0000000000000003
(XEN) r9: 0000000000000000 r10: 000000000000000a r11: 0000000000000000
(XEN) r12: ffff880107a4a8f8 r13: ffffffff821fdfb0 r14: ffffc90000002140
(XEN) r15: ffffffff81a7c600 cr0: 0000000080050033 cr4: 0000000000360670
(XEN) cr3: 000000003492c000 cr2: 00007fcc1156a030
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0018 cs: 0010

Will investigate further (whether this persists in newer xen versions)