Every now and then my server kernel panic so I set up netconsole to see what's the culprit and it seems to be related to firewall(?)
Any idea how to fix that?
Here are the logs:
[494221.511181] skbuff: skb_under_panic: text:00000000f0c6c75f len:74 put:14 head:000000001bebe299...
I managed to downgrade using this command:
apt install proxmox-ve=6.1-2 pve-manager=6.1-11 pve-kernel-helper=6.1-9 corosync=3.0.3-pve1 criu=3.11-3 glusterfs-client=5.5-3 ifupdown=0.8.35+pve1 ksm-control-daemon=1.3-1 libjs-extjs=6.0.1-10 libknet1=1.15-pve1 libproxmox-acme-perl=1.0.2...
If I have 500 Mbps down/50 Mbps up I'd want to only limit upload.
Many providers offer a download "burst" where download could burst to 10 Gbps, but upload is 1 Gbps, no burst, so I could limit download to say 5 Gbps and upload 500 Mbps
This only downgrades Proxmox's meta package. We'd need to downgrade qemu, but there are many dependencies, so I don't think it's possible. I'll have to wait I guess :/
I have passed through USB ports to my VM. When I unplug a device from these ports, VM freezes, VM stats keep loading forever and I can't stop it. I must kill it manually. It worked fine on PVE 6.1 This started happening after I upgraded.
VM config:
To clarify things, the container runs out of RAM. but the host has plenty of free RAM. Shouldn't it kill the process instead of killing the whole container?
My LXC container gets killed for running out of RAM. Is this a normal behaviour?
Here's syslog: https://pastebin.com/8c6t8XLF
I'm running latest Proxmox version
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.