public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Brad Campbell <lists2009@fnarfbargle.com>,
	Nadav Amit <nadav.amit@gmail.com>
Cc: "Saso Slavicic" <saso.linux@astim.si>,
	"kvm list" <kvm@vger.kernel.org>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: XP machine freeze
Date: Sun, 19 Apr 2015 19:16:30 +0200	[thread overview]
Message-ID: <5533E2EE.6000906@redhat.com> (raw)
In-Reply-To: <5533DCE0.4080606@fnarfbargle.com>



On 19/04/2015 18:50, Brad Campbell wrote:
> And I can confidently state that over the years I've seen this happen a
> number of times, but in each case I was using qemu with an SDL console
> as a user-interactive VM, and a moving the mouse would restore network
> connectivity. It was obviously seriously exacerbated by something that
> went into 3.16.

Yes, it was---it's straight in the commit message for commit f210f7572bed:

> commit 56cc2406d68c ("KVM: nVMX: fix "acknowledge interrupt on exit"
> when APICv is in use") changed the behavior of apic_clear_irr [...]
> Nonetheless, it appears the race might even occur prior to this commit:

Note that there is another regression between 3.17 and 3.19 (visible as
migration failures with XFS in the guest), so I'd keep 3.17.x for a
while in production.

The hard disk holding my test system's root filesystem died on Friday so
it may take a few days before I actually prepare the fix for stable@ and
also apply the other pending patches.  Nevertheless, no data was lost
(/home is safe) so it's just a matter of finding some time to reinstall
the OSes.

Paolo

  reply	other threads:[~2015-04-19 17:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 15:10 XP machine freeze Saso Slavicic
2015-03-19  0:51 ` Marcelo Tosatti
2015-03-30 16:19   ` Saso Slavicic
2015-03-22 15:31 ` Brad Campbell
2015-03-30 21:11   ` Paolo Bonzini
2015-03-31  0:27     ` Brad Campbell
2015-03-31  6:29       ` Saso Slavicic
2015-03-31  7:18         ` Brad Campbell
2015-03-31  8:56           ` Paolo Bonzini
2015-03-31 11:16             ` Brad Campbell
2015-03-31 11:23               ` Paolo Bonzini
2015-04-04 10:55                 ` Brad Campbell
2015-04-13  4:07     ` Brad Campbell
2015-04-13 12:38       ` Paolo Bonzini
2015-04-13 12:45         ` Brad Campbell
2015-04-13 14:02           ` Paolo Bonzini
2015-04-13 14:25             ` Brad Campbell
2015-04-19 15:27             ` Brad Campbell
2015-04-19 15:48               ` Nadav Amit
2015-04-19 16:50                 ` Brad Campbell
2015-04-19 17:16                   ` Paolo Bonzini [this message]
2015-04-13 12:47         ` Saso Slavicic
2015-04-13 13:33         ` Radim Krčmář
2015-04-13 13:34         ` Nadav Amit
2015-04-13 14:01           ` Paolo Bonzini

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=5533E2EE.6000906@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    --cc=nadav.amit@gmail.com \
    --cc=rkrcmar@redhat.com \
    --cc=saso.linux@astim.si \
    /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