[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] commit : "virtio: set ISR on dataplane notifications" break
[Qemu-devel] commit : "virtio: set ISR on dataplane notifications" breaks virtio-pci network on linux guest.
Wed, 18 Jan 2017 10:21:32 +0800
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
Upgrading from 2.7.1 to 2.8 on my machines here leaves the guests
without networking. All guests are using a vanilla self-compiled 4.8.12
kernel. The host is using a 4.9.3 kernel.
Guests are using virtio networking into a bridge on the host.
tcpdump on the bridge shows the guests sending dhcp requests and the
host sending replies, but the replies never make it into the guest.
A bisect between 2.7.1 & 2.8 shows the following commit at fault.
This would appear to be the same fault as mentioned here :
It's no issue for me to leave my hosts at 2.7, but in case it hadn't
been raised I thought I'd track it down and report it.
address@hidden:~/qemu$ git bisect good
83d768b5640946b7da55ce8335509df297e2c7cd is the first bad commit
Author: Paolo Bonzini <address@hidden>
Date: Fri Nov 18 16:07:02 2016 +0100
virtio: set ISR on dataplane notifications
Dataplane has been omitting forever the step of setting ISR when
an interrupt is raised. This caused little breakage, because the
specification actually says that ISR may not be updated in MSI mode.
Some versions of the Windows drivers however didn't clear MSI mode
correctly, and proceeded using polling mode (using ISR, not the used
ring index!) for crashdump and hibernation. If it were just crashdump
and hibernation it would not be a big deal, but recent releases of
Windows do not really shut down, but rather log out and hibernate to
make the next startup faster. Hence, this manifested as a more serious
hang during shutdown with e.g. Windows 8.1 and virtio-win 1.8.0 RPMs.
Newer versions fixed this, while older versions do not use MSI at all.
The failure has always been there for virtio dataplane, but it became
visible after commits 9ffe337 ("virtio-blk: always use dataplane path
if ioeventfd is active", 2016-10-30) and ad07cd6 ("virtio-scsi: always
use dataplane path if ioeventfd is active", 2016-10-30) made virtio-blk
and virtio-scsi always use the dataplane code under KVM. The good news
therefore is that it was not a bug in the patches---they were doing
exactly what they were meant for, i.e. shake out remaining
The fix is not hard, so it's worth arranging for the broken drivers.
The virtio_should_notify+event_notifier_set pair that is common to
virtio-blk and virtio-scsi dataplane is replaced with a new public
function virtio_notify_irqfd that also sets ISR. The irqfd emulation
code now need not set ISR anymore, so virtio_irq is removed.
Reviewed-by: Stefan Hajnoczi <address@hidden>
Tested-by: Farhan Ali <address@hidden>
Tested-by: Alex Williamson <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
:040000 040000 fa35e9e7e6b49f32f4c5b24586f65ca7f2e6fc73
282ecd3bb6c512e135b3e10d70de6c9bc306203e M hw
:040000 040000 6ded15de7a064a8c00ac60d3f61e09e5d66a5cdd
7dc07e32776505c037da7bd9e95a78c2518fa458 M include
- [Qemu-devel] commit : "virtio: set ISR on dataplane notifications" breaks virtio-pci network on linux guest.,
Brad Campbell <=