Unfortunately, XO does not currently provide a way to select disks across multiple VMs to migrate them.
It may be possible in the next major release scheduled for September, but not today.
If you have some knowledge of JavaScript, you should be able to it yourself by using xo-lib or xo-cli.
If you are a paying customer, please open a support ticket and we should be able to help you with that.
Hi,
This happens for very old jobs (which contains : in their id) which have been migrated.
The easy fix is simply to manually create a new job and delete the old one.
Hello Frank,
With Backup NG you can configure multiple types of backup and multiple targets in a single job, which results in a single snapshot if possible 
@honold Indeed, we should probably try to upgrade noVNC in XO, but that may not be easy, I fear the lib (and its packaging) has changed quite a lot since 0.6.1.
Anyway, when you see a bug, the best approach is to create an issue on the bug tracker
Yes, I'm a bit late 
Expect it in the next couple of days!
Answered directly, but I'm writing this down here if someone else needs it:
xo-cli --list-objects --\$VBDs id=<VM id>
# then, for each VBD
xo-cli --list-objects --VDI id=<VBD id>
@noelweston for non-string values you need to use JSON syntax:
xo-cli job.runSequence idSequence='json:["80a02c7c-3386-424d-b346-71d141c9cbd9"]'
@rubenc The fix as been released today
@Danp, @DustinB3403 Thanks for your feedback, we'll change the default values for hours & minutes, see https://github.com/vatesfr/xo-web/issues/1295