Proxmox disable vmbr0 port after container shutdown

[Yoel Villarreal]

If I reboot physical machine with latest proxmox 5.1 then the host start normally all my CT and VM, but if I need to shutdown any random CT and try to start again y got this in /var/log/syslog:

Dec 19 16:51:51 nodo1 pvedaemon[9155]: shutdown CT 107: UPID:nodo1:000023C3:0014B4E3:5A3989F7:vzshutdown:107:root@pam:
Dec 19 16:51:51 nodo1 kernel: vmbr0: port 17(veth107i0) entered disabled state
Dec 19 16:51:51 nodo1 kernel: vmbr0: port 17(veth107i0) entered disabled state
Dec 19 16:51:51 nodo1 kernel: device veth107i0 left promiscuous mode
Dec 19 16:51:51 nodo1 kernel: vmbr0: port 17(veth107i0) entered disabled state
Dec 19 16:51:52 nodo1 pvedaemon[2161]: unable to get PID for CT 107 (not running?)
Dec 19 16:51:53 nodo1 pvedaemon[2161]: unable to get PID for CT 107 (not running?)
Dec 19 16:51:54 nodo1 pvedaemon[2160]: <root@pam> end task UPID:nodo1:000023C3:0014B4E3:5A3989F7:vzshutdown:107:root@pam: OK
Dec 19 16:52:06 nodo1 pvedaemon[9423]: starting CT 107: UPID:nodo1:000024CF:0014BAB8:5A398A06:vzstart:107:root@pam:
Dec 19 16:52:06 nodo1 pvedaemon[2161]: <root@pam> starting task UPID:nodo1:000024CF:0014BAB8:5A398A06:vzstart:107:root@pam:
Dec 19 16:52:06 nodo1 systemd[1]: Starting PVE LXC Container: 107...
Dec 19 16:52:07 nodo1 kernel: EXT4-fs (dm-20): mounted filesystem with ordered data mode. Opts: (null)
Dec 19 16:52:07 nodo1 kernel: IPv6: ADDRCONF(NETDEV_UP): veth107i0: link is not ready
Dec 19 16:52:07 nodo1 kernel: vmbr0: port 17(veth107i0) entered blocking state
Dec 19 16:52:07 nodo1 kernel: vmbr0: port 17(veth107i0) entered disabled state
Dec 19 16:52:07 nodo1 kernel: device veth107i0 entered promiscuous mode
Dec 19 16:52:37 nodo1 pveproxy[12567]: proxy detected vanished client connection
Dec 19 16:53:36 nodo1 systemd[1]: pve-container@107.service: Start operation timed out. Terminating.
Dec 19 16:53:36 nodo1 systemd[1]: Failed to start PVE LXC Container: 107.
Dec 19 16:53:36 nodo1 systemd[1]: pve-container@107.service: Unit entered failed state.
Dec 19 16:53:36 nodo1 systemd[1]: pve-container@107.service: Failed with result 'timeout'.
Dec 19 16:53:36 nodo1 pvedaemon[9423]: command 'systemctl start pve-container@107' failed: exit code 1
Dec 19 16:53:36 nodo1 pvedaemon[2161]: <root@pam> end task UPID:nodo1:000024CF:0014BAB8:5A398A06:vzstart:107:root@pam: command 'systemctl start pve-container@107' failed: exit code 1

and got a nice thread of my cpu 100% load as stated in attachment pictures, I even lost comms via webgui, but ssh to physical host is still accesible, you can see how vmbr0 port 17 got destroyed after CT 107 stop, but it can't start again because somethig is wrong with veth in ports 48 and 49



Can anyone help me with this ? I had an offline proxmox 3.4 and nothing of this happened ever. Now I made a fresh install and found this. Thanks in advance

 

[ONE FOTON]

hello I have a different problem but with the same error code

kvm: -drive if=pflash,unit=1,format=raw,id=drive-efidisk0,file=/var/lib/vz/images/107/vm-107-disk-2.qcow2: PC system firmware (pflash) must be a multiple of 0x1000
TASK ERROR: start failed: command '/usr/bin/kvm -id 107 -chardev 'socket,id=qmp,path=/var/run/qemu-server/107.qmp,server,nowait' -mon 'chardev=qmp,mode=control' -pidfile /var/run/qemu-server/107.pid -daemonize -smbios 'type=1,uuid=3bced6bc-f1a0-4454-a7a2-18b314505727' -drive 'if=pflash,unit=0,format=raw,readonly,file=/usr/share/kvm/OVMF_CODE-pure-efi.fd' -drive 'if=pflash,unit=1,format=raw,id=drive-efidisk0,file=/var/lib/vz/images/107/vm-107-disk-2.qcow2' -name WIN10PRO4 -smp '4,sockets=1,cores=4,maxcpus=4' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -vga none -nographic -no-hpet -cpu 'host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=proxmox,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,kvm=off' -m 6145 -k es -readconfig /usr/share/qemu-server/pve-q35.cfg -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' -device 'vfio-pci,host=03:00.0,id=hostpci0,bus=pci.0,addr=0x10' -device 'vfio-pci,host=03:00.1,id=hostpci1,bus=pci.0,addr=0x11' -device 'vfio-pci,host=04:00.0,id=hostpci2,bus=pci.0,addr=0x1b' -device 'vfio-pci,host=04:00.1,id=hostpci3,bus=pci.0,addr=0x1c' -chardev 'socket,path=/var/run/qemu-server/107.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:d99d8bd2022' -device 'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive 'file=/var/lib/vz/images/107/vm-107-disk-1.qcow2,if=none,id=drive-scsi0,discard=on,format=qcow2,cache=none,aio=native,detect-zeroes=unmap' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap107i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' -device 'virtio-net-pci,mac=AA:52:25:9A:89:87,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300' -rtc 'driftfix=slew,base=localtime' -machine 'type=q35' -global 'kvm-pit.lost_tick_policy=discard'' failed: exit code 1

the vm is a win 10 that works well! I do not know what this error was!
do not modify anything in this machine and the problem points to the UEFI disk drive.
If someone has any idea how to solve it, it would be very helpful