issues occured again tonight after downgrade to 5.4.0-121-generic
but the system seems didn't freeze totally and the cpu Utilization also didn't reach to 100%
network connection didn't work
Ubuntu 20.04.04 machine freezes
- Thread starter AxisNL
- Start date
but the system seems didn't freeze totally and the cpu Utilization also didn't reach to 100%
network connection didn't work
Just wanted to update and say that I resolved my issue by turning-off all power saving features, including c-states - hasn't happened since
I am having exactly the same issues - host CPU is a Celeron J6412 (Protectli VP2420), the Proxmox 8.0.3 host is running 2 VMs and is lightly loaded. This is my first Proxmox host, moving away from ESXi, so the setup is fairly vanilla.
The first VM, pfSense firewall, runs perfectly with no issues whatsoever. The Ubuntu 22.04.3 VM crashes sporadically, generally through the night it seems and when it has crashed the memory is always maxed out and one CPU is running 100%. As a test I increased the guest RAM from 8GB to 16GB and the crashes happen less frequently but still do happen.
@JohnBee Where did you disable power savings? In the Ubuntu guest or in Proxmox host? Any clues to what you did gratefully received.
The first VM, pfSense firewall, runs perfectly with no issues whatsoever. The Ubuntu 22.04.3 VM crashes sporadically, generally through the night it seems and when it has crashed the memory is always maxed out and one CPU is running 100%. As a test I increased the guest RAM from 8GB to 16GB and the crashes happen less frequently but still do happen.
@JohnBee Where did you disable power savings? In the Ubuntu guest or in Proxmox host? Any clues to what you did gratefully received.
Have you tried installing the latest Intel microcode? The freezing issue is a known one that is nearly always resolved by updating the microcode. If you search these forums, there's plenty of guides on how to do it and why it's required.
Thank you for the hint. My searches took me here and I updated the Debian Firmware Repository and ran
but I get the same results -
Did I miss something here? The output from apt showed the latest microcode version that Ubuntu lists, is it necessary to go to the latest 'unstable' version? I ran this on the guest VM but should this be updating the microcode on the Proxmox host? Apologies for the beginner questions
Running
did give lots of updates mentioning firmware so perhaps that will help. I did this to the host too.
Code:
apt install intel-microcode
Code:
# grep microcode /proc/cpuinfo | uniq
microcode : 0x1
# dmesg | grep microcode
[ 0.295779] MDS: Vulnerable: Clear CPU buffers attempted, no microcodeDid I miss something here? The output from apt showed the latest microcode version that Ubuntu lists, is it necessary to go to the latest 'unstable' version? I ran this on the guest VM but should this be updating the microcode on the Proxmox host? Apologies for the beginner questions
Running
Code:
apt dist-upgrade
Last edited:
You'll need to add the non-free-firmware repositories to /etc/apt/sources.list
Then run:
Code:
# Include Intel microcode firmware
deb http://ftp.debian.org/debian bookworm main contrib non-free-firmware
deb http://ftp.debian.org/debian bookworm-updates main contrib non-free-firmwareThen run:
Code:
sudo apt update && sudo apt install intel-microcodeNew to proxmox but not virtualization, migrated from ESXi to Proxmox 8 and running several VMs including windows, ubuntu, etc. All of my VMs run fine except my Ubuntu VMs keep freezing. Only way to recover is to run "qm stop <100>" and restart the VM. I have 2 Ubuntu VMs and both freeze randomly my Windows, GNS3 Server, OpenSUSE all fine but my Ubuntu VMs having the issue. Disabled power controlls still same issue. Really frustrating to be honest. Also not running a NUC but using a Core i5:
Last edited:
Hi,
please share the output of
pveversion -v and qm config <ID> for the problematic VMs. Is there something obviously different in the configuration of the Ubuntu VMs and the other VMs? Do you see anything interesting in the host or guest system logs around the time the issue occurs? Should a VM hang again, please share the output of qm status <ID> --verbose while it's hanging.Crashed again shortly after booting, this time I was tailing the kernel, system and dmesg logs and all that was displayed was the logs below and the OS was frozen. could not click anywhere in the desktop:
Hi Fiona, I apprecaite the help. Attached are the requested outputs for you. To also add I store this VM on an NFS share, I have other VMs also on that share that maintain running when the 2x Ubuntu boxes freeze. my version of OS is Ubuntu 20.04.6 LTS.
Hmm, sounds like it might be a network issue. There is an error in the VM about CIFS and then about disk issues (and the virtual disk is stored on NFS). Can you also check the system journal of the host around the time the issue happened?
Thank you for that hint, I checked the logs and saw an OpenVPN crash right before. I am using a VPN to route my traffic differently and found an update for the provider so I updated and will monitor. My other Ubuntu VM does not have any VPN so if it crashes again I will gather the logs from it Thank you !!!
Thank you !!!
With the same network-related error messages? Maybe there is some kind of instability then or was it overloaded?Well that wasnt it, I just had it crash again without the VPN even running.
Good afternoon
We have two hosts that are united in a cluster.
1st host: 88 x Intel(R) Xeon(R) CPU E5-2696 v4
2nd host: 96 x AMD EPYC 7642
When migrating from one host to another, the virtual machines were rebooted, in the properties of the virtual machine I had to change the processor type to KVM64 - the problem with the migration disappeared.
Virtual machines migrated from one host to another occurred live.
Another point has arisen that some virtual machines on Ubuntu freeze after migration after a random time, and some freeze even without migration, you can’t do anything in the console, only hard reset
What could be the problem? Can anyone tell me?
We have two hosts that are united in a cluster.
1st host: 88 x Intel(R) Xeon(R) CPU E5-2696 v4
2nd host: 96 x AMD EPYC 7642
When migrating from one host to another, the virtual machines were rebooted, in the properties of the virtual machine I had to change the processor type to KVM64 - the problem with the migration disappeared.
Virtual machines migrated from one host to another occurred live.
Another point has arisen that some virtual machines on Ubuntu freeze after migration after a random time, and some freeze even without migration, you can’t do anything in the console, only hard reset
What could be the problem? Can anyone tell me?