Hi!
I checked on the last 3 Proxmox servers in which I have access and they are two of the Intel Silver 4208 and instead the third is an E-2236, all three servers have the problem only on Windows 2022 servers, no problems with other VMs, I attach screen shots of the 3 CPUs
have a nice day!
Hi,
Unfortunately yesterday on a new proxmox VE 7.2.4 with only one VM a new Windows server 2022 same problem ... crash of the VM found turned off for no reason, the server is a new Dell T340 with Perc 330 controller .... now I install the old kernel and I pray it won't happen again as they are...
Tonight another proxmox VE server updated two days ago, with two VMs Windows server 2022 gave problems on a machine that shut down at 01:43 AM .. now I proceed to go back to the previous kernel (proxmox-boot-tool kernel pin 5.13.19-6-pve) that with the other three proxmox VE servers that I...
a few more days have passed, and yesterday this update to the pve-kernel- 5.15.35-5 Kernel came out ... has the problem been solved with this update? Thank you
Sorry, a few days have passed now ... we are waiting for an official fix, can you tell us something please? it seems to me really serious that for a problem like this you have to wait so long for a fixl, what problems are there? why don't you tell us anything? thank you
Sorry, I ask someone from the "Staff Member" to have an official voice from them on how and when an official fix will be released for this, I would say, big problem with VM windows 2022, which makes them practically unusable on Proxmox VE with the new kernel still available in Proxmox...
I also had the same problem on multiple proxmox VE servers of various customers with windows 2022 that turned off every night with the error indicated in the previous posts, at the moment I solved it using the old Kernel (5.13.19-6-pve) and everything started working again.
So I wonder when an...
Ok, my request stems from the need to give to my client access only VM (PVEVMAdmin and works) then the storage (PVEDatastoreAdmin and it works), then this user as well as to manage the VM Backup and sun without altering the configuration must PVE you can always switch off your PVE and of course...
i don't understand.. i whant only that the user "pippo" can start, stop, reset, shutdown the only one PVE server.
ok i have deleted my other post... sorry
ok, but then how can I do to give the user "pippo" the permission only for start, restart, stop etc.. of my only one PVE?
i have try to use only "/" for the path but the same result...
how i do to use the "Sys.PowerMgmt Sys.Console" for this only permission of "pippo" ? ths
Hi to All,
i am this problem, i have crated the additional Role:
pveum roleadd Sys_Power-only -privs "Sys.PowerMgmt Sys.Console"
and i have add a permissions to the user "pippo" (is a PVE user autentication) for only start, stop, reset, shutdown the node, i have only one node and the name of...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.