On Fri, Jul 23, 2021 at 03:31:02AM -0500, Ivan wrote: > On Fri, Jul 23, 2021 at 2:59 AM Michael S. Tsirkin <[email protected]> wrote: > > > > On Thu, Jul 22, 2021 at 11:50:11PM -0500, Ivan wrote: > > > On Thu, Jul 22, 2021 at 11:25 PM Jason Wang <[email protected]> wrote: > > > > 在 2021/7/23 上午10:54, Ivan 写道: > > > > > On Thu, Jul 22, 2021 at 9:37 PM Jason Wang <[email protected]> > > > > > wrote: > > > > >> Does it work if you turn off lro before enabling the forwarding? > > > > > 0 root@NuRaid:~# ethtool -K eth0 lro off > > > > > Actual changes: > > > > > rx-lro: on [requested off] > > > > > Could not change any device features > > > > > > > > Ok, it looks like the device misses the VIRTIO_NET_F_CTRL_GUEST_OFFLOADS > > > > which makes it impossible to change the LRO setting. > > > > > > > > Did you use qemu? If yes, what's the qemu version you've used? > > > > > > These are VirtualBox machines, which I've been using for years with > > > longterm kernels 4.19, and I never had such a problem. But now that I > > > tried upgrading to kernels 5.10 or 5.13 -- the panics started. These > > > are just generic kernel builds, and a minimalistic userspace. > > > > I would be useful to see the features your virtualbox instance provides > > > > cat /sys/class/net/eth0/device/features > > > > replacing eth0 with device name as appropriate > > # grep . /sys/class/net/eth0/device/* 2>/dev/null > /sys/class/net/eth0/device/device:0x0001 > /sys/class/net/eth0/device/ > features:1100010110111011111100000000000000000000000000000000000000000000 > /sys/class/net/eth0/device/modalias:virtio:d00000001v00001AF4 > /sys/class/net/eth0/device/status:0x00000007 > /sys/class/net/eth0/device/uevent:DRIVER=virtio_net > /sys/class/net/eth0/device/uevent:MODALIAS=virtio:d00000001v00001AF4 > /sys/class/net/eth0/device/vendor:0x1af4 > > # lspci -vv -nn > 00:03.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device > [1af4:1000] > Subsystem: Red Hat, Inc. Virtio network device [1af4:0001] > Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > <TAbort- > <MAbort- >SERR- <PERR- INTx- > Latency: 64 > Interrupt: pin A routed to IRQ 19 > Region 0: I/O ports at d000 [size=32] > Capabilities: [80] Null > Kernel driver in use: virtio-pci > Kernel modules: virtio_pci >
Disabling guest offloads reproduces the warning, but not the crash for me. -- MST _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
