Search results

  1. J

    Detect and throttle 100% CPU on VMs

    It is relatively frequent that some of my VMs goes to 100% cpu usage. This time a customer got infected by one of those spywares that turns the vm into a bitcoin miner zombie. The thing is that I have to manually detect the spike of usage in the proxmox web interface, and alert my customer...
  2. J

    Advice for file sharing between containers

    I have it working (mounting a remote filesystem via nfs), using 5.0-23 and in the .conf file: lxc.aa_profile: unconfined
  3. J

    How to start VM/CT from another node

    Hello, The other day my main node went off unexpectedly. As I store my images in the nas, I thought that I could start the VMs of that node in another, until I fixed it. But I could not find the command or way to do it. It seems that you need that the node which holds the VMs to be up and...
  4. J

    Weird bug in lxc containers

    Hello, Here using latest PVE 4.4-13. Today I had to do maintenance on my main node, so I moved my containers to another node: shutdown / migrate / start (I really miss years ago when we could do live migration using openvz... can't believe we are still stuck without it in lxc). All went ok...
  5. J

    Advice for file sharing between containers

    Yes, I understand that and already added nfs to the default profile. My question was if you had any concern about security, so that's why you didn't allow it by default.
  6. J

    Advice for file sharing between containers

    I am trying to figure out why it is not allowed by default in the lxc-default-with-mounting profile. Do you have any concerns about security?
  7. J

    Bugs related to reused VMIDs

    Hello, This is my first message in this forum and I would like to discuss an issue I find problematic on Proxmox. In brief: VMIDs should be auto-incremental, like in a database. Currently, when you remove a VM/CT, the ID becomes available again, and the next time you create a virtual machine...