Bug#603802: 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: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
From: "Artur Linhart" <Artur.Linhart@bcpraha.com>
Date: Thu, 18 Nov 2010 08:35:08 +0100
Message-id: <[🔎] 6D22EEE43B8840E8A700835178099DAE@private.praha.bcpraha.com>
Reply-to: "Artur Linhart" <Artur.Linhart@bcpraha.com>, 603802@bugs.debian.org
In-reply-to:
References: <[🔎] 20101117124532.9808.86594.reportbug@alg-puv-xen-1> <[🔎] 84lj4sp01s.fsf@sauna.l.org>

One more correctlion to my last message - I have figured out, some instances have had still the kernel from version 2.6.32-21 what
was the reason why they started correctly... So it seems the effect can be seen on all DomUs with the kernel from package version
2.6.32-27

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>
- Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart
  - From: Timo Juhani Lindfors <timo.lindfors@iki.fi>

Prev by Date: Bug#599823: linux-2.6: XEN and NFS causes duplicate filenames with large directories
Next by Date: Bug#602418: linux-image-2.6.32-5-xen-amd64: with xen 4.0, fork()/clone() fails with ENOMEM during X startup with nv driver
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#603802: Acknowledgement (linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart)
Index(es):
- Date
- Thread