My machines crashes


Dec 26, 2009
New York, USA

my machine crash and fails to boot after reboot. I do not know what the exactly happens but all my servers with this configuration after reboot crashes.

omega:~# pveversion -v
pve-manager: 1.5-7 (pve-manager/1.5/4660)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.24-7-pve: 2.6.24-11
pve-kernel-2.6.18-2-pve: 2.6.18-5
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5

modprobe ip_tables
modprobe iptable_filter
modprobe ipt_LOG
modprobe ipt_multiport
modprobe xt_multiport
modprobe ipt_REJECT
modprobe ipt_state
modprobe xt_state
modprobe ipt_limit
modprobe xt_limit
modprobe ipt_recent
modprobe ipt_owner
modprobe iptable_nat
modprobe ipt_REDIRECT


IPTABLES="ipt_REJECT ipt_owner ipt_REDIRECT ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp"

I think it can cause the ip_conntrack module.

How to solve this problem?
"A kernel crash could occur if a container was started before the conntrack modules were loaded and 'iptstate' was executed inside the container."

Actually, try to test it with the same config.


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!