South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Upgraded to PVE 9 about a week ago. Smooth process.And all done. Both nodes are now on 9.0.3.
Not that I've noticed. Both HA and FreePBX have been running without reboot since I upgraded to PVE 9.0.3. No stability issues on my end.Anyone have random VM reboots of guests running on their Proxmox hosts?
There is nothing in the Proxmox VE logs so it looks like a VM failure. But I am certain it’s something in particular with my setup as it happens across both my nodes (identical machines, Optiplex Thin Client 3000’s), and moving the VM from one node to another yields no difference.
Nothing in the VM logs either, which is making troubleshooting harder than it should be.
so could it be config on PVE2? sleep states or something else?Moved everything to one node, and resource values look good. I have not overcommitted anything on the RAM or CPU side of things.
The poor little Celeron CPU is grafting HARD today
View attachment 1841667
It's happening on both nodes. Sorry if I am not making sense - I caought the flu so feeling a bit scatterbrained today.so could it be config on PVE2? sleep states or something else?
What CPU did you choose for the VM's?It's happening on both nodes. Sorry if I am not making sense - I caought the flu so feeling a bit scatterbrained today.
I had them all on one node, then the rebooting issue started, so I moved one VM to another node to see if it was related to the VM, or the node. But the rebooting happens on the other node too, so it's something that is following the VM.
OR, whatever it is is just common to my setup as both nodes are identical machines. So it could be a software bug as well, but I'm coming up empty-handed as the journaltcl is not giving me any pointers and from Proxmox's perspective, all is well.
Currently running Host type and I left the additional parameters as-is.What CPU did you choose for the VM's?
Changing to host type has resolved issues in past for me but clearly not your issue :-(Currently running Host type and I left the additional parameters as-is.
Each VM has 2x cores available.
Drat. I guess I could change it to another type to see if that changes anything. I've always left it as host as I reckon that is probably best for compatibility reasons.Changing to host type has resolved issues in past for me but clearly not your issue :-(
Do you have spare hardware you can install ProxMox on to move these 2 VM's to eliminate your current hosts?
My OMV is using this as CPU type - x86-64-v2-AES but my HA is also using HostDrat. I guess I could change it to another type to see if that changes anything. I've always left it as host as I reckon that is probably best for compatibility reasons.
No other hardware I'm afraid, unless I get get it running on a Pi 2B
Gonna give that a go as well and see what the outcome is - moving CPU type to x86-64-v2-AES-10111-802.11b-911-Y2K or whatever that type is called.My OMV is using this as CPU type - x86-64-v2-AES but my HA is also using Host
Overcommiting memory of the host? Does the VM itself die (timer in Prox reset)?Anyone have random VM reboots of guests running on their Proxmox hosts?
There is nothing in the Proxmox VE logs so it looks like a VM failure. But I am certain it’s something in particular with my setup as it happens across both my nodes (identical machines, Optiplex Thin Client 3000’s), and moving the VM from one node to another yields no difference.
Nothing in the VM logs either, which is making troubleshooting harder than it should be.
Nope, as far as proxmox is concerned the VM doesn't reboot, but everything inside the host is as if it does a hard reboot.Overcommiting memory of the host? Does the VM itself die (timer in Prox reset)?
Windows VM? All drivers installed if it is Windows?Nope, as far as proxmox is concerned the VM doesn't reboot, but everything inside the host is as if it does a hard reboot.
Both Linux and the proxmox agent tools have been loaded, too.Windows VM? All drivers installed if it is Windows?
No PCIe devices, but there is a USB device (HDD) passed through to the Openmediavault VM via the USB ID
View attachment 1842051
Yeah, you know it's bad if even ChatGPT gives up on youMine is setup the same as well but it’s been running fine. Shuu this is a tough one