Search results

  1. M

    LXC restart creates kworker CPU 100%

    I agree, after updating to latest version recently we've seen a recurrence of this problem ...
  2. M

    [SOLVED] No longer getting JSON response after update for pvesh get /cluster/resources --type vm

    That worked, thanks! Had to use "--output-format json-pretty" pvesh get /cluster/resources --output-format json-pretty --type vm
  3. M

    [SOLVED] No longer getting JSON response after update for pvesh get /cluster/resources --type vm

    We updated some of our servers last night to 5.2-9 and since then the "pvesh get /cluster/resources --type vm" command that used to return JSON now returns a text table with information. Since I use this in some code, is there any way to display/get it in JSON format as opposed to this table...
  4. M

    LXC restart creates kworker CPU 100%

    I can confirm we get the same issue ever since we upgraded to the new version of Proxmox. This is very annoying and renders a host almost useless with us unable to kill the kworker process. Instead of restarting the LXC we've tried shutting it down and then starting it up again, which appeared...

About

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!