All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Gleb Natapov <gleb@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: guest suspend/resume & virtio: vring errors
Date: Sat, 09 Jul 2011 13:47:25 +0400	[thread overview]
Message-ID: <4E1823AD.2090207@msgid.tls.msk.ru> (raw)
In-Reply-To: <20110709091720.GG10249@redhat.com>

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.

>> 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).

What's wrong/broken in linux?  Can it be fixed?

Thanks,

/mjt

  reply	other threads:[~2011-07-09  9:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 19:02 guest suspend/resume & virtio: vring errors Michael Tokarev
2011-07-09  9:17 ` Gleb Natapov
2011-07-09  9:47   ` Michael Tokarev [this message]
2011-07-09  9:55     ` Gleb Natapov
2011-07-09 10:09       ` Michael Tokarev
2011-07-09 10:36         ` Gleb Natapov
2011-07-09 11:54           ` Michael Tokarev
2011-07-09 12:07             ` Gleb Natapov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E1823AD.2090207@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.