public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2948108 ] qemu-kvm fails to migrate properly in 0.12.2
Date: Mon, 08 Feb 2010 22:06:23 +0000	[thread overview]
Message-ID: <E1NebkN-0005Ab-R1@sfs-web-4.v29.ch3.sourceforge.com> (raw)

Bugs item #2948108, was opened at 2010-02-08 14:06
Message generated for change (Tracker Item Submitted) made by ramereth
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2948108&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: qemu
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Lance Albertson (ramereth)
Assigned to: Nobody/Anonymous (nobody)
Summary: qemu-kvm fails to migrate properly in 0.12.2

Initial Comment:
I'm using Ganeti and encountered a problem [1] with migrating KVM virtual machines. I have confirmed that this is not a problem specific to Ganeti and is also happening to the Libvirt project [2].

When migrating from host A to host B, everything goes fine however the guest VM (running CentOS 5.4) clock changes to approximately 600 seconds in the future. When attempting to migrate back to host B, the VM locks up and stops responding. However, if you fix the clock prior to syncing back to host A, the migration happens however the clock on the VM literally stops so the guest is pretty unusable. 

I tried the same scenario using Ubuntu 9.10 for the guest OS and has different issues. Upon migrating to host B, the clock on the guest VM was ahead by over 3 days into the future. Then when I migrate it back to host A the VM locks up hard.

I can confirm I have no problem using migration when using 0.11.1.

Here's the detail information about our setup:
Hardware: Intel(R) Xeon(R) CPU 5160  @ 3.00GHz
qemu-kvm: 0.12.2
kernel: 2.6.29-hardened
Linux OS: Gentoo Hardened

If you need more information, please let me know and I'll be happy to provide it.

Thanks-

[1] http://groups.google.com/group/ganeti/browse_thread/thread/9b2c556557e749cf
[2] http://thread.gmane.org/gmane.comp.emulators.libvirt/20771

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2948108&group_id=180599

             reply	other threads:[~2010-02-08 22:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08 22:06 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-08 23:09 [ kvm-Bugs-2948108 ] qemu-kvm fails to migrate properly in 0.12.2 SourceForge.net
2010-02-08 23:27 SourceForge.net
2010-02-08 23:54 SourceForge.net
2010-02-09  0:13 SourceForge.net
2010-02-09  0:30 SourceForge.net
2010-02-09  0:33 SourceForge.net
2010-02-09  9:50 SourceForge.net
2010-02-09 15:55 SourceForge.net
2010-02-09 16:09 SourceForge.net
2010-02-09 19:29 SourceForge.net
2010-06-16 15:39 SourceForge.net
2010-06-16 17:30 SourceForge.net

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=E1NebkN-0005Ab-R1@sfs-web-4.v29.ch3.sourceforge.com \
    --to=noreply@sourceforge.net \
    /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