search for: mytap

...g the device. In tun_set_iff(): if (!!(ifr->ifr_flags & IFF_MULTI_QUEUE) != !!(tun->flags & IFF_MULTI_QUEUE)) return -EINVAL; so if you've configured QEMU to use multiqueue, the you need to use: $ ip tuntap add dev mytap mode tap vnet_hdr multi_queue actually vnet_hdr doesn't matter as that can be set on the fly but multi_queue is mandatory. Without it, I get the same EINVAL error as you mention. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://li...

hmmm, I thought := assigned a key just like +=, except := locked it so it could not be changed later. Am I misunderstanding the man page for udev? Thanks, John H. Nyhuis Desk: (206)-685-8334 jnyhuis at uw.edu Box 359461, 15th floor, 106 On 10/29/2019 4:31 PM, Leon Fauster via CentOS wrote: > Am 29.10.19 um 23:41 schrieb John H Nyhuis: >> Thanks, I did catch the mistype (after IU

Hello, On KubeVirt, we are trying to pre-create a tap device, then instruct libvirt to consume it (via the type=ethernet , managed='no' attributes). It works as expected, **unless** when we create a multi-queue tap device. The difference when creating the tap device is that we set the multi-queue flag; libvirt throws the following error when consuming it: ``` LibvirtError(Code=38,