Proxmox VE 8.3 released!

[uberarchiver]

Please run debsums -s.
If it doesn't show any changed packages, then you may want to run a memtest on your host.

Did you upgrade the kernel recently? Does it also happen with the previous kernel?

debsums -s

The host is running ECC-memory:

ras-mc-ctl --errors
No Memory errors.

No PCIe AER errors.

No Extlog errors.

No MCE errors.

Kernel upgraded to 6.8.12-4-pve from 6.8.8-4-pve
I have not witnessed this problem before. Is it possible that it is a bug in vncproxy ?
I was doing upgrades to a few Ubuntu VMs. As normal there is very intensive screen updating happening then...

Rgds

 

[mira]

I'd suggest to move this to a separate thread. Could you open one and @ me there?
Please also provide the journal covering a few minutes (~10) before and after the segfaults.

 

[blackpaw]

try upgrade the kernel to 6.11, for me it was the solution.

I'm on 6.8.12-4-pve, not seeing any 6.11 in the repos.

Edit: Found it, was showing in cmd line auto complete for some reason. Installed, we'll see how it goes.

Thanks.

 

[maarvien]

I recently performed a fresh installation of PVE 8.3. However, after starting the host I noticed it was using about 7GB of memory out of the available 96GB. Is this normal behavior?

For the boot disk, I chose Btrfs instead of ZFS, similar to another host I set up previously, which started with around 1.8GB of memory usage.

Any insights or advice would be appreciated!

 

[t.lamprecht]

However, after starting the host I noticed it was using about 7GB of memory out of the available 96GB. Is this normal behavior?

How did you measure that? It can be fine if it's used for some caches, as unused memory is basically wasted memory and those caches can be made available if more memory is actually required by programs/VMs. But if an idle PVE installation uses 7 GB of memory that cannot be made available it would be rather odd – here a fresh installation uses roughly 1.3 GB of memory.

 

[maarvien]

Hi Thomas,

i did try again with fresh install but same result and only 1 SSD disk (boot drive is partitioned)
On a other system with a intel xeon it uses 1.2 GB so i dont know why it use this much on this server

 

[David123]

what's the status on nftables now?

Is it recommended to enable it for an existing server without much trouble (just ticking it in the DC > server > firewall tab) ?

I noticed when doing it it moved all rules correctly but:

pve-firewall restart
pve-firewall status


Status: enabled/running (pending changes)

 

[fiona]

Hi,

what's the status on nftables now?

while at lot of work was/is being done to shape it up, the nftables-based firewall is still in "tech preview" status, see the docs: https://pve.proxmox.com/pve-docs/chapter-pve-firewall.html#pve_firewall_nft

Is it recommended to enable it for an existing server without much trouble (just ticking it in the DC > server > firewall tab) ?

Again, it is still in tech preview, so you might run into bugs/incompatibilities with certain edge cases. I'd not recommend it yet for production use in sensitive environments, it will be announced when it's ready for that

I noticed when doing it it moved all rules correctly but:

pve-firewall restart
pve-firewall status


Status: enabled/running (pending changes)

How long did you wait after the restart? Anything in the system logs/journal?

 

[David123]

How long did you wait after the restart? Anything in the system logs/journal?

I ran the restart command because pve-firewall status showed (pending changes)

journalctl -f doesn't show anything new when enabling / disabling it. When enabling it, pve-firewall.log starts to get entries. It never gets that on iptables

0 5 - 09/Dec/2024:00:00:05 +0100 starting pvefw logger
735 7 guest-735-in 09/Dec/2024:10:28:56 +0100 ACCEPT: OUT=fwbr735i1 PHYSOUT=tap735i1
..

 

[fiona]

I ran the restart command because pve-firewall status showed (pending changes)

journalctl -f doesn't show anything new when enabling / disabling it. When enabling it, pve-firewall.log starts to get entries. It never gets that on iptables

0 5 - 09/Dec/2024:00:00:05 +0100 starting pvefw logger
735 7 guest-735-in 09/Dec/2024:10:28:56 +0100 ACCEPT: OUT=fwbr735i1 PHYSOUT=tap735i1
..

Please open a new thread (to avoid making the announcement thread here less readable) and provide the details of your configuration (i.e. firewall configuration files, package versions, etc.).