qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Marcin Gibuła" <m.gibula@beyond.pl>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] troubleshooting live migration
Date: Thu, 16 Jan 2014 23:33:44 +0100	[thread overview]
Message-ID: <52D85E48.8030403@beyond.pl> (raw)

 > I tried -no-hpet, was still able to replicate the 'lapic' issue. I
 > find it interesting that I can only trigger it if the vm has been
 > running awhile.

Hi,

I've seen identical crashes with live migration in our environment. It 
looks identical - VM has to be idle for some time and after migration 
CPU is at 100% and VM is dead. All migration happens between same hardware.

I don't think I've ever had Windows guest crashing like this and I think 
this is somehow related to kvmclock. I've tried to debug qemu guest 
process and from I can tell, its kernel is busy looping in some time 
management related functions. Could you try to reproduce this issue with 
-no-kvmclock? Our testing environment is currently offline so I can't 
test it myself.

We also use 3.10 kernel (though 3.8 wasn't working either) and strugled 
with this issue with qemu 1.4, 1.5 and 1.6. Didn't test 1.7. Also we're 
using AMD CPUs, so it seems to be platform independend.

-- 
mg

             reply	other threads:[~2014-01-16 22:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 22:33 Marcin Gibuła [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-14 15:31 [Qemu-devel] troubleshooting live migration Marcus Sorensen
2014-01-15  6:08 ` Marcus Sorensen
2014-01-15 14:27   ` Marcus Sorensen

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=52D85E48.8030403@beyond.pl \
    --to=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).