Hi, On 1/29/18 4:17 PM, Roberto Alvarado wrote: > Hi Folks, > > After upgrade a node I got the following problem if the VM have a traffic > shapping / network rate limit rule active, wont boot on the last version of > PVE kernel/Proxmox-VE: > > What is ":1"? > Usage: ... basic [ match EMATCH_TREE ] > [ action ACTION_SPEC ] [ classid CLASSID ] > > Where: SELECTOR := SAMPLE SAMPLE ... > FILTERID := X:Y:Z > ACTION_SPEC := ... look at individual actions
This sound like Bug 1637 [1] which was reported over the weekend. AFAICT there are two fixes, one in the iproute2 package - which got already rolled out to the community repository by now, and the following patch still waiting to get applied: https://pve.proxmox.com/pipermail/pve-devel/2018-January/030526.html [1]: https://bugzilla.proxmox.com/show_bug.cgi?id=1637 Quoting Wolfgang from the bug report: > Can you test iproute2>=4.13.0-3 from the pve-no-subscription repositories? The second patch should get in soon. cheers, Thomas > > NOTE: CLASSID is parsed as hexadecimal input. > command '/sbin/tc filter add dev tap104i0 parent ffff: prio 50 basic police > rate 1048576bps burst 1048576b mtu 64kb drop flowid :1' failed: exit code 1 > kvm: -netdev > type=tap,id=net0,ifname=tap104i0,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 256 > TASK ERROR: start failed: command '/usr/bin/kvm -id 104 -chardev > 'socket,id=qmp,path=/var/run/qemu-server/104.qmp,server,nowait' -mon > 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/104.pid -daemonize > -smbios 'type=1,uuid=da4227fc-04e6-451a-8f28-488fbb3f5334' -name DH.local > -smp ‘2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot > 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' > -vga std -vnc unix:/var/run/qemu-server/104.vnc,x509,password -cpu > kvm64,+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/104.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:743a2495d1c0' -drive > 'if=none,id=drive-ide2,media=cdrom,aio=threads' -device > 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -drive > 'file=/mnt/pve/NFSNode-NX/images/104/vm-104-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' > -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=E6:64:81:D3:48:08,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' > -rtc ‘base=localtime'' failed: exit code 1 > > If you try to enable the rate limit on a running VM of the node: > > Parameter verification failed. (400) > net0: hotplug problem - command '/sbin/tc filter add dev tap104i0 parent > ffff: prio 50 basic police rate 1048576bps burst 1048576b mtu 64kb drop > flowid :1' failed: exit code > > But if remove the rate limit from the network card of the VM, starts without > problem. > > > The VM Config with the rate limit: > > agent: 1 > bootdisk: virtio0 > cores: 2 > ide2: none,media=cdrom > localtime: 1 > memory: 2048 > name: DH.local > net0: virtio=E6:64:81:D3:48:08,bridge=vmbr300,rate=1 > numa: 0 > ostype: l26 > smbios1: uuid=da4227fc-04e6-451a-8f28-488fbb3f5334 > sockets: 1 > virtio0: NFSNode-NX:104/vm-104-disk-1.qcow2,cache=writeback,size=50G > > > The VM Config without the rate limit: > > agent: 1 > bootdisk: virtio0 > cores: 2 > ide2: none,media=cdrom > localtime: 1 > memory: 2048 > name: DH.local > net0: virtio=E6:64:81:D3:48:08,bridge=vmbr300 > numa: 0 > ostype: l26 > smbios1: uuid=da4227fc-04e6-451a-8f28-488fbb3f5334 > sockets: 1 > virtio0: NFSNode-NX:104/vm-104-disk-1.qcow2,cache=writeback,size=50G > > > > Information about the version with the problem: > > root@nx6:/var/log# pveversion --verbose > proxmox-ve: 5.1-38 (running kernel: 4.13.13-5-pve) > pve-manager: 5.1-43 (running version: 5.1-43/bdb08029) > pve-kernel-4.13.13-4-pve: 4.13.13-35 > pve-kernel-4.13.13-2-pve: 4.13.13-33 > pve-kernel-4.13.13-5-pve: 4.13.13-38 > pve-kernel-4.13.13-3-pve: 4.13.13-34 > libpve-http-server-perl: 2.0-8 > lvm2: 2.02.168-pve6 > corosync: 2.4.2-pve3 > libqb0: 1.0.1-1 > pve-cluster: 5.0-19 > qemu-server: 5.0-20 > pve-firmware: 2.0-3 > libpve-common-perl: 5.0-25 > libpve-guest-common-perl: 2.0-14 > libpve-access-control: 5.0-7 > libpve-storage-perl: 5.0-17 > pve-libspice-server1: 0.12.8-3 > vncterm: 1.5-3 > pve-docs: 5.1-16 > pve-qemu-kvm: 2.9.1-6 > pve-container: 2.0-18 > pve-firewall: 3.0-5 > pve-ha-manager: 2.0-4 > ksm-control-daemon: 1.2-2 > glusterfs-client: 3.8.8-1 > lxc-pve: 2.1.1-2 > lxcfs: 2.0.8-1 > criu: 2.11.1-1~bpo90 > novnc-pve: 0.6-4 > smartmontools: 6.5+svn4324-1 > root@nx6:/var/log# uname -a > Linux nx6 4.13.13-5-pve #1 SMP PVE 4.13.13-38 (Fri, 26 Jan 2018 10:47:09 > +0100) x86_64 GNU/Linux > root@nx6:/var/log# > > > But in this version of pve, a VM with a rate limit works without problems and > the VM boots normally: > > root@nx7:/etc/pve/qemu-server# pveversion --verbose > proxmox-ve: 5.1-36 (running kernel: 4.13.13-5-pve) > pve-manager: 5.1-42 (running version: 5.1-42/724a6cb3) > pve-kernel-4.13.4-1-pve: 4.13.4-26 > pve-kernel-4.13.13-4-pve: 4.13.13-35 > pve-kernel-4.13.13-2-pve: 4.13.13-33 > pve-kernel-4.13.13-5-pve: 4.13.13-36 > pve-kernel-4.13.13-3-pve: 4.13.13-34 > libpve-http-server-perl: 2.0-8 > lvm2: 2.02.168-pve6 > corosync: 2.4.2-pve3 > libqb0: 1.0.1-1 > pve-cluster: 5.0-19 > qemu-server: 5.0-19 > pve-firmware: 2.0-3 > libpve-common-perl: 5.0-25 > libpve-guest-common-perl: 2.0-14 > libpve-access-control: 5.0-7 > libpve-storage-perl: 5.0-17 > pve-libspice-server1: 0.12.8-3 > vncterm: 1.5-3 > pve-docs: 5.1-16 > pve-qemu-kvm: 2.9.1-6 > pve-container: 2.0-18 > pve-firewall: 3.0-5 > pve-ha-manager: 2.0-4 > ksm-control-daemon: 1.2-2 > glusterfs-client: 3.8.8-1 > lxc-pve: 2.1.1-2 > lxcfs: 2.0.8-1 > criu: 2.11.1-1~bpo90 > novnc-pve: 0.6-4 > smartmontools: 6.5+svn4324-1 > zfsutils-linux: 0.7.3-pve1~bpo9 > root@nx7:/etc/pve/qemu-server# uname -a > Linux nx7 4.13.13-5-pve #1 SMP PVE 4.13.13-36 (Mon, 15 Jan 2018 12:36:49 > +0100) x86_64 GNU/Linux > root@nx7:/etc/pve/qemu-server# > > Someone with the same problem???? > > Thanks! > > Regards > > Roberto > > > _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
