Bezüglich Vincenzo Maffione's Nachricht vom 21.11.2017 09:39 (localtime): … > > If this is the case, although you are allowed to do that, I don't think > it's a convenient way to use netmap. > Since VLAN interfaces like vlan0 do not have (and cannot have) native > netmap support, you are falling back to emulated netmap adapters (which > are probably buggy on FreeBSD, specially when combined with VALE). > Apart from bugs I think that with this setup you can't get decent > performance that would justify using netmap rather than the standard > kernel bridge and TAP devices.
Hello, lockup happened earlier than expected. This time 'vale-ctl' still reported (-l) the configuration. One guest, using if_vtnet(4)-virtio-net#vale2:korso, showed: dmz: watchdog timeout on queue 0 (dmz is the renamed if_vtnet(4)) I could attach tcpdump to the uplink interface and also to all vlan children. Complete silence everywhere. So it seems the nic stopped processing anything. Do you think that symptom could be caused by my special vale integration, so that bugs in netmap emulation could crash the NIC? Or is it unlikely that this is related. I hadn't prepared a debug kernel for the host, so the machine rebooted without again. I think I'll have to start with replacing vale first, to narrow down possible causes. Today I was lucky, the lockup happend after business hours, but I won't rely on that. At least I know if I really need to look for a debug netmap kernel, or possibly there's something else... Thanks, -harry _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
