@Byte0 The json: makes the rest of the value interpreted as JSON, otherwise it is interpreted as a plain string. It is therefore required for all non-string values. Some method params (like memory for vm.set) accept both integers and strings, that's why it was working.

xe is a XAPI client, like XO is a XAPI client too. The issue with this, is if you have 1 pool it's OK. If you have many pools, it's a lot better to use XO API.

@BenjiReis The xapi is written in OCaml? That is pretty cool. I would love to learn OCaml one day. Anyways, doesn't seem intuitive to design it this way: [image: 1729609345601-334b8d7a-6f7e-4796-97c2-3c1fe4144fb6-screenshot-from-2024-10-22-08-02-03.png] Going to file an issue in that repo to see what happens. I suppose they would have to fix the OCaml code you linked as well.

Ok. You threw me a curve ball when you mentioned the "[XO Backup blah blah]" stuff. I think you are referring to the snapshots. If so, then yes they get transferred over when you migrate the VMs.

A badly formated VHD can indeed trigger this, nice catch!