All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uri Lublin <uril-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Chris Lalancette <clalance-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Migration problems
Date: Thu, 24 Jan 2008 13:52:16 +0200	[thread overview]
Message-ID: <47987BF0.7030005@qumranet.com> (raw)
In-Reply-To: <47979986.1060409-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Chris Lalancette wrote:
> 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.
>
> 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
>   
Hi Chris,

I am chasing migration bug(s) too.
I think the problem lies in userspace and not in the kernel modules.
It seems that for kvm-56 migration works but for kvm-57 it does not.
The problem seems to be related to the qemu-cvs merge: 
25a2e04e5689af63d104de2dea755f30bf643afd
If you run it with -no-kvm migration seems to be working.

The test case I'm using is savevm/loadvm.
After a loadvm my FC6 guest gets double-fault (<qemu-cmdline> -loadvm <id>).
Adding '-no-kvm-irqchip' does not help.
But if I start qemu in a stopped mode (<qemu-cmdline> -S) and 'loadvm 
<id>' in qemu-monitor, it works.
Sometimes after lodavm guest network does work better with '-no-kvm-irqchip'
I am trying to use bisection to find the problematic patch.

Thanks,
Uri.

-------------------------------------------------------------------------
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/

  parent reply	other threads:[~2008-01-24 11:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23 19:46 Migration problems Chris Lalancette
     [not found] ` <47979986.1060409-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-01-24  6:12   ` Avi Kivity
2008-01-24 11:52   ` Uri Lublin [this message]
     [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=47987BF0.7030005@qumranet.com \
    --to=uril-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.