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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
