Works with .raw at the moment. If you disconnect it from the vm and migrate it to another SR its converter to vhd.

@flakpyro said in How to migrate XOA itself?: @DustinB Are the any downsides to having two XOA instances pointing at the same pool? Since the config itself is stored at the pool level im guessing theres no downside? IE: Priimary XOA running in core DC and secondary XOA running at your DR site. Is it just a matter of adding the pool on the secondary XOA and it downloads the existing config or did you need to do a full export / import? If you import your configuration, each XO instance will think they should be running the backups as far as I've noticed. If I have two instances running with the same configuration, I simply disable the backup jobs on one of them. The config file is just an XML that contains your existing instance. You can import it to any new XO instance and have the same exact configuration.

That would be easier if you open a ticket so we can use our remote access tunnel to take a look

Have you saved the view you wanted to have? I'm not entirely sure to get it, what is the URL you have in your browser?

Bit of a necro-post, but we're mid migration of storage/VM hosts/pools. I have a single win11 VM that's UEFI (not secure boot). It runs just fine on our old 8.1 server that we're migrating off of. If I provision a new UEFI VM on the new pool and point it at the shared storage VHD, it refuses to boot with the same "The emulator required to run this VM..." error OP posted. I've tried restarting the toolstack and "updating the Secure Boot certs" on the host server. Any guidance very much welcomed, I was unaware that this VM wasn't booting on the new pool (the VM is off a lot of the time), and we're a couple weeks from this project completing (and the old server being WEEEd).

There's an open issue about this on Github, just check on the forum

It's probably broken in that version of noVNC sadly This will change in XO 6/XO Lite

@ronivay You make a good Point. What I didn't know, that I do now, I wasn't "naming" my schedules. Once you do that, it replaces the Cron time. So I called my things like "Daily @ 4:30 - Diff" but obviously naming schemes are broad.

@heman Yes. The management interface on each host (Eth4) is in the same vlan as XOA's management interface. Storage vlans on each host (Bond0) is in the same storage vlan as the second interface on XOA (setup for backups) with no gateway.

@rkelley Home > Host > Network

You need to restart the service as root/sudoer, eg sudo systemctl restart xoa-updater. Note that you can have XOA support with our ticket system, even on XOA Free If you want someone at Vates dedicated to your issue, please create a ticket!

As I said, we can extend it, just ask us