REST API: Attaching an existing .vhd to a stopped VM

Danp

You attach a VDI to a VM by creating a VBD. Take a look at the POST /vbds endpoint.

Bytevenidos

@Danp Thanks! Also, I converted my VM to a template and it had the .iso in it prior to doing that but then when i spin it up from the REST API the .iso is gone?

Bytevenidos

@Danp They're all GET methods no way to mount anything.

Danp

@Bytevenidos Are you up-to-date?

Bytevenidos

Updated now!

@Danp

Bytevenidos

@Danp How about the CD-ROM with the .iso? Can i mount that on the VM using these also ?

Danp

@Bytevenidos I don't see an endpoint in the REST API for mounting an ISO. However, you should be able to mount the ISO during the VM creation. I will ask around about using the REST API to mount and eject ISOs.

Bytevenidos

@danp The POST /vbds endpoint allows configuring both "RW" or "RO" and a bootable Boolean.

If I need to mount an OS installation ISO and a separate provisioning VDI to the same VM, I assume I must execute two distinct POST /vbds requests:

For the CD-ROM (ISO): Set "mode": "RO" and "bootable": true.
For the provisioning VDI: Set "mode": "RW" and "bootable": false.

Would this work in mounting my OS .iso to my VM in the CD-ROM and also mount the VDI to the vm so it will read it on first boot?

{
  "VM": "VM-UUID", 
  "VDI": "VDI-UUID", 
  "bootable": false,
  "mode": "RW" 
}

Danp

@Bytevenidos You can try that, but it most likely won't work.

I've confirmed with the dev team that the end point to mount an ISO doesn't currently exist for the REST API. However, it does exist in the older JSON-RPC API, which you can access using xo-cli --

vm.insertCd id=<string> cd_id=<string> [force=<boolean>]

Bytevenidos

@Danp alright, thanks. I'll give that a try.