pvesh

Hi, I tried to run a command via the new qemu command api endpoint via pvesh, but do not know how to format this correctly. I haven't found any hints or usage examples in the usual places. root@proxmox ~ > pvesh create /nodes/proxmox/qemu/109/agent/exec -command id ┌─────┬───────┐ │ key │...

Is there a way do add a new disk to a VM using pvesh ? I use pvesh create /nodes/$(hostname -s)/storage/local/content -filename vm-XXXX-disk-0 -format raw -size 10G -vmid XXXX to create a new disk, then I run pvesh create /nodes/$(hostname -s)/qemu ..., but how can I add a 2nd / 3rd / ... disk...

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...

Proxmox version: 5.2-8/fdf39912 I'm trying to find out, which node a vm is currently routed to, so I thought this command might be useful: pvesh get /cluster/ha/resources/vm:101 However, it only sends back the following error message: Use of uninitialized value in string eq at...

I am trying to automate the creation of QEMU images, but there isn't a lot of documentation that I can find about all the options that I can pass to the newest version of 'pvesh'. The man page is very lacking and even googling doesn't give many options.

Within the last month or so pvesh has changed from outputting json to "pretty" output by default. I'm trying to obtain json output again but cant figure out how; pvesh refers to format options: # pvesh USAGE: pvesh set <api_path> [OPTIONS] [FORMAT_OPTIONS] Call API PUT on <api_path>...

I notice that when I try to create an LXC container using the command line tool "pvesh", that after I create a new image from container it creates successfully but then the CLI sends the "pvesh" process to the background, and then i have to issue "fg" to bring the prompt back? pve:/> create...

I have written a python wrapper for pvesh that integrates with Salt-Stack (not Salt Cloud). Going forward, I need to establish a review process for new releases of Proxmox VE so that API changes can be identified before we apply updates. I've looked through the pve-docs distributed with Proxmox...

The command `pvesh get cluster/backup` returns a list of defined backups in the following format: 200 OK [ { "compress" : "lzo", "dow" : "mon,tue,wed,thu,fri,sat,sun", "enabled" : "", "id" : "7d3875b8db02bfcb258d1904f0c6745af64db4ea:1", "mailnotification" ...

If the description contains non-alphabetic characters, you can not create a snapshot on another server Run the command from the server p1 root@p1 # pvesh create /nodes/p1/qemu/125/snapshot -snapname "ss_test1" -description "automatically created" -vmstate false 200 OK root@p1 # pvesh create...