Search results

When will the patch be released?

How did you revert the update?

It seems to happen when I add a firewall rule and action "REJECT", replacing the action to "DROP" and I no longer seem to get kernel panic.

Disabling the firewall seems to have fixed the issue.

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...

Any news on this? I'm stuck on version v6.0 due to that. Newer versions are unusable if you have USB passthrough.

Can I finally update Proxmox or is it still bugged? I reported the bug here by the way: https://bugzilla.proxmox.com/show_bug.cgi?id=2781

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...

I did

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 :/

Is there any way to downgrade Proxmox while this gets fixed?

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

I've been using this command to migrate VMs between nodes but today we upgraded nodes to the latest version and the command no longer works: vzdump $vm --stdout | ssh $host@$ip qmrestore - $vm --storage local --force INFO: sending archive to stdout INFO: starting kvm to execute backup task...

My drives are all local

I have a server: CPU: 2x Intel Xeon E5-2689 @ 2.6 GHz Mobo: Supermicro X9DRi-LN4F+ RAM: 72 GB ECC @ 1333 MHz HD: NVMe 970 EVO 256 GB, 2x 1 TB WD, 2x 500 GB SSD GPU: AMD RX 570 OS: Proxmox Every time I copy a big file from a drive to a different drive, iowait goes up to 80% and all VMs become...

Shouldn't it still throw an error instead of doing this?

dmesg I see [Mon Feb 24 12:46:52 2020] HTB: quantum of class 10001 is big. Consider r2q change. [Mon Feb 24 12:46:52 2020] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 [Mon Feb 24 12:46:52 2020] #PF error: [INSTR] [Mon Feb 24 12:46:52 2020] PGD 0 P4D 0 [Mon Feb 24...