Dear technicians & Proxmox devs,
lets start it this way - I think I've found an issue and I'm more or less out of ideas on how to continue debugging / solving the issue at all.
In use:
Proxmox 5.2 details:
running on:
Inside the system Intel Corporation 82576 (igb module) being used. 2 Onboard, 2 on pcie card.
Now let's take a vanilla template from Proxmox site (Ubuntu 14.04, CentOS 7), create 2 lxc container with any of the OS and start them both. After starting just shutdown them and do a simple pct start again. This will work. Now lets start both and create an IPTables firewall rule like this inside the container:
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
Shutdown the container and try to start it again. It will result in a hanging lxc monitor process like this:
root 5036 1 0 13:41 ? 00:00:00 /usr/bin/lxc-start -n 9135
root 5040 1 2 13:41 ? 00:00:00 [lxc monitor] /var/lib/lxc 9135
root 5130 2569 0 13:41 ? 00:00:00 lxc-info -n 9135 -p
After doing a kill -9 5040 at least pct list command works again but only way found to solve this and get the container at least started again is to reboot the Proxmox node itself.
I've tried a lot of things like updating the igb module to the really latest version, tried to play with SR-IOV, used Ubuntu instead of CentOS, downgrading/upgrading kernel, used a container restore from another Proxmox 5 System known to shutdown and start there without any issues - no way. If there is a single iptables rule being created inside the container the container can be stopped but never be restarted without prior reboot of the node.
Last hope now is that someone in forum is getting an idea from the details on how to solve this issue.
Thanks for reading my lines and for help
Andreas
lets start it this way - I think I've found an issue and I'm more or less out of ideas on how to continue debugging / solving the issue at all.
In use:
Proxmox 5.2 details:
Code:
proxmox-ve: 5.2-2 (running kernel: 4.15.18-5-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-8
pve-kernel-4.13: 5.2-2
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-3-pve: 4.15.18-22
pve-kernel-4.15.18-1-pve: 4.15.18-19
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.13.16-4-pve: 4.13.16-51
pve-kernel-4.13.4-1-pve: 4.13.4-26
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-29
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-35
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve1~bpo1running on:
Code:
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 2.1c
Release Date: 08/03/2012
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
ISA is supported
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 8.16
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Supermicro
Product Name: X8DTU
Version: 1234567890
Serial Number: 1234567890
UUID: 12345678-0200-900A-2500-1234567890AB
Wake-up Type: Power Switch
SKU Number: To Be Filled By O.E.M.
Family: ServerInside the system Intel Corporation 82576 (igb module) being used. 2 Onboard, 2 on pcie card.
Now let's take a vanilla template from Proxmox site (Ubuntu 14.04, CentOS 7), create 2 lxc container with any of the OS and start them both. After starting just shutdown them and do a simple pct start again. This will work. Now lets start both and create an IPTables firewall rule like this inside the container:
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
Shutdown the container and try to start it again. It will result in a hanging lxc monitor process like this:
root 5036 1 0 13:41 ? 00:00:00 /usr/bin/lxc-start -n 9135
root 5040 1 2 13:41 ? 00:00:00 [lxc monitor] /var/lib/lxc 9135
root 5130 2569 0 13:41 ? 00:00:00 lxc-info -n 9135 -p
After doing a kill -9 5040 at least pct list command works again but only way found to solve this and get the container at least started again is to reboot the Proxmox node itself.
I've tried a lot of things like updating the igb module to the really latest version, tried to play with SR-IOV, used Ubuntu instead of CentOS, downgrading/upgrading kernel, used a container restore from another Proxmox 5 System known to shutdown and start there without any issues - no way. If there is a single iptables rule being created inside the container the container can be stopped but never be restarted without prior reboot of the node.
Last hope now is that someone in forum is getting an idea from the details on how to solve this issue.
Thanks for reading my lines and for help
Andreas
