Yes, it seems to be the same bug. I have figured out, I made a mistake, the statement "xm unpause" does not help. But I have a little bit other behavior - I have more DomUs and some from them were restored and started correctly, some not. I cannot recognize any general difference between them...
Unfortunately, I will not have the chance to test the patch directly, I use vanilla kernel from the package only... -----Original Message----- From: Timo Juhani Lindfors [mailto:timo.lindf...@iki.fi] Sent: Wednesday, November 17, 2010 2:11 PM To: Artur Linhart Cc: 603...@bugs.debian.org Subject: Re: Bug#603802: linux-image-2.6.32-5-xen-amd64: DomU not really resumed (hangs) after restore from disk after Dom0 restart Artur Linhart <al.li...@bcpraha.com> writes: > If the kernel is used for paravirtual DomU, then the DomU is > normally started orshutdown. Ifthe xm save and xm restore is invoked > explicitely,then the DomU also restores normally. Only in the case > the DomU is restored automatically via xendomains script facility on > Dom0 start it is restored, so visible in the list This is most likely a duplicate of my bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602273 Can you please test the patch that is included in that bug report? __________ Informace od NOD32 5626 (20101117) __________ Tato zprava byla proverena antivirovym systemem NOD32. http://www.nod32.cz -- 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/d8023ff3bde644b4a700ae12bbcb0...@private.praha.bcpraha.com
