Additional info - I figured out, the domain is paused only, so after calling of
xm unpause <DomId>
the domain continues to respond and to run.

So, maybe it is not a bug, but a feature?

If it is so, then there should be a possibility to start the domain immediatelly.

One more remark: It does not affect the fully virtualized domains, only the paravirtualized domains.





--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 3853B9555C184C2C84ACFEE6367EBB71@private.praha.bcp raha.com">http://lists.debian.org/3853B9555C184C2C84ACFEE6367EBB71@private.praha.bcp raha.com