How can I browse storage from the Proxmox VE GUI?

[senseivita]

I'm trying to browse my storage from Proxmox VE but nothing shows. First I added my install image NFS share, it added it successfully, read its capacity and free space, appearing it went fine, but there was nothing in it. Nor entries were displayed when I tried to create a VM to test if it was indeed pulling data from the server.

I thought it could be because the mount wasn't recursive, and install images, or ISOs, are further segregated by OS. I created new mounts for Linux and the BSDs and tried again, but both browsing the datastores and when attempting to create VMs fail to populate results/lists.

Browsing for VMs wasn't any better. Of course I wasn't expecting anything at all since my VMs are on vSphere. That said, not even the virtual disks appeared, and I know they are compatible. I've converted (via export-import, and straight just changing the vdisk format with qemu-img) before from vSphere to KVM in Unraid and RHEL, probably Debian too, I don't remember; I'm aware there's an importer straight from vSphere but what I really need/want is to learn how to browse exisiting data in datastores/storage from the GUI.

I'm root BTW. I don't know if that's standard because I converted a Debian 12 (fresh) installation, but I'm pretty sure I should not have permissions issues as root.



Is it possible at all? or will I need to do the qm … commands every time? I would imagine mounts are automatically scanned upon their addition, on second thought scratch that because what I want to do is browse the current filesystem, not a version of it in a database.

I'll leave it there because I don't think I'm making any sense. Hopefully I am. I appreciate your guidance though.

 

[sterzy]

Is it possible at all? or will I need to do the qm … commands every time? I would imagine mounts are automatically scanned upon their addition, on second thought scratch that because what I want to do is browse the current filesystem, not a version of it in a database.

So Proxmox VE expects a certain folder structure and will display the files in those folders [1]. Browsing the file system as such, as you may be used to from VMWare isn't really how it is done in PVE most of the time. However, you can configure the content-dirs parameter to specify certain folders that should be used for certain types of content [2].

[1]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#storage_directory
[2]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#storage_nfs

 

[senseivita]

Proxmox VE expects a certain folder structure

:O

That's all the answer I needed. Thanks! I know now to change my approach.

I guess I never cared to pay attention past the chapter of storage and storage types on that same document, because though most of the examples of storage types are self-explanatory, some aren't or are ambiguous and because most if not all Proxmox terminology is ultra generic (e.g: datastore vs storage) it was tough to find more about it. I thought it would be trivial to circle back to it but I guess I was wrong.

But touching the blueish/invisible flame of a jet lighter, involuntary manslaughter… mistakes are tools for learning. Just kidding.

Thanks again!

 

[Envy8181]

Override Proxmox creating subdirectories in the share by modifying /etc/pve/storage.cfg by adding this line. This example is for the ISO share forcing it to use root of that share rather than creating /template/iso.
content-dirs iso=./