From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: guest suspend/resume & virtio: vring errors Date: Sat, 9 Jul 2011 12:55:07 +0300 Message-ID: <20110709095507.GH10249@redhat.com> References: <4E17545E.7010400@msgid.tls.msk.ru> <20110709091720.GG10249@redhat.com> <4E1823AD.2090207@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: KVM list To: Michael Tokarev Return-path: Received: from mx1.redhat.com ([209.132.183.28]:28671 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752504Ab1GIJzN (ORCPT ); Sat, 9 Jul 2011 05:55:13 -0400 Content-Disposition: inline In-Reply-To: <4E1823AD.2090207@msgid.tls.msk.ru> Sender: kvm-owner@vger.kernel.org List-ID: On Sat, Jul 09, 2011 at 01:47:25PM +0400, Michael Tokarev wrote: > 09.07.2011 13:17, Gleb Natapov wrote: > > On Fri, Jul 08, 2011 at 11:02:54PM +0400, Michael Tokarev wrote: > >> I tried suspend/resume cycle for a linux guest > >> today, with 100% failure result. There are 2 > > Good. It works as expect :) Linux virtio drivers do not support PM. > > This means that neither in-guest suspend/resume nor > qemu-kvm migrate-to-file (which fails for a different > reason I'm trying to debug now) works. Which is very > unfortunate. > Migration to file should work, or, at least, is a different problem. It does not require guest cooperation. > >> With e1000 instead of virtio-net-pci, the suspend > >> does not complete - guest kernel freezes after the > >> message "Suspending console(s)" and does not respond > >> (but does not eat 100% CPU either) - the same as for > >> older guest kernel. > >> > >> Has anyone succeeded suspend/resume cycle? > >> > > Yes, but Linux and suspend/resume are not best friends. Sometimes it > > works by mistake, but next merged patch fixes it and suspend/resume > > returns to its normal broken state. > > Lovelylovely. > > It does not work with any version of windows I tried, too > (which is winXP, win7 32 and win7 64bits). Windows enters > an endless loop with a black screen during suspend (eating > 100% CPU time). > Heh. Is this S4 or S3 suspend resume? Looks like recent breakage. The only knows problem to me is in win7/2008 S3 resume + net. > What's wrong/broken in linux? Can it be fixed? > Complete lack of regression testing. -- Gleb.