public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Philipp Hahn <hahn@univention.de>
Cc: kvm@vger.kernel.org
Subject: Re: [BUG] VM stuck in interrupt-loop after suspend to/resumed from file, or no interrupts at all
Date: Wed, 12 Jan 2011 15:11:32 +0000	[thread overview]
Message-ID: <20110112151132.GR26354@redhat.com> (raw)
In-Reply-To: <201101121551.19083.hahn@univention.de>

On Wed, Jan 12, 2011 at 03:51:13PM +0100, Philipp Hahn wrote:
> Hello,
> 
> libvirt implements a manages save, which suspens a VM to a file, from which it 
> can be resumed later. This uses Qemus/Kvms "migrate exec:<file>" feature.
> This doesn't work reliable for me: In may cases the resumed VM seems to be 
> stuck: its VNC console is restored, but no key presses or network packages 
> are accepted. This both happens with Windows XP, 7, 2008 and Linux 2.6.32 
> systems.
> 
> Using the debugging cycle described below in more detail I was able to track 
> the problem down to interrupt handling: Either the Linux-guest-kernel 
> constantly receives an interrupt for the 8139cp network adapter, or no 
> interrupts at all (neither network nor keyboard nor timer); only sending a 
> NMI works and shows that at least the Linux-Kernel is still alive.
> 
> If I add the -no-kvm-irqchip Option, it seems to work; I was not able to 
> reproduce a hang.

I remember reporting a bug with that scenario 4/5 months back
and it being fixed in the host kernel IIRC.

Daniel

      reply	other threads:[~2011-01-12 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 14:51 [BUG] VM stuck in interrupt-loop after suspend to/resumed from file, or no interrupts at all Philipp Hahn
2011-01-12 15:11 ` Daniel P. Berrange [this message]

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=20110112151132.GR26354@redhat.com \
    --to=berrange@redhat.com \
    --cc=hahn@univention.de \
    --cc=kvm@vger.kernel.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