Re: kvm vlan virtio problem
Hi Bryan, On 23.01.2013 04:44, Bryan Venteicher wrote: Hi, - Original Message - Hi! The same warning shows up in our setup: Jan 21 23:40:46 host kernel: WARNING: at net/core/dev.c:1712 skb_gso_segment+0x1df/0x2b0() (Tainted: GW --- ) Jan 21 23:40:46 host kernel: Hardware name: System Product Name Jan 21 23:40:46 host kernel: tun: caps=(0x1b0049, 0x0) len=4452 data_len=4380 ip_summed=0 [...] KVM host: CentOS 6.3, Linux kernel 2.6.32-279.19.1.el6.x86_64 VM guest: FreeBSD 9.1, virtio-kmod-9.1-0.242658 Disabling TSO on vtnet0 stops the warnings on the KVM host. Is there any progress on this issue? Alright, I tried to recreate this on Ubuntu 12.10 without any luck. Please describe your network configuration. On my Linux host, my VLAN interface looks like: eth0.100 Link encap:Ethernet HWaddr 6c:f0:49:05:2b:6d inet6 addr: fe80::6ef0:49ff:fe05:2b6d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3119867 errors:0 dropped:0 overruns:0 frame:0 TX packets:3790183 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:166813040 (166.8 MB) TX bytes:5435432448 (5.4 GB) That is plugged into this bridge: br100 Link encap:Ethernet HWaddr 6c:f0:49:05:2b:6d inet addr:192.168.99.101 Bcast:192.168.99.255 Mask:255.255.255.0 inet6 addr: fe80::6ef0:49ff:fe05:2b6d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:876 (876.0 B) TX bytes:1420 (1.4 KB) With the tap device created by QEMU for my FreeBSD guest: vnet1 Link encap:Ethernet HWaddr fe:54:00:ec:4f:4e inet6 addr: fe80::fc54:ff:feec:4f4e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:800284 errors:0 dropped:0 overruns:0 frame:0 TX packets:3119877 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:5238099122 (5.2 GB) TX bytes:210492002 (210.4 MB) All this tied together: # brctl show br100 bridge name bridge id STP enabled interfaces br100 8000.6cf049052b6d no eth0.100 vnet1 Does this approximate your configuration? What's the output of `ethtool -k` for your VLAN, bridge, and vnet interfaces? First of all: Thanks for your efforts. We are using a different setup. Basically we are using a router VM, which means: All IP traffic for the actual VMs is routed through it. One ethernet interface of the router VM is bridged with the physical ethernet interface of the KVM host. The router VM has one or more additional interfaces for the actual VMs. This is the output of ifconfig -a from the KVM host: br0 Link encap:Ethernet HWaddr AA:50:00:1F:23:AD inet addr:88.12.100.100 Bcast:88.12.100.127 Mask:255.255.255.255 inet6 addr: fe80::aa50:ff:fe1f:23ad/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:338087 errors:0 dropped:0 overruns:0 frame:0 TX packets:213316 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:115518852 (110.1 MiB) TX bytes:528688448 (504.1 MiB) eth0 Link encap:Ethernet HWaddr AA:50:00:1F:23:AD inet6 addr: fe80::aa50:ff:fe1f:23ad/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6398703 errors:0 dropped:0 overruns:0 frame:0 TX packets:8451045 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3566218121 (3.3 GiB) TX bytes:7532154606 (7.0 GiB) Interrupt:43 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:138575 errors:0 dropped:0 overruns:0 frame:0 TX packets:138575 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:480320359 (458.0 MiB) TX bytes:480320359 (458.0 MiB) virbr0Link encap:Ethernet HWaddr 52:54:00:83:09:92 inet addr:10.30.1.1 Bcast:10.30.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7 errors:0 dropped:0 overruns:0 frame:0 TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:232 (232.0 b) TX bytes:3156 (3.0 KiB) virbr0-nic Link encap:Ethernet HWaddr 52:54:00:83:09:92 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX
Re: Re: kvm vlan virtio problem
Hi! The same warning shows up in our setup: Jan 21 23:40:46 host kernel: WARNING: at net/core/dev.c:1712 skb_gso_segment+0x1df/0x2b0() (Tainted: GW --- ) Jan 21 23:40:46 host kernel: Hardware name: System Product Name Jan 21 23:40:46 host kernel: tun: caps=(0x1b0049, 0x0) len=4452 data_len=4380 ip_summed=0 [...] KVM host: CentOS 6.3, Linux kernel 2.6.32-279.19.1.el6.x86_64 VM guest: FreeBSD 9.1, virtio-kmod-9.1-0.242658 Disabling TSO on vtnet0 stops the warnings on the KVM host. Is there any progress on this issue? Best regards Franz On 04.11.2012 02:53, Bryan Venteicher wrote: Hi, - Original Message - From: Bane Ivosev bane.ivo...@pmf.uns.ac.rs To: Bryan Venteicher bry...@daemoninthecloset.org, freebsd-stable@freebsd.org Sent: Saturday, November 3, 2012 7:58:57 PM Subject: Re: kvm vlan virtio problem thanks bryan, i don't have vlans inside guest. as you suggested i disabled nic tso ifconfig vtnet0 -tso and sysctl net.inet.tcp.tso=0 and so far, so good! everything is ok now. once again, thanks a lot. No need to disable TSO globally. So it seems if_vtnet sending down TSO frames that don't have the appropriate flags set. I'll look into it more in a next couple of days. Thanks for the quick reply back. Bryan On 11/03/2012 09:40 PM, Bryan Venteicher wrote: Hi, - Original Message - From: Bane Ivosevbane.ivo...@pmf.uns.ac.rs To: freebsd-stable@freebsd.org Sent: Saturday, November 3, 2012 2:12:25 PM Subject: kvm vlan virtio problem hi, i have several kvm ubuntu 12.04 and centos 6 hosts with standard bridged network setup. same problem on each server with freebsd 9 amd64 guest and virtio nic: soon after guest start host syslog is filling with this message at very high rate. guest is working without any problem. with e1000 guest driver eveything is ok. does enyone have/had same problem? thanks. I have a vague recollection of looking at something similar last year... Do you have VLAN configured in the guest as well? What is the ifconfig output? Does disabling TSO on the vtnetX device make these messages go away? Bryan kernel: [2337728.094141] [ cut here ] kernel: [2337728.094144] WARNING: at /build/buildd/linux-3.2.0/net/core/dev.c:1955 skb_gso_segment+0x341/0x3b0() kernel: [2337728.094146] Hardware name: System x3550 M3 -[7944K3G]- kernel: [2337728.094148] 802.1Q VLAN Support: caps=(0x30195833, 0x0) len=3196 data_len=0 ip_summed=0 kernel: [2337728.094149] Modules linked in: dm_snapshot ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables kvm_intel kvm dm_crypt nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc nls_iso8859_1 nls_cp437 vfat fat 8021q garp bridge stp serio_raw cdc_ether usbnet vhost_net macvtap i7core_edac macvlan shpchp ioatdma edac_core dca tpm_tis lp parport mac_hid btrfs zlib_deflate libcrc32c usbhid hid megaraid_sas bnx2 kernel: [2337728.094177] Pid: 8685, comm: vhost-8683 Tainted: G W3.2.0-31-generic #50-Ubuntu kernel: [2337728.094179] Call Trace: kernel: [2337728.094180]IRQ [81066d7f] warn_slowpath_common+0x7f/0xc0 kernel: [2337728.094185] [81066e76] warn_slowpath_fmt+0x46/0x50 kernel: [2337728.094188] [8153f581] skb_gso_segment+0x341/0x3b0 kernel: [2337728.094191] [81542ee1] dev_hard_start_xmit+0xc1/0x540 kernel: [2337728.094196] [a01c0150] ? br_flood+0xc0/0xc0 [bridge] kernel: [2337728.094199] [8154360a] dev_queue_xmit+0x2aa/0x420 kernel: [2337728.094203] [a01c01e2] br_dev_queue_push_xmit+0x92/0xd0 [bridge] kernel: [2337728.094208] [a01c0278] br_forward_finish+0x58/0x60 [bridge] kernel: [2337728.094212] [a01c042b] __br_forward+0xab/0xd0 [bridge] kernel: [2337728.094217] [a01c04ed] br_forward+0x5d/0x70 [bridge] kernel: [2337728.094221] [a01c11c2] br_handle_frame_finish+0x182/0x2a0 [bridge] kernel: [2337728.094226] [a01c14a8] br_handle_frame+0x1c8/0x270 [bridge] kernel: [2337728.094231] [a01c12e0] ? br_handle_frame_finish+0x2a0/0x2a0 [bridge] kernel: [2337728.094234] [81540892] __netif_receive_skb+0x1e2/0x520 kernel: [2337728.094237] [81540ff1] process_backlog+0xb1/0x190 kernel: [2337728.094240] [815422e4] net_rx_action+0x134/0x290 kernel: [2337728.094242] [8165a4fe] ? _raw_spin_lock+0xe/0x20 kernel: [2337728.094245] [8106e528] __do_softirq+0xa8/0x210 kernel: [2337728.094248] [81664d6c] call_softirq+0x1c/0x30 kernel: [2337728.094249]EOI [81015305] do_softirq+0x65/0xa0 kernel
Re: kvm vlan virtio problem
Hi, - Original Message - Hi! The same warning shows up in our setup: Jan 21 23:40:46 host kernel: WARNING: at net/core/dev.c:1712 skb_gso_segment+0x1df/0x2b0() (Tainted: GW --- ) Jan 21 23:40:46 host kernel: Hardware name: System Product Name Jan 21 23:40:46 host kernel: tun: caps=(0x1b0049, 0x0) len=4452 data_len=4380 ip_summed=0 [...] KVM host: CentOS 6.3, Linux kernel 2.6.32-279.19.1.el6.x86_64 VM guest: FreeBSD 9.1, virtio-kmod-9.1-0.242658 Disabling TSO on vtnet0 stops the warnings on the KVM host. Is there any progress on this issue? It seems the only way this could happen is if the FreeBSD TCP/IP stack sent down an mbuf with CSUM_TSO set and CSUM_TCP not set; this doesn't seem possible from looking at FreeBSD's tcp_output(). I'll try to look closer at this during this week. Bryan Best regards Franz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kvm vlan virtio problem
Hi, - Original Message - Hi! The same warning shows up in our setup: Jan 21 23:40:46 host kernel: WARNING: at net/core/dev.c:1712 skb_gso_segment+0x1df/0x2b0() (Tainted: GW --- ) Jan 21 23:40:46 host kernel: Hardware name: System Product Name Jan 21 23:40:46 host kernel: tun: caps=(0x1b0049, 0x0) len=4452 data_len=4380 ip_summed=0 [...] KVM host: CentOS 6.3, Linux kernel 2.6.32-279.19.1.el6.x86_64 VM guest: FreeBSD 9.1, virtio-kmod-9.1-0.242658 Disabling TSO on vtnet0 stops the warnings on the KVM host. Is there any progress on this issue? Alright, I tried to recreate this on Ubuntu 12.10 without any luck. Please describe your network configuration. On my Linux host, my VLAN interface looks like: eth0.100 Link encap:Ethernet HWaddr 6c:f0:49:05:2b:6d inet6 addr: fe80::6ef0:49ff:fe05:2b6d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3119867 errors:0 dropped:0 overruns:0 frame:0 TX packets:3790183 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:166813040 (166.8 MB) TX bytes:5435432448 (5.4 GB) That is plugged into this bridge: br100 Link encap:Ethernet HWaddr 6c:f0:49:05:2b:6d inet addr:192.168.99.101 Bcast:192.168.99.255 Mask:255.255.255.0 inet6 addr: fe80::6ef0:49ff:fe05:2b6d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:876 (876.0 B) TX bytes:1420 (1.4 KB) With the tap device created by QEMU for my FreeBSD guest: vnet1 Link encap:Ethernet HWaddr fe:54:00:ec:4f:4e inet6 addr: fe80::fc54:ff:feec:4f4e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:800284 errors:0 dropped:0 overruns:0 frame:0 TX packets:3119877 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:5238099122 (5.2 GB) TX bytes:210492002 (210.4 MB) All this tied together: # brctl show br100 bridge name bridge id STP enabled interfaces br100 8000.6cf049052b6d no eth0.100 vnet1 Does this approximate your configuration? What's the output of `ethtool -k` for your VLAN, bridge, and vnet interfaces? Bryan Best regards Franz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kvm vlan virtio problem
Hi, - Original Message - From: Bane Ivosev bane.ivo...@pmf.uns.ac.rs To: freebsd-stable@freebsd.org Sent: Saturday, November 3, 2012 2:12:25 PM Subject: kvm vlan virtio problem hi, i have several kvm ubuntu 12.04 and centos 6 hosts with standard bridged network setup. same problem on each server with freebsd 9 amd64 guest and virtio nic: soon after guest start host syslog is filling with this message at very high rate. guest is working without any problem. with e1000 guest driver eveything is ok. does enyone have/had same problem? thanks. I have a vague recollection of looking at something similar last year... Do you have VLAN configured in the guest as well? What is the ifconfig output? Does disabling TSO on the vtnetX device make these messages go away? Bryan kernel: [2337728.094141] [ cut here ] kernel: [2337728.094144] WARNING: at /build/buildd/linux-3.2.0/net/core/dev.c:1955 skb_gso_segment+0x341/0x3b0() kernel: [2337728.094146] Hardware name: System x3550 M3 -[7944K3G]- kernel: [2337728.094148] 802.1Q VLAN Support: caps=(0x30195833, 0x0) len=3196 data_len=0 ip_summed=0 kernel: [2337728.094149] Modules linked in: dm_snapshot ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables kvm_intel kvm dm_crypt nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc nls_iso8859_1 nls_cp437 vfat fat 8021q garp bridge stp serio_raw cdc_ether usbnet vhost_net macvtap i7core_edac macvlan shpchp ioatdma edac_core dca tpm_tis lp parport mac_hid btrfs zlib_deflate libcrc32c usbhid hid megaraid_sas bnx2 kernel: [2337728.094177] Pid: 8685, comm: vhost-8683 Tainted: G W3.2.0-31-generic #50-Ubuntu kernel: [2337728.094179] Call Trace: kernel: [2337728.094180] IRQ [81066d7f] warn_slowpath_common+0x7f/0xc0 kernel: [2337728.094185] [81066e76] warn_slowpath_fmt+0x46/0x50 kernel: [2337728.094188] [8153f581] skb_gso_segment+0x341/0x3b0 kernel: [2337728.094191] [81542ee1] dev_hard_start_xmit+0xc1/0x540 kernel: [2337728.094196] [a01c0150] ? br_flood+0xc0/0xc0 [bridge] kernel: [2337728.094199] [8154360a] dev_queue_xmit+0x2aa/0x420 kernel: [2337728.094203] [a01c01e2] br_dev_queue_push_xmit+0x92/0xd0 [bridge] kernel: [2337728.094208] [a01c0278] br_forward_finish+0x58/0x60 [bridge] kernel: [2337728.094212] [a01c042b] __br_forward+0xab/0xd0 [bridge] kernel: [2337728.094217] [a01c04ed] br_forward+0x5d/0x70 [bridge] kernel: [2337728.094221] [a01c11c2] br_handle_frame_finish+0x182/0x2a0 [bridge] kernel: [2337728.094226] [a01c14a8] br_handle_frame+0x1c8/0x270 [bridge] kernel: [2337728.094231] [a01c12e0] ? br_handle_frame_finish+0x2a0/0x2a0 [bridge] kernel: [2337728.094234] [81540892] __netif_receive_skb+0x1e2/0x520 kernel: [2337728.094237] [81540ff1] process_backlog+0xb1/0x190 kernel: [2337728.094240] [815422e4] net_rx_action+0x134/0x290 kernel: [2337728.094242] [8165a4fe] ? _raw_spin_lock+0xe/0x20 kernel: [2337728.094245] [8106e528] __do_softirq+0xa8/0x210 kernel: [2337728.094248] [81664d6c] call_softirq+0x1c/0x30 kernel: [2337728.094249] EOI [81015305] do_softirq+0x65/0xa0 kernel: [2337728.094254] [815427c8] netif_rx_ni+0x28/0x30 kernel: [2337728.094258] [81478ec6] tun_get_user+0x306/0x4a0 kernel: [2337728.094261] [81479085] tun_sendmsg+0x25/0x30 kernel: [2337728.094265] [a01b09b6] handle_tx+0x296/0x530 [vhost_net] kernel: [2337728.094269] [a01b0c85] handle_tx_kick+0x15/0x20 [vhost_net] kernel: [2337728.094273] [a01ade3d] vhost_worker+0xdd/0x170 [vhost_net] kernel: [2337728.094276] [a01add60] ? vhost_set_memory+0x130/0x130 [vhost_net] kernel: [2337728.094279] [8108a03c] kthread+0x8c/0xa0 kernel: [2337728.094282] [81664c74] kernel_thread_helper+0x4/0x10 kernel: [2337728.094285] [81089fb0] ? flush_kthread_worker+0xa0/0xa0 kernel: [2337728.094287] [81664c70] ? gs_change+0x13/0x13 kernel: [2337728.094289] ---[ end trace a38cf088269411b3 ]--- kernel: [2337728.094731] [ cut here ] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kvm vlan virtio problem
thanks bryan, i don't have vlans inside guest. as you suggested i disabled nic tso ifconfig vtnet0 -tso and sysctl net.inet.tcp.tso=0 and so far, so good! everything is ok now. once again, thanks a lot. On 11/03/2012 09:40 PM, Bryan Venteicher wrote: Hi, - Original Message - From: Bane Ivosevbane.ivo...@pmf.uns.ac.rs To: freebsd-stable@freebsd.org Sent: Saturday, November 3, 2012 2:12:25 PM Subject: kvm vlan virtio problem hi, i have several kvm ubuntu 12.04 and centos 6 hosts with standard bridged network setup. same problem on each server with freebsd 9 amd64 guest and virtio nic: soon after guest start host syslog is filling with this message at very high rate. guest is working without any problem. with e1000 guest driver eveything is ok. does enyone have/had same problem? thanks. I have a vague recollection of looking at something similar last year... Do you have VLAN configured in the guest as well? What is the ifconfig output? Does disabling TSO on the vtnetX device make these messages go away? Bryan kernel: [2337728.094141] [ cut here ] kernel: [2337728.094144] WARNING: at /build/buildd/linux-3.2.0/net/core/dev.c:1955 skb_gso_segment+0x341/0x3b0() kernel: [2337728.094146] Hardware name: System x3550 M3 -[7944K3G]- kernel: [2337728.094148] 802.1Q VLAN Support: caps=(0x30195833, 0x0) len=3196 data_len=0 ip_summed=0 kernel: [2337728.094149] Modules linked in: dm_snapshot ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables kvm_intel kvm dm_crypt nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc nls_iso8859_1 nls_cp437 vfat fat 8021q garp bridge stp serio_raw cdc_ether usbnet vhost_net macvtap i7core_edac macvlan shpchp ioatdma edac_core dca tpm_tis lp parport mac_hid btrfs zlib_deflate libcrc32c usbhid hid megaraid_sas bnx2 kernel: [2337728.094177] Pid: 8685, comm: vhost-8683 Tainted: G W3.2.0-31-generic #50-Ubuntu kernel: [2337728.094179] Call Trace: kernel: [2337728.094180]IRQ [81066d7f] warn_slowpath_common+0x7f/0xc0 kernel: [2337728.094185] [81066e76] warn_slowpath_fmt+0x46/0x50 kernel: [2337728.094188] [8153f581] skb_gso_segment+0x341/0x3b0 kernel: [2337728.094191] [81542ee1] dev_hard_start_xmit+0xc1/0x540 kernel: [2337728.094196] [a01c0150] ? br_flood+0xc0/0xc0 [bridge] kernel: [2337728.094199] [8154360a] dev_queue_xmit+0x2aa/0x420 kernel: [2337728.094203] [a01c01e2] br_dev_queue_push_xmit+0x92/0xd0 [bridge] kernel: [2337728.094208] [a01c0278] br_forward_finish+0x58/0x60 [bridge] kernel: [2337728.094212] [a01c042b] __br_forward+0xab/0xd0 [bridge] kernel: [2337728.094217] [a01c04ed] br_forward+0x5d/0x70 [bridge] kernel: [2337728.094221] [a01c11c2] br_handle_frame_finish+0x182/0x2a0 [bridge] kernel: [2337728.094226] [a01c14a8] br_handle_frame+0x1c8/0x270 [bridge] kernel: [2337728.094231] [a01c12e0] ? br_handle_frame_finish+0x2a0/0x2a0 [bridge] kernel: [2337728.094234] [81540892] __netif_receive_skb+0x1e2/0x520 kernel: [2337728.094237] [81540ff1] process_backlog+0xb1/0x190 kernel: [2337728.094240] [815422e4] net_rx_action+0x134/0x290 kernel: [2337728.094242] [8165a4fe] ? _raw_spin_lock+0xe/0x20 kernel: [2337728.094245] [8106e528] __do_softirq+0xa8/0x210 kernel: [2337728.094248] [81664d6c] call_softirq+0x1c/0x30 kernel: [2337728.094249]EOI [81015305] do_softirq+0x65/0xa0 kernel: [2337728.094254] [815427c8] netif_rx_ni+0x28/0x30 kernel: [2337728.094258] [81478ec6] tun_get_user+0x306/0x4a0 kernel: [2337728.094261] [81479085] tun_sendmsg+0x25/0x30 kernel: [2337728.094265] [a01b09b6] handle_tx+0x296/0x530 [vhost_net] kernel: [2337728.094269] [a01b0c85] handle_tx_kick+0x15/0x20 [vhost_net] kernel: [2337728.094273] [a01ade3d] vhost_worker+0xdd/0x170 [vhost_net] kernel: [2337728.094276] [a01add60] ? vhost_set_memory+0x130/0x130 [vhost_net] kernel: [2337728.094279] [8108a03c] kthread+0x8c/0xa0 kernel: [2337728.094282] [81664c74] kernel_thread_helper+0x4/0x10 kernel: [2337728.094285] [81089fb0] ? flush_kthread_worker+0xa0/0xa0 kernel: [2337728.094287] [81664c70] ? gs_change+0x13/0x13 kernel: [2337728.094289] ---[ end trace a38cf088269411b3 ]--- kernel: [2337728.094731] [ cut here ] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: kvm vlan virtio problem
Hi, - Original Message - From: Bane Ivosev bane.ivo...@pmf.uns.ac.rs To: Bryan Venteicher bry...@daemoninthecloset.org, freebsd-stable@freebsd.org Sent: Saturday, November 3, 2012 7:58:57 PM Subject: Re: kvm vlan virtio problem thanks bryan, i don't have vlans inside guest. as you suggested i disabled nic tso ifconfig vtnet0 -tso and sysctl net.inet.tcp.tso=0 and so far, so good! everything is ok now. once again, thanks a lot. No need to disable TSO globally. So it seems if_vtnet sending down TSO frames that don't have the appropriate flags set. I'll look into it more in a next couple of days. Thanks for the quick reply back. Bryan On 11/03/2012 09:40 PM, Bryan Venteicher wrote: Hi, - Original Message - From: Bane Ivosevbane.ivo...@pmf.uns.ac.rs To: freebsd-stable@freebsd.org Sent: Saturday, November 3, 2012 2:12:25 PM Subject: kvm vlan virtio problem hi, i have several kvm ubuntu 12.04 and centos 6 hosts with standard bridged network setup. same problem on each server with freebsd 9 amd64 guest and virtio nic: soon after guest start host syslog is filling with this message at very high rate. guest is working without any problem. with e1000 guest driver eveything is ok. does enyone have/had same problem? thanks. I have a vague recollection of looking at something similar last year... Do you have VLAN configured in the guest as well? What is the ifconfig output? Does disabling TSO on the vtnetX device make these messages go away? Bryan kernel: [2337728.094141] [ cut here ] kernel: [2337728.094144] WARNING: at /build/buildd/linux-3.2.0/net/core/dev.c:1955 skb_gso_segment+0x341/0x3b0() kernel: [2337728.094146] Hardware name: System x3550 M3 -[7944K3G]- kernel: [2337728.094148] 802.1Q VLAN Support: caps=(0x30195833, 0x0) len=3196 data_len=0 ip_summed=0 kernel: [2337728.094149] Modules linked in: dm_snapshot ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables kvm_intel kvm dm_crypt nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc nls_iso8859_1 nls_cp437 vfat fat 8021q garp bridge stp serio_raw cdc_ether usbnet vhost_net macvtap i7core_edac macvlan shpchp ioatdma edac_core dca tpm_tis lp parport mac_hid btrfs zlib_deflate libcrc32c usbhid hid megaraid_sas bnx2 kernel: [2337728.094177] Pid: 8685, comm: vhost-8683 Tainted: G W3.2.0-31-generic #50-Ubuntu kernel: [2337728.094179] Call Trace: kernel: [2337728.094180]IRQ [81066d7f] warn_slowpath_common+0x7f/0xc0 kernel: [2337728.094185] [81066e76] warn_slowpath_fmt+0x46/0x50 kernel: [2337728.094188] [8153f581] skb_gso_segment+0x341/0x3b0 kernel: [2337728.094191] [81542ee1] dev_hard_start_xmit+0xc1/0x540 kernel: [2337728.094196] [a01c0150] ? br_flood+0xc0/0xc0 [bridge] kernel: [2337728.094199] [8154360a] dev_queue_xmit+0x2aa/0x420 kernel: [2337728.094203] [a01c01e2] br_dev_queue_push_xmit+0x92/0xd0 [bridge] kernel: [2337728.094208] [a01c0278] br_forward_finish+0x58/0x60 [bridge] kernel: [2337728.094212] [a01c042b] __br_forward+0xab/0xd0 [bridge] kernel: [2337728.094217] [a01c04ed] br_forward+0x5d/0x70 [bridge] kernel: [2337728.094221] [a01c11c2] br_handle_frame_finish+0x182/0x2a0 [bridge] kernel: [2337728.094226] [a01c14a8] br_handle_frame+0x1c8/0x270 [bridge] kernel: [2337728.094231] [a01c12e0] ? br_handle_frame_finish+0x2a0/0x2a0 [bridge] kernel: [2337728.094234] [81540892] __netif_receive_skb+0x1e2/0x520 kernel: [2337728.094237] [81540ff1] process_backlog+0xb1/0x190 kernel: [2337728.094240] [815422e4] net_rx_action+0x134/0x290 kernel: [2337728.094242] [8165a4fe] ? _raw_spin_lock+0xe/0x20 kernel: [2337728.094245] [8106e528] __do_softirq+0xa8/0x210 kernel: [2337728.094248] [81664d6c] call_softirq+0x1c/0x30 kernel: [2337728.094249]EOI [81015305] do_softirq+0x65/0xa0 kernel: [2337728.094254] [815427c8] netif_rx_ni+0x28/0x30 kernel: [2337728.094258] [81478ec6] tun_get_user+0x306/0x4a0 kernel: [2337728.094261] [81479085] tun_sendmsg+0x25/0x30 kernel: [2337728.094265] [a01b09b6] handle_tx+0x296/0x530 [vhost_net] kernel: [2337728.094269] [a01b0c85] handle_tx_kick+0x15/0x20 [vhost_net] kernel: [2337728.094273] [a01ade3d] vhost_worker+0xdd/0x170 [vhost_net] kernel: [2337728.094276] [a01add60
