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. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
