I wanted to add some more information to the reproducer for posterity: On 09/01/2025 10:06, Friedrich Weber wrote: > > [1] > > - Hypervisor is Proxmox VE 8.3 (QEMU/KVM)
Hypervisor kernel is Proxmox VE's 6.11.0-2-pve (I wouldn't expect it to matter here). > - VM has 4 cores, 8G RAM, 3x virtio-net NICs (one for management, two for > bond0) This description is maybe a bit too brief. Here is the upstream QEMU 9.2.0 command line I've been using for the Arch VM. It still contains some Proxmox VE specifics, but hopefully it's still useful: /path/to/qemu-9.2.0/build/qemu-system-x86_64 \ -accel kvm \ -name 'arch-ovs,debug-threads=on' \ -chardev 'socket,id=qmp,path=/var/run/qemu-server/104.qmp,server=on,wait=off' \ -mon 'chardev=qmp,mode=control' \ -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' \ -mon 'chardev=qmp-event,mode=control' \ -pidfile /var/run/qemu-server/104.pid \ -smbios 'type=1,uuid=6f651eed-e73a-44bd-9f6c-e644eafa8bfc' \ -smp '4,sockets=1,cores=4,maxcpus=4' \ -nodefaults \ -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' \ -vnc 'unix:/var/run/qemu-server/104.vnc,password=on' \ -cpu qemu64,+aes,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+pni,+popcnt,+sse4.1,+sse4.2,+ssse3 \ -m 8192 \ -object 'iothread,id=iothread-virtioscsi0' \ -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' \ -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' \ -device 'pci-bridge,id=pci.3,chassis_nr=3,bus=pci.0,addr=0x5' \ -device 'vmgenid,guid=94b7cdf8-9e24-4cb8-9bd5-6246cad1f8ba' \ -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' \ -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' \ -device 'VGA,id=vga,bus=pci.0,addr=0x2' \ -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3,free-page-reporting=on' \ -drive 'file=/dev/zvol/zplansch/vm-104-cloudinit,if=none,id=drive-ide0,media=cdrom,format=raw,aio=io_uring' \ -device 'ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0' \ -drive 'if=none,id=drive-ide2,media=cdrom,aio=io_uring' \ -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=101' \ -device 'virtio-scsi-pci,id=virtioscsi0,bus=pci.3,addr=0x1,iothread=iothread-virtioscsi0' \ -drive 'file=/dev/zvol/zplansch/vm-104-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=io_uring,detect-zeroes=on' \ -device 'scsi-hd,bus=virtioscsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' \ -netdev 'type=tap,id=net0,ifname=tap104i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' \ -device 'virtio-net-pci,mac=BA:FF:FF:6B:6B:07,netdev=net0,bus=pci.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256,bootindex=102' \ -netdev 'type=tap,id=net1,ifname=tap104i1,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' \ -device 'virtio-net-pci,mac=BA:FF:FF:E8:61:F2,netdev=net1,bus=pci.0,addr=0x13,id=net1,rx_queue_size=1024,tx_queue_size=256' \ -netdev 'type=tap,id=net2,ifname=tap104i2,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' \ -device 'virtio-net-pci,mac=BA:FF:FF:DD:4C:0B,netdev=net2,bus=pci.0,addr=0x14,id=net2,rx_queue_size=1024,tx_queue_size=256' \ -machine 'type=pc' Just to be clear, the user who originally hit this issue did so on a bare metal setup, not inside a VM. _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
