Export List of All VM Proxmox

[Nefariousparity]

It would be absolutely monumental fantastic if there were a way to export all VM's and Containers running in a ProxMox cluster. Export to CSV, or even print on screen in console a list of VMs. I think there was a console command in the past but I can't figure it out.

 

[Hannes Laimer]

Hey,

pvesh get /cluster/resources --type vm --output-format [text, json, json-pretty, yaml] should be what you're looking for.

 

[Nefariousparity]

Awesome, thank you! I did the "qm list option on each node.

 

[Sebastian Schubert]

Hi,

the text output does not show the (for me necessary) columns "name", but it's present in the json output. Any idea how the vm name can be shown in the human readable output?

 

[Hannes Laimer]

Hey,

you could use json-pretty or paste the json output there[1]. If you only have access to the command line maybe look at something like[2].

[1] http://json2table.com/
[2] https://github.com/kellyjonbrazil/jtbl

 

[Sebastian Schubert]

How about extending the integrated tool instaed of relying on 3rd party stuff?
Btw. json-pretty is also not human-readable/tie-compatible.

 

[Hannes Laimer]

You're right, I've sent a patch.

https://lists.proxmox.com/pipermail/pve-devel/2021-June/049065.html

 

[Sebastian Schubert]

/me plays "metallica hero of the day" for hannes

 

[omerk]

It would be nice if we could have got these exports in UI with CSV support

 

[Tmanok]

Technically you could get metrics through GRAPHITE or InfluxDB but I agree, updating spreadsheets containing current VM configurations and resource allocations in the GUI would be exceptional for automating our documentation work.

+1 for this feature. Thanks Hannes!


Tmanok

 

[ramon5544]

Assuming you put your json output in a file called vm.json; you can convert that to csv:

pvesh get /cluster/resources --type vm --output-format json > vm.json

then do something like this:

jq -r '.[] | [.vmid, .name, .status] | @csv' "vm.json" |tr -d '"'

 

[Tmanok]

Hi Ramon,

That's a good example, for me I'd like to make sure IP's are correctly configured and following IPAM in environments with multiple staff and many VMs. Moreover, I wish to document the current configuration of all the VMs in an easy to read and compare table, enabling easy CPU and Memory resource allocation calculations, etc. Maybe others have completely different ambitions, so a broad-spectrum output that anyone can narrow down from would look like:

pvesh get /cluster/resources --output-format json-pretty > clusterresources.json
jq -r '.[] | [.cpu, .content, .disk, .diskread, .diskwrite, .id, .maxcpu, .maxdisk, .maxmem, .mem, .name, .netin, .netout, .node, .plugintype, .pool, .sdn, .shared, .status, .tags, .template, .type, .uptime, .vmid] | @csv' "clusterresources.json" |tr -d '"' > clusterresources.csv

Mind you, depending on your CSV interpreter (e.g. LibreOffice) I noticed that the CSV file from the above export is not opened correctly due to the blank columns for some of the data. Anyway, this will provide other readers with the "complete" set of options, from which they can whittle down to their preference.

For IP addresses in particular, it is far too specific to extract from all VMs and unfortunately is specific to the interface and the parsing of the qemu-agent data:
pvesh get /nodes/pve2/qemu/120/agent/network-get-interfaces -o json | jq '.result[] | select(.name == "ens18") | .["ip-addresses"][] | select(.["ip-address-type"] == "ipv4") | .["ip-address"]'
Which will yield a single IP address.

Ideally, there should be a GUI feature that harmonizes the outputs of PVESH into a more massaged and simple to data dump file. It would save many hours comparing configurations, troubleshooting, resource planning, and maintaining large clusters with hundreds of VMs and their oddly specific networking. Firewall exports would also be helpful en-masse.

Thanks,


Tmanok

 

[yudidy67]

halo, can you share the specification with GigaByte details?