Bug#603802: Acknowledgement (linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart)

To: <603802@bugs.debian.org>
Subject: Bug#603802: Acknowledgement (linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart)
From: "Artur Linhart - Linux communication" <AL.LINUX@bcpraha.com>
Date: Wed, 17 Nov 2010 14:16:05 +0100
Message-id: <[🔎] 3853B9555C184C2C84ACFEE6367EBB71@private.praha.bcpraha.com>
Reply-to: "Artur Linhart - Linux communication" <AL.LINUX@bcpraha.com>, 603802@bugs.debian.org
In-reply-to: <handler.603802.B.128999794318350.ack@bugs.debian.org>
References: <[🔎] 20101117124532.9808.86594.reportbug@alg-puv-xen-1> <handler.603802.B.128999794318350.ack@bugs.debian.org>

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.

Reply to:

References:
- Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
  - From: Artur Linhart <al.linux@bcpraha.com>

Prev by Date: Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
Next by Date: Bug#603811: linux-image-2.6.26-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds)
Previous by thread: Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
Next by thread: Bug#603811: linux-image-2.6.26-amd64: SCHED_IDLE issues (tasks blocked for more than 120 seconds)
Index(es):
- Date
- Thread