CT stress command kills all access to server - why?


New Member
Sep 26, 2023
Hi everyone,
at the beginning I will point out that with proxmox I am just starting my adventure.
My question is about solving a problem when on a new CT - Ubuntu 22.04, I fire up the following command:
stress -m 512 -c 1 -t 60
Of course, I invoke it on purpose.
I'm learning how to manage proxmox server, stressing CT systems.
Well, and I came across this case.
This command completely kills my access as root to any terminal on the server.
Whether directly in ssh or in the GUI - it doesn't matter.
While cpu and ram usage on the root instance is still available, I still can't invoke any command - whether to kill the aforementioned stress command or call htop in the terminal.
Can anyone advise me why this is happening - why by firing stress on CT it affects the whole server even though I still have resources in main memory and cpu?

This is a problem in the range of a hypothetical scenario when some user on the host fires such a command at me.



The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!