VMs with rate limit and bridged network not booting: "RTNETLINK answers: No such file or directory"

[carles89]

Hi all,

I noticed that my VMs with bridged network can't boot when rate limit is enabled on any network interface. Without rate limit, they work OK.

Also, if I change network to NAT and I set a rate limit, VMs boot without problems.

Here is the error:

Running as unit 701.scope.
RTNETLINK answers: No such file or directory
We have an error talking to the kernel
command '/sbin/tc filter add dev tap701i0 parent ffff: prio 50 basic police rate 20971520bps burst 1048576b mtu 64kb drop flowid :1' failed: exit code 2
kvm: -netdev type=tap,id=net0,ifname=tap701i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on: network script /var/lib/qemu-server/pve-bridge failed with status 512
TASK ERROR: start failed: command '/usr/bin/systemd-run --scope --slice qemu --unit 701 -p 'KillMode=none' -p 'CPUShares=1000' /usr/bin/kvm -id 701 -chardev 'socket,id=qmp,path=/var/run/qemu-server/701.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/701.pid -daemonize -smbios 'type=1,uuid=38aa7f19-77fa-48e3-8e8b-0f2bf3d3934e' -name testing -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000' -vga std -vnc unix:/var/run/qemu-server/701.vnc,x509,password -no-hpet -cpu 'kvm64,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_relaxed,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce' -m 2048 -k es -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device 'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device 'usb-tablet,id=tablet,bus=uhci.0,port=1' -chardev 'socket,path=/var/run/qemu-server/701.qga,server,nowait,id=qga0' -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:6c68f7bef396' -drive 'if=none,id=drive-ide0,media=cdrom,aio=threads' -device 'ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=200' -drive 'file=/var/lib/vz/images/701/vm-701-disk-1.qcow2,if=none,id=drive-virtio0,cache=writeback,format=qcow2,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' -drive 'file=/mnt/pve/tsicloudstoragen0_images/images/701/vm-701-disk-1.qcow2,if=none,id=drive-virtio1,cache=writeback,format=qcow2,aio=threads,detect-zeroes=on' -device 'virtio-blk-pci,drive=drive-virtio1,id=virtio1,bus=pci.0,addr=0xb' -netdev 'type=tap,id=net0,ifname=tap701i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=3A:39:33:64:36:38,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1

Here are my package versions:

proxmox-ve: 4.1-39 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-22 (running version: 4.1-22/aca130cf)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.2.8-1-pve: 4.2.8-39
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-36
qemu-server: 4.0-64
pve-firmware: 1.1-7
libpve-common-perl: 4.0-54
libpve-access-control: 4.0-13
libpve-storage-perl: 4.0-45
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-9
pve-container: 1.0-52
pve-firewall: 2.0-22
pve-ha-manager: 1.0-25
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
fence-agents-pve: not correctly installed
openvswitch-switch: 2.3.2-2

Any thoughts on that?

Best regards,

Carles

 

[wbumiller]

Can you `modprobe cls_basic`?

 

[carles89]

Hi wbumiller,

Here is the output:

root@xxxxx:~# modprobe cls_basic
modprobe: ERROR: could not insert 'cls_basic': Exec format error

Regards

 

[wbumiller]

Can you try getting the exact revision of the package of the running kernel installed again (from /var/apt/cache) and try loading the module then?

 

[carles89]

Hi bumiller,

Sorry, I don't know what you're asking for. Do I need to reinstall the running kernel?

This is my /var/cache/apt directory:

root@xxxxxx:/var/cache/apt/archives# ls | grep kernel
pve-kernel-2.6.32-39-pve_2.6.32-156_amd64.deb
pve-kernel-2.6.32-39-pve_2.6.32-157_amd64.deb
pve-kernel-2.6.32-40-pve_2.6.32-159_amd64.deb
pve-kernel-2.6.32-40-pve_2.6.32-160_amd64.deb
pve-kernel-2.6.32-41-pve_2.6.32-163_amd64.deb
pve-kernel-2.6.32-41-pve_2.6.32-164_amd64.deb
pve-kernel-2.6.32-42-pve_2.6.32-165_amd64.deb
pve-kernel-2.6.32-43-pve_2.6.32-166_amd64.deb
pve-kernel-4.2.6-1-pve_4.2.6-28_amd64.deb
pve-kernel-4.2.6-1-pve_4.2.6-36_amd64.deb
pve-kernel-4.2.8-1-pve_4.2.8-37_amd64.deb
pve-kernel-4.2.8-1-pve_4.2.8-39_amd64.deb

And this is my running kernel:

root@xxxxx:~# uname -a
Linux xxxxx 4.2.8-1-pve #1 SMP Wed Feb 3 16:33:06 CET 2016 x86_64 GNU/Linux

Thank you

Best regards,

 

[wbumiller]

If you can afford downtime simply try a reboot, otherwise try:

# dpkg -i /var/cache/apt/archives/pve-kernel-4.2.8-1-pve_4.2.8-37_amd64.deb
# modprobe cls_basic

 

[carles89]

Hi wbumiller,

I installed the package and everything worked flawessly.

Thank you so much.

Best regards,