* xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
@ 2015-07-24 18:56 linux
2015-07-24 19:27 ` Sander Eikelenboom
2015-07-27 14:07 ` Andrew Cooper
0 siblings, 2 replies; 8+ messages in thread
From: linux @ 2015-07-24 18:56 UTC (permalink / raw)
To: xen-devel
Hi All,
On my AMD system running xen-unstable (last commit: ),
after a few restarts of a HVM guest with pci-passthrough i got these on
shutdown of the guest:
(never seen this before, so it should be something triggered by a recent
commit)
--
Sander
.... (probably lost before but that's lost)
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] MMIO emulation failed: d23v0 64bit @
0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
status 1.
(XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
(XEN) [2015-07-24 18:46:53.733] MMIO emulation failed: d23v0 64bit @
0010:ffffffff814e1acf -> 0f b7 11 74 09 83 3d cd 58 eb 00 ff 74 01 c3 89
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
2015-07-24 18:56 xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8 linux
@ 2015-07-24 19:27 ` Sander Eikelenboom
2015-07-27 14:07 ` Andrew Cooper
1 sibling, 0 replies; 8+ messages in thread
From: Sander Eikelenboom @ 2015-07-24 19:27 UTC (permalink / raw)
To: linux; +Cc: xen-devel
Friday, July 24, 2015, 8:56:02 PM, you wrote:
> Hi All,
> On my AMD system running xen-unstable (last commit: ),
> after a few restarts of a HVM guest with pci-passthrough i got these on
> shutdown of the guest:
> (never seen this before, so it should be something triggered by a recent
> commit)
> --
> Sander
Hmm it seems the guest still had the:
mmio_hole=3072
In the config, perphaps that conflicts with for instance
b730fc3e157a7b401305cecad7fcefee28340e2c
"hvmloader/pci: try to avoid placing BARs in RMRRs"
Although the commit message seems to indicate it shouldn't conflict:
"- If mmio_hole_size is not specified, and the existing MMIO range has
RMRRs in it, and there is space to expand the hole in lowmem without
moving more memory, then make the MMIO hole as large as possible."
> .... (probably lost before but that's lost)
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] MMIO emulation failed: d23v0 64bit @
> 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.733] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.733] MMIO emulation failed: d23v0 64bit @
> 0010:ffffffff814e1acf -> 0f b7 11 74 09 83 3d cd 58 eb 00 ff 74 01 c3 89
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
2015-07-24 18:56 xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8 linux
2015-07-24 19:27 ` Sander Eikelenboom
@ 2015-07-27 14:07 ` Andrew Cooper
2015-07-27 14:22 ` Paul Durrant
` (2 more replies)
1 sibling, 3 replies; 8+ messages in thread
From: Andrew Cooper @ 2015-07-27 14:07 UTC (permalink / raw)
To: linux, xen-devel; +Cc: Paul Durrant
On 24/07/15 19:56, linux@eikelenboom.it wrote:
> Hi All,
>
> On my AMD system running xen-unstable (last commit: ),
> after a few restarts of a HVM guest with pci-passthrough i got these
> on shutdown of the guest:
> (never seen this before, so it should be something triggered by a
> recent commit)
>
> --
> Sander
>
>
> .... (probably lost before but that's lost)
>
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> status 1.
Paul: this is very likely an issue your emulation series.
66 89 02 is mov %ax,(%rdx), but has ended up in handle_pio() which seems
wrong.
Sander: Please can you rerun with the following debug
diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c
index d3b9cae..7560d08 100644
--- a/xen/arch/x86/hvm/io.c
+++ b/xen/arch/x86/hvm/io.c
@@ -163,7 +163,9 @@ int handle_pio(uint16_t port, unsigned int size, int
dir)
break;
default:
gdprintk(XENLOG_ERR, "Weird HVM ioemulation status %d.\n", rc);
- domain_crash(curr->domain);
+ show_execution_state(curr);
+ dump_execution_state();
+ domain_crash_synchronous(curr->domain);
break;
}
~Andrew
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
2015-07-27 14:07 ` Andrew Cooper
@ 2015-07-27 14:22 ` Paul Durrant
2015-07-27 14:44 ` Sander Eikelenboom
2015-07-28 21:16 ` linux
2 siblings, 0 replies; 8+ messages in thread
From: Paul Durrant @ 2015-07-27 14:22 UTC (permalink / raw)
To: Andrew Cooper, linux, xen-devel
> -----Original Message-----
> From: Andrew Cooper [mailto:andrew.cooper3@citrix.com]
> Sent: 27 July 2015 15:08
> To: linux@eikelenboom.it; xen-devel@lists.xen.org
> Cc: Paul Durrant
> Subject: Re: [Xen-devel] xen-unstabel + linux 4.2: MMIO emulation failed:
> d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89
> 65 c8 e8
>
> On 24/07/15 19:56, linux@eikelenboom.it wrote:
> > Hi All,
> >
> > On my AMD system running xen-unstable (last commit: ),
> > after a few restarts of a HVM guest with pci-passthrough i got these
> > on shutdown of the guest:
> > (never seen this before, so it should be something triggered by a
> > recent commit)
> >
> > --
> > Sander
> >
> >
> > .... (probably lost before but that's lost)
> >
> > (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> > (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> > status 1.
> > (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> > (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> > status 1.
> > (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> > (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> > status 1.
>
> Paul: this is very likely an issue your emulation series.
>
> 66 89 02 is mov %ax,(%rdx), but has ended up in handle_pio() which seems
> wrong.
>
It suggests that the MMIO emulation failure did not clean up and thus the subsequent handle_pio() found the state machine in a bad state.
Paul
> Sander: Please can you rerun with the following debug
>
> diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c
> index d3b9cae..7560d08 100644
> --- a/xen/arch/x86/hvm/io.c
> +++ b/xen/arch/x86/hvm/io.c
> @@ -163,7 +163,9 @@ int handle_pio(uint16_t port, unsigned int size, int
> dir)
> break;
> default:
> gdprintk(XENLOG_ERR, "Weird HVM ioemulation status %d.\n", rc);
> - domain_crash(curr->domain);
> + show_execution_state(curr);
> + dump_execution_state();
> + domain_crash_synchronous(curr->domain);
> break;
> }
>
> ~Andrew
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
2015-07-27 14:07 ` Andrew Cooper
2015-07-27 14:22 ` Paul Durrant
@ 2015-07-27 14:44 ` Sander Eikelenboom
2015-07-28 21:16 ` linux
2 siblings, 0 replies; 8+ messages in thread
From: Sander Eikelenboom @ 2015-07-27 14:44 UTC (permalink / raw)
To: Andrew Cooper; +Cc: Paul Durrant, xen-devel
Monday, July 27, 2015, 4:07:39 PM, you wrote:
> On 24/07/15 19:56, linux@eikelenboom.it wrote:
>> Hi All,
>>
>> On my AMD system running xen-unstable (last commit: ),
>> after a few restarts of a HVM guest with pci-passthrough i got these
>> on shutdown of the guest:
>> (never seen this before, so it should be something triggered by a
>> recent commit)
>>
>> --
>> Sander
>>
>>
>> .... (probably lost before but that's lost)
>>
>> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
>> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
>> status 1.
>> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
>> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
>> status 1.
>> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
>> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
>> status 1.
> Paul: this is very likely an issue your emulation series.
> 66 89 02 is mov %ax,(%rdx), but has ended up in handle_pio() which seems
> wrong.
> Sander: Please can you rerun with the following debug
Well i have only seen this once now .. hasn't happened again so far, so
it's not very reproduceable i'm afraid.
I can see when i can make some time to run a script that does a loop
on creating and shutting down a guest with pci-passthrough, see if i can
get it to fail again.
--
Sander
> diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c
> index d3b9cae..7560d08 100644
> --- a/xen/arch/x86/hvm/io.c
> +++ b/xen/arch/x86/hvm/io.c
> @@ -163,7 +163,9 @@ int handle_pio(uint16_t port, unsigned int size, int
> dir)
> break;
> default:
> gdprintk(XENLOG_ERR, "Weird HVM ioemulation status %d.\n", rc);
> - domain_crash(curr->domain);
> + show_execution_state(curr);
> + dump_execution_state();
> + domain_crash_synchronous(curr->domain);
> break;
> }
> ~Andrew
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
2015-07-27 14:07 ` Andrew Cooper
2015-07-27 14:22 ` Paul Durrant
2015-07-27 14:44 ` Sander Eikelenboom
@ 2015-07-28 21:16 ` linux
2015-07-29 9:06 ` Paul Durrant
2 siblings, 1 reply; 8+ messages in thread
From: linux @ 2015-07-28 21:16 UTC (permalink / raw)
To: Andrew Cooper; +Cc: Paul Durrant, xen-devel
On 2015-07-27 16:07, Andrew Cooper wrote:
> On 24/07/15 19:56, linux@eikelenboom.it wrote:
>> Hi All,
>>
>> On my AMD system running xen-unstable (last commit: ),
>> after a few restarts of a HVM guest with pci-passthrough i got these
>> on shutdown of the guest:
>> (never seen this before, so it should be something triggered by a
>> recent commit)
>>
>> --
>> Sander
>>
>>
>> .... (probably lost before but that's lost)
>>
>> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
>> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
>> status 1.
>> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
>> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
>> status 1.
>> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
>> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
>> status 1.
>
> Paul: this is very likely an issue your emulation series.
>
> 66 89 02 is mov %ax,(%rdx), but has ended up in handle_pio() which
> seems
> wrong.
>
> Sander: Please can you rerun with the following debug
>
> diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c
> index d3b9cae..7560d08 100644
> --- a/xen/arch/x86/hvm/io.c
> +++ b/xen/arch/x86/hvm/io.c
> @@ -163,7 +163,9 @@ int handle_pio(uint16_t port, unsigned int size,
> int
> dir)
> break;
> default:
> gdprintk(XENLOG_ERR, "Weird HVM ioemulation status %d.\n",
> rc);
> - domain_crash(curr->domain);
> + show_execution_state(curr);
> + dump_execution_state();
> + domain_crash_synchronous(curr->domain);
> break;
> }
>
> ~Andrew
Hi Andrew,
I tried your debug patch, however that doesn't print anything new to xl
dmesg.
It seems to be too busy trying to crash .. (although that actually seems
to fail)
This was testing on a tree with a619657e2d5725a61cb72f65901db42e98f2a896
as last commit and it fails at the first shutdown of the guest.
After that i tried it with the current staging tree with
44313ab77f3e3c5b566ea4f23b0e32bfd5eafa29 as last commit
and i don't to get those failures anymore .. i even done a start
shutdown loop of 100 iterations .. everything was fine.
--
Sander
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
2015-07-28 21:16 ` linux
@ 2015-07-29 9:06 ` Paul Durrant
2015-07-29 11:11 ` Sander Eikelenboom
0 siblings, 1 reply; 8+ messages in thread
From: Paul Durrant @ 2015-07-29 9:06 UTC (permalink / raw)
To: linux, Andrew Cooper; +Cc: xen-devel
> -----Original Message-----
> From: linux@eikelenboom.it [mailto:linux@eikelenboom.it]
> Sent: 28 July 2015 22:16
> To: Andrew Cooper
> Cc: xen-devel@lists.xen.org; Paul Durrant
> Subject: Re: [Xen-devel] xen-unstabel + linux 4.2: MMIO emulation failed:
> d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89
> 65 c8 e8
>
> On 2015-07-27 16:07, Andrew Cooper wrote:
> > On 24/07/15 19:56, linux@eikelenboom.it wrote:
> >> Hi All,
> >>
> >> On my AMD system running xen-unstable (last commit: ),
> >> after a few restarts of a HVM guest with pci-passthrough i got these
> >> on shutdown of the guest:
> >> (never seen this before, so it should be something triggered by a
> >> recent commit)
> >>
> >> --
> >> Sander
> >>
> >>
> >> .... (probably lost before but that's lost)
> >>
> >> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> >> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> >> status 1.
> >> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> >> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> >> status 1.
> >> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
> >> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
> >> status 1.
> >
> > Paul: this is very likely an issue your emulation series.
> >
> > 66 89 02 is mov %ax,(%rdx), but has ended up in handle_pio() which
> > seems
> > wrong.
> >
> > Sander: Please can you rerun with the following debug
> >
> > diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c
> > index d3b9cae..7560d08 100644
> > --- a/xen/arch/x86/hvm/io.c
> > +++ b/xen/arch/x86/hvm/io.c
> > @@ -163,7 +163,9 @@ int handle_pio(uint16_t port, unsigned int size,
> > int
> > dir)
> > break;
> > default:
> > gdprintk(XENLOG_ERR, "Weird HVM ioemulation status %d.\n",
> > rc);
> > - domain_crash(curr->domain);
> > + show_execution_state(curr);
> > + dump_execution_state();
> > + domain_crash_synchronous(curr->domain);
> > break;
> > }
> >
> > ~Andrew
>
>
> Hi Andrew,
>
> I tried your debug patch, however that doesn't print anything new to xl
> dmesg.
> It seems to be too busy trying to crash .. (although that actually seems
> to fail)
>
> This was testing on a tree with a619657e2d5725a61cb72f65901db42e98f2a896
> as last commit and it fails at the first shutdown of the guest.
>
> After that i tried it with the current staging tree with
> 44313ab77f3e3c5b566ea4f23b0e32bfd5eafa29 as last commit
> and i don't to get those failures anymore .. i even done a start
> shutdown loop of 100 iterations .. everything was fine.
>
Good. I can't see anything particularly relevant in the range between those two commits, but it doesn't sound like it's anything to do with my emulation series.
Paul
> --
> Sander
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8
2015-07-29 9:06 ` Paul Durrant
@ 2015-07-29 11:11 ` Sander Eikelenboom
0 siblings, 0 replies; 8+ messages in thread
From: Sander Eikelenboom @ 2015-07-29 11:11 UTC (permalink / raw)
To: Paul Durrant; +Cc: Andrew Cooper, xen-devel
Wednesday, July 29, 2015, 11:06:37 AM, you wrote:
>> -----Original Message-----
>> From: linux@eikelenboom.it [mailto:linux@eikelenboom.it]
>> Sent: 28 July 2015 22:16
>> To: Andrew Cooper
>> Cc: xen-devel@lists.xen.org; Paul Durrant
>> Subject: Re: [Xen-devel] xen-unstabel + linux 4.2: MMIO emulation failed:
>> d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89
>> 65 c8 e8
>>
>> On 2015-07-27 16:07, Andrew Cooper wrote:
>> > On 24/07/15 19:56, linux@eikelenboom.it wrote:
>> >> Hi All,
>> >>
>> >> On my AMD system running xen-unstable (last commit: ),
>> >> after a few restarts of a HVM guest with pci-passthrough i got these
>> >> on shutdown of the guest:
>> >> (never seen this before, so it should be something triggered by a
>> >> recent commit)
>> >>
>> >> --
>> >> Sander
>> >>
>> >>
>> >> .... (probably lost before but that's lost)
>> >>
>> >> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
>> >> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
>> >> status 1.
>> >> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
>> >> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
>> >> status 1.
>> >> (XEN) [2015-07-24 18:46:53.732] domain_crash called from io.c:166
>> >> (XEN) [2015-07-24 18:46:53.732] io.c:165:d23v0 Weird HVM ioemulation
>> >> status 1.
>> >
>> > Paul: this is very likely an issue your emulation series.
>> >
>> > 66 89 02 is mov %ax,(%rdx), but has ended up in handle_pio() which
>> > seems
>> > wrong.
>> >
>> > Sander: Please can you rerun with the following debug
>> >
>> > diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c
>> > index d3b9cae..7560d08 100644
>> > --- a/xen/arch/x86/hvm/io.c
>> > +++ b/xen/arch/x86/hvm/io.c
>> > @@ -163,7 +163,9 @@ int handle_pio(uint16_t port, unsigned int size,
>> > int
>> > dir)
>> > break;
>> > default:
>> > gdprintk(XENLOG_ERR, "Weird HVM ioemulation status %d.\n",
>> > rc);
>> > - domain_crash(curr->domain);
>> > + show_execution_state(curr);
>> > + dump_execution_state();
>> > + domain_crash_synchronous(curr->domain);
>> > break;
>> > }
>> >
>> > ~Andrew
>>
>>
>> Hi Andrew,
>>
>> I tried your debug patch, however that doesn't print anything new to xl
>> dmesg.
>> It seems to be too busy trying to crash .. (although that actually seems
>> to fail)
>>
>> This was testing on a tree with a619657e2d5725a61cb72f65901db42e98f2a896
>> as last commit and it fails at the first shutdown of the guest.
>>
>> After that i tried it with the current staging tree with
>> 44313ab77f3e3c5b566ea4f23b0e32bfd5eafa29 as last commit
>> and i don't to get those failures anymore .. i even done a start
>> shutdown loop of 100 iterations .. everything was fine.
>>
> Good. I can't see anything particularly relevant in the range between those two commits, but it doesn't sound like it's anything to do with my emulation series.
> Paul
Well one thing i still find weird is why didn't the domain crash properly ?
>> --
>> Sander
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2015-07-29 11:11 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-24 18:56 xen-unstabel + linux 4.2: MMIO emulation failed: d23v0 64bit @ 0010:ffffffff814e2b1c -> 66 89 02 48 8d 55 c0 48 89 5d c0 44 89 65 c8 e8 linux
2015-07-24 19:27 ` Sander Eikelenboom
2015-07-27 14:07 ` Andrew Cooper
2015-07-27 14:22 ` Paul Durrant
2015-07-27 14:44 ` Sander Eikelenboom
2015-07-28 21:16 ` linux
2015-07-29 9:06 ` Paul Durrant
2015-07-29 11:11 ` Sander Eikelenboom
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).