On 30/07/15 14:12, Paul Durrant wrote: >> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1. >> (XEN) domain_crash called from io.c:166 >> (XEN) d19v0 weird emulation state 1 >> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1. >> (XEN) domain_crash called from io.c:166 >> (XEN) d19v0 weird emulation state 1 >> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1. >> (XEN) domain_crash called from io.c:166 >> > Hmm. Can't understand how that's happening... handle_pio() shouldn't be > called unless the state is STATE_IORESP_READY and yet the inner function is > hitting the default case in the switch.
Sounds like something is changing the state between the two checks. Is this shared memory writeable by qemu? ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
