public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Lalancette <clalance-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Migration problems
Date: Wed, 23 Jan 2008 14:46:14 -0500	[thread overview]
Message-ID: <47979986.1060409@redhat.com> (raw)

All,
     I've been doing some migration testing of KVM guests, and have been running
into some problems.  Let me describe the setup and what I've tried, and maybe
somebody has some ideas about what might be going on here.

Setup:
     2 identical Intel SDV boxes,  Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz
     Both machines are running F-8 kernel, 2.6.23.8-63.fc8 x86_64, with updated
KVM kernel modules from git.
     On one machine, I have a /kvm directory that holds my guest disk image;
this directory is exported via NFS and mounted as /kvm on the secondary machine.

The guest in question is also an F-8 x86_64 guest, running the same kernel as
the hosts.  I start it up with the following command-line:

qemu-system-x86_64 -hda /kvm/f8x86_64.dsk -boot c -m 385 -net
nic,vlan=0,macaddr=00:13:6e:12:34:56 -net tap,vlan=0,script=/etc/kvm-ifup
-monitor stdio

The guest starts up just fine.  On the secondary machine, I use the following
command-line:

qemu-system-x86_64 -hda /kvm/f8x86_64.dsk -boot c -m 385 -net
nic,vlan=0,macaddr=00:13:6e:12:34:56 -net tap,vlan=0,script=/etc/kvm-ifup
-monitor stdio -incoming tcp://0:4444

(i.e. exactly the same, but I add the -incoming parameter).  When I try to do
live migration this way, things seem like they work, and it even seems like a
few instructions get executed on the destination side.  However, fairly quickly
I'll get "Disabling IRQ #11" on the console of the guest at the destination, and
the qemu process will just spin at 100%, with no interaction possible.  IRQ #11,
incidentally, is the IRQ associated with the emulated rtl8139 card.

This led me to suspect the in-kernel PIC/APIC emulation, and, sure enough, if I
pass -no-kvm-irqchip (on both the source and destination), things are better; I
can at least migrate from the host to the destination without the "Disabling IRQ
#11" message.  However, if I put any sort of load on the guest while doing
migration, I still get a hang-up, even with -no-kvm-irqchip.

Has anyone else seen this, or have ideas where I can start debugging it?

Thanks,
Chris Lalancette

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

             reply	other threads:[~2008-01-23 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23 19:46 Chris Lalancette [this message]
     [not found] ` <47979986.1060409-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-01-24  6:12   ` Migration problems Avi Kivity
2008-01-24 11:52   ` Uri Lublin
     [not found]     ` <47987BF0.7030005-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-25 16:08       ` Guido Guenther
     [not found]         ` <20080125160841.GA24819-DVvpyRRQz99DDGxTMhc9XQ@public.gmane.org>
2008-01-28 18:40           ` Guido Guenther

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=47979986.1060409@redhat.com \
    --to=clalance-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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