@Bambos A timeout error means that the host did not reply in the expected delay, which, if I'm remembering correctly is 5 minutes.

I suspect a problem on your host but we will take a look further on your support ticket.

Permissions will come in XO 6 this year 🙂

Hi,

No, because XenCenter use XAPI LDAP configuration, which is removed in XCP-ng, it won't work. For user access with LDAP/SSO, you must use XO.

@spcmediaco

I restored a backup VM to the host that is currently working and that VM worked, now I'm trying to migrate a VM from the 'broken' host to the working host and see if that works. Maybe I need to format the 'broken' host and reinstall it.

ok, thanks. No local storage all shared iscsi storage

@olivierlambert

Dou! Thanks for clarifying the speed limit - I've adjust to 100MiB, which should use about 80% of my available bandwidth.

Resolving the VDIs' appears to have worked as backups going now.

I just have these long running tasks which have been going multiple days with no end in sight that I can't resolve. I suspect they may be related to why I can't migrate VM's between hosts now.

Cheers
Kent.

Screenshot 2025-01-09 at 7.59.46 AM.png

Yes, you can use JSON-RPC et REST APIs together for now 🙂

We will try to add support for CPU settings soon.

Also, expect things to accelerate in 2025 regarding the REST API.

@gudge25 ...forget about it... Mikrotik won't fix v6 and they have a proprietary OS, so you can't install normal stuff.

@HamiltonWDS Thanks for the report. As it works with wget let use it! I'll switch from curl to wget in doc. In the meantime some colleagues will investigate more.

Sure, happy to have a PR on our doc!

Thank you very much for the clear explanation @HamiltonWDS ! This will be really helpful so we find a solution for that. We might default to IPv4 for a lot higher latency, and in the future maybe having closer location mirrors. Let me discuss this internally and schedule an action for that.

(Thanks @nathanael-h , might even worth getting a part of this in our current doc with an example, adding @thomas-dkmt in the loop)

@DustinB
Yes

@thomas-dkmt said in "Block migraton" option on the VM´s Advanced tab:

@olivierlambert @DustinB Thanks! It's always helpful to have a native speaker's perspective.

Happy to help, worth noting that if a setting like this is enabled on a given VM, there should also be some sort of visual indication on the home screen of XO to annotate that these VMs won't move unless this is disabled.

The simple answer here is to use the Continuous Replication backup type. It'll copy the VM to another host on whatever schedule you set.

It couldn't be simpler.

@Danp

have now 🙂

@olivierlambert

A quick follow up for anyone performing warm migrations.

If you elect for the migrated VM to be powered on post migration, then the option to protect from accidental shutdown needs to be off to enable the source VM to be turned off when the migrated VM it turned on.

c09859e7-b32d-486a-90ed-e44061d68ead-image.png

If you like the thrill of adrenaline and elect for the source VM to be deleted post migration then the protect from accidental deletion would also need to be turned off. I am not that brave.

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

@DustinB

Thanks Dustin. This is exactly our goal setup.

Thinking further, as XO/XOA could be hosted on either host it would make sense to host this on the DR host.