testing whether the https://kernel.ubuntu.com/mainline/v6.16/ and https://kernel.ubuntu.com/mainline/v6.16.12/ kernels are showing the issue on your system(s) would be highly appreciated to narrow down the cause. we still cannot reproduce any...
Hi,
could you also install debugger and debug symbols with apt install pve-qemu-kvm-dbgsym gdb and while the VM is stuck, run the following script:
root@pve8a1 ~ # cat stacks-stats.sh
#/bin/bash
VMID=$1
if [ -z $VMID ]
then
echo "usage: $0...
Hi @MiamiJack ,
Ensure you have a line search your_hostname_server at the top of file /etc/resolv.conf
Example:
root@a:~# cat /etc/resolv.conf
search a.node1.example.com
nameserver 1.1.1.1
nameserver 8.8.8.8
Hope this help!
We're very excited to present the first stable release of our new Proxmox Datacenter Manager!
Proxmox Datacenter Manager is an open-source, centralized management solution to oversee and manage multiple, independent Proxmox-based environments...
there is nothing to worry about
it is the temperature on the Fahrenheit scale
for example:
75F = 24C
85F = 30C
115F = 46C
Worry about the SSD when the temperature reaches:
149F - 65C = attention - check cooling
158F - 70C = critical - replace the...
We're pleased to announce the release of Proxmox Backup Server 4.1.
This version is based on Debian 13.2 (“Trixie”), uses Linux kernel 6.17.2-1 as the new stable default, and comes with ZFS 2.3.4 for reliable, enterprise-grade storage and...
We're proud to present the next iteration of our Proxmox Virtual Environment platform. This new version 9.1 is the first point release since our major update and is dedicated to refinement.
This release is based on Debian 13.2 "Trixie" but we're...
I have updated my original post with the latest information, stating that kernel 6.17 seems to fix the issues according to the reports we got until now, and that kernel 6.17 is now the default in Proxmox VE 9.1.
EDIT: This post has been edited with the newest information we currently have.
From multiple reports over the last weeks, we can confirm that the issue is caused by:
Intel ICE drivers used by multiple Intel NICs, at least in combination with...