VirtIO issues with suricata

[WolfAURman_IKrell]

Hello, everyone!
This post will show how to fix a problem with VM drivers with VirtIO. How can this fix be applied via proxmox? I tried passing them through args, it didn't work.
How then in this case how to correctly pass parameters in the configuration?
I tried to transmit in the following format:

args: \
  -netdev type=tap,id=net0,ifname=tap103i0,script=no,downscript=no,vhost=on,queues=8 -device virtio-net-pci,mac=BC:24:11:6A:36:40,netdev=net0,csum=off,gso=off,guest_tso4=off \
  -netdev type=tap,id=net1,ifname=tap103i1,script=no,downscript=no,vhost=on,queues=8 -device virtio-net-pci,mac=BC:24:11:36:52:86,netdev=net1,csum=off,gso=off,guest_tso4=off \
  -netdev type=tap,id=net3,ifname=tap103i3,script=no,downscript=no,vhost=on,queues=8 -device virtio-net-pci,mac=BC:24:11:CD:96:19,netdev=net3,csum=off,gso=off,guest_tso4=off

But alas, it didn't seem to work...

 

[dakralex]

Hi!

Currently, there is no option to add custom flags to the network device parameters. You could pass these via -args but bare in mind that the tap devices aren't created for them automatically, so they need to be set up manually or you could write a script that does that, but this is of course a little hacky. For some guidance how to do that, see [0]. You can also file a feature request for this at [1].

[0] https://wiki.qemu.org/Documentation/Networking#Setting_up_taps_on_Linux
[1] https://bugzilla.proxmox.com/enter_bug.cgi?product=pve&component=Qemu