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-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3853b9555c184c2c84acfee6367eb...@private.praha.bcpraha.com
