Hi,
If anyone could give me a fast advise on my toruble :
One node updated to lates kernel/version , most VPSes are CTs, but yesterday installed Windows on VM. During the night Windows VM managed to load the whole server to load:2000 , and froze the server . (Windows was assigned 50% of CPUs , and 30% of RAM .
After manual reboot i see i can start and stop mvirtual machines, however proxmox GUI interface became unaccessible - says "The connection has timed out"
I had tried
service pve-cluster restart && service pvedaemon restart && service pvestatd restart && service pveproxy restart
and
pve-firewall stop
but no luck .
COuld anywone advise me - how can i check if it runs via CLI and how i can posisbly fix this ?
Also secondary question qould be how Windows VM could freeze whole server ? (I have installed all virtio drivers from https://fedorapeople.org/groups/vir...o/virtio-win-0.1.141-1/virtio-win-0.1.141.iso )
Would apreciate any help, as this is live server
Thanks .
If anyone could give me a fast advise on my toruble :
One node updated to lates kernel/version , most VPSes are CTs, but yesterday installed Windows on VM. During the night Windows VM managed to load the whole server to load:2000 , and froze the server . (Windows was assigned 50% of CPUs , and 30% of RAM .
After manual reboot i see i can start and stop mvirtual machines, however proxmox GUI interface became unaccessible - says "The connection has timed out"
I had tried
service pve-cluster restart && service pvedaemon restart && service pvestatd restart && service pveproxy restart
and
pve-firewall stop
but no luck .
COuld anywone advise me - how can i check if it runs via CLI and how i can posisbly fix this ?
Also secondary question qould be how Windows VM could freeze whole server ? (I have installed all virtio drivers from https://fedorapeople.org/groups/vir...o/virtio-win-0.1.141-1/virtio-win-0.1.141.iso )
Would apreciate any help, as this is live server
Thanks .