Sure. libvmi is linear, however, once the call to xen happens, that vm is latched and will have the flag injected into the control block. That is outside of the execution path of libvmi. The next instruction boundary the VM hits and executes will cause an event to be dispatched.  I don't want an event to come through, pausing the vcpu of the VM, and then not have a handler to take care of the event on the ring. This will leave the vcpu in a paused state until the ring is flushed. Am i thinking about this incorrectly?