From: Chris Dunlop <chris@onthe.net.au>
To: "Marcin Gibuła" <m.gibula@beyond.pl>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Unresponsive linux guest once migrated
Date: Fri, 28 Mar 2014 10:59:18 +1100 [thread overview]
Message-ID: <20140327235918.GA7689@onthe.net.au> (raw)
In-Reply-To: <5334B44E.4080300@beyond.pl>
On Fri, Mar 28, 2014 at 12:29:18AM +0100, Marcin Gibuła wrote:
> W dniu 2014-03-27 23:52, Chris Dunlop pisze:
>> Hi,
>>
>> I have a problem where I migrate a linux guest VM, and on the
>> receiving side the guest goes to 100% cpu as seen by the host, and
>> the guest itself is unresponsive, e.g. not responding to ping etc.
>> The only way out I've found is to destroy the guest.
>>
>> This seems to only happen if the guest has been idle for an extended
>> period (e.g. overnight). I've migrated the guest 100 times in a row
>> without any problems when the guest has been used "a little" (e.g.
>> logging in and looking around, it's not doing anything normally).
>
> Hi,
>
> I've seen very similar problem on our installation. Have you tried to
> run with kvm-clock explicitly disabled (either via no-kvmclock in
> guest kernel or with -kvm-clock in qemu) ?
No, I haven't tried it yet (I've confirmed kvm-clock is currently
being used). I'll have a look at it.
Did it help your issue?
Thanks,
Chris
next prev parent reply other threads:[~2014-03-27 23:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 22:52 [Qemu-devel] Unresponsive linux guest once migrated Chris Dunlop
2014-03-27 23:29 ` Marcin Gibuła
2014-03-27 23:59 ` Chris Dunlop [this message]
2014-03-31 8:39 ` Marcin Gibuła
2014-04-02 5:41 ` Chris Dunlop
2014-04-02 8:45 ` Marcin Gibuła
2014-04-02 9:04 ` Dr. David Alan Gilbert
2014-04-02 9:30 ` Marcin Gibuła
2014-04-02 9:39 ` Dr. David Alan Gilbert
2014-04-02 10:18 ` Marcin Gibuła
2014-04-02 17:05 ` Marcin Gibuła
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=20140327235918.GA7689@onthe.net.au \
--to=chris@onthe.net.au \
--cc=m.gibula@beyond.pl \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).