[Bug 219903] New: [6.14.0_rc7] TX timeout and ping failed after change the tx queue length

[Bug 219903] New: [6.14.0_rc7] TX timeout and ping failed after change the tx queue length

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=219903

            Bug ID: 219903
           Summary: [6.14.0_rc7] TX timeout and ping failed after change
                    the tx queue length
           Product: Virtualization
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: low
          Priority: P3
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: leiyang@redhat.com
        Regression: No

How reproducible:
100%

Steps to reproduce
1.Boot guest with virtio-net device and enable queue_reset:

-device
virtio-net-pci,id=net0,netdev=hostnet0,queue_reset=on,bus=pcie.0,addr=0x5 \
-netdev
tap,id=hostnet0,script=/etc/qemu-ifup,downscript=/etc/qemu-ifdown,vhost=on \


2.Ping external host after change the tx size, ping failed

[root@guest ~]# ethtool -G eth0 tx 8
[root@guest ~]# ping 10.72.136.90 -c 10
PING 10.72.136.90 (10.72.136.90) 56(84) bytes of data.
From 10.72.139.48 icmp_seq=1 Destination Host Unreachable
From 10.72.139.48 icmp_seq=2 Destination Host Unreachable
From 10.72.139.48 icmp_seq=3 Destination Host Unreachable
From 10.72.139.48 icmp_seq=4 Destination Host Unreachable
From 10.72.139.48 icmp_seq=5 Destination Host Unreachable
From 10.72.139.48 icmp_seq=6 Destination Host Unreachable
From 10.72.139.48 icmp_seq=7 Destination Host Unreachable

— 10.72.136.90 ping statistics —
10 packets transmitted, 0 received, +7 errors, 100% packet loss, time 9227ms
pipe 4

3.Guest dmesg will repeatedly print messages like the following:

[ 488.149842] virtio_net virtio1 eth0: NETDEV WATCHDOG: CPU: 25: transmit queue
0 timed out 5004 ms
[ 488.149855] virtio_net virtio1 eth0: TX timeout on queue: 0, sq: output.0,
vq: 0x1, name: output.0, 5004000 usecs ago


I don't think this is a regression issues, since this is first time to test
this scenario.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.