access rights for directory holding vms

[Elleni]

Wir created a separate directory in the userhome named myvms where we want the useraccount to be able to create vms under his responsability, whereas the standard directory contains vms the user is allowed to use but not modify.

Now I realized that despite the myvms is in a subfolder in /home/user/ when the user logged in in proxmox creates a new vm in this directory the access rights of the subfolder images containing the disk is owned by root user. Is there a way to configure the system that way that the vms are created are owned by the corresponding user?

As a workaround I see the possibility to create a cronjob with chown -R username:users /home/username/myvms but thought, I should ask here wether there is a more elegant solution.

 

[bbgeek17]

I'm skeptical about the feasibility of this approach. From Proxmox VE's perspective, VMs reside within defined Storage Pools, and distributing those across users’ home directories isn’t a healthy or sustainable model for PVE.

It sounds like you're aiming to implement a self-contained, cloud-like management experience. In that case, I’d suggest exploring the built-in PVE Pools and Permissions feature set. Alternatively, you could look into a third-party manager like MultiPortal or similar projects.

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Elleni]

What I want to achieve is a replacement of windows 11 laptop with vmware workstation. With the additional requirement that one vm the user shall not be able to manipulate. So we setup pve on top of a gui / debian install. That vm is sitting in a directory which is owned by root and by permissions and roles within pve I managed to restrict the users rights.

On the other hand he shall be able to selfcreate vms where he is allowed more thus I added the second directory myvms in users home and it works well besides that pve writes files with ownership root instead of the underlying access rights / ownership. Ex. the user has some vmware or other vm disks he wants to convert to qcow2 to then use them in pve. Now in myvms he needs to be able to create a vm and then replace the disk with the converted one, and as the user has no sudo - he needs to do this in a folder he is able to write in.

However - I will help myself with the cronjob then which changes the ownership back to the users.

We also have normal / standard pve nodes setup to replace our esxi servers. where high availability is needed even with a small cluster, this all works quite well.