qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Liran Schour <LIRANS@il.ibm.com>,
	Pierre Riteau <Pierre.Riteau@irisa.fr>,
	qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
	Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: Live migration of x86-64 kvm guests broken?
Date: Wed, 02 Dec 2009 19:44:19 +0100	[thread overview]
Message-ID: <4B16B583.7010005@siemens.com> (raw)
In-Reply-To: <20091202183533.GT27346@us.ibm.com>

Ryan Harper wrote:
> * Jan Kiszka <jan.kiszka@siemens.com> [2009-12-02 12:18]:
>> Ryan Harper wrote:
>>> * Jan Kiszka <jan.kiszka@siemens.com> [2009-12-02 12:07]:
>>>> Ryan Harper wrote:
>>>>> * Jan Kiszka <jan.kiszka@siemens.com> [2009-12-02 09:28]:
>>>>>> Hi,
>>>>>>
>>>>>> I'm facing stalled x86-64 guests after live migration when using kvm
>>>>>> (share disk images). This does not happen with x86-32 guests or when
>>>>>> disabling kvm. Both qemu and qemu-kvm git heads are affected (recent
>>>>>> vmstate fixes applied). Running I/O load during the migration (e.g. a
>>>>>> simple "ls -R /") seems to trigger it reliably.
>>>>>>
>>>>>> Can anyone confirm / comment on this? Do we fail to restore some magic
>>>>>> state that only long mode cares about?
>>>>> Just tested upstream qemu.git (with vmstate fixes) and I could migrate
>>>>> RHEL 5.3 64-bit guest with your light io load over localhost.  I'll try
>>>>> remote hosts next.
>>>> Hell, too many variables. It looks like the kernel modules have some if
>>>> not the ultimate impact: kvm-mod-2.6.31.6b on my 2.6.27 host works fine,
>>>> kvm-kmod stable-2.6.32 as well as master cause troubles.
>>>>
>>>> What is your host kernel and/or kvm module version?
>>> Stock 64-bit Ubuntu Karmic:
>>> % uname -a
>>> Linux symmetry 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:53:52 UTC 2009 x86_64 GNU/Linux
>>>
>>> % modinfo kvm
>>> filename:
>>> /lib/modules/2.6.31-15-generic/kernel/arch/x86/kvm/kvm.ko
>>> license:        GPL
>>> author:         Qumranet
>>> srcversion:     82D6B673524596F9CF3E84C
>>> depends:        
>>> vermagic:       2.6.31-15-generic SMP mod_unload modversions 
>>> parm:           oos_shadow:bool
>>>
>>> % modinfo kvm-intel
>>> filename: /lib/modules/2.6.31-15-generic/kernel/arch/x86/kvm/kvm-intel.ko
>>> license:        GPL
>>> author:         Qumranet
>>> srcversion:     8FEA479DFCD7F174DA7864E
>>> depends:        kvm
>>> vermagic:       2.6.31-15-generic SMP mod_unload modversions 
>>> parm:           bypass_guest_pf:bool
>>> parm:           vpid:bool
>>> parm:           flexpriority:bool
>>> parm:           ept:bool
>>> parm:           emulate_invalid_guest_state:bool
>>>
>> So far, so consistent. Could you try kvm-kmod-2.6.32-rc7 on top of that?
>>
> 
> Sure, can you remind me of the kvm-kmod build magic for building that
> branch?
> 

If you want to build from git, check Wolfgang's nice README. But it
might be easier to just download the tarball from sourceforge.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-12-02 18:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 15:24 [Qemu-devel] Live migration of x86-64 kvm guests broken? Jan Kiszka
2009-12-02 16:44 ` [Qemu-devel] " Ryan Harper
2009-12-02 18:05   ` Jan Kiszka
2009-12-02 18:10     ` Ryan Harper
2009-12-02 18:16       ` Jan Kiszka
2009-12-02 18:35         ` Ryan Harper
2009-12-02 18:44           ` Jan Kiszka [this message]
2009-12-02 19:10             ` Ryan Harper
2009-12-02 19:24               ` Ryan Harper
2009-12-02 19:26                 ` Jan Kiszka
2009-12-02 18:16 ` Juan Quintela

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=4B16B583.7010005@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=LIRANS@il.ibm.com \
    --cc=Pierre.Riteau@irisa.fr \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=ryanh@us.ibm.com \
    /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).