@DevilDan Are you using the Load Balancer plugin to manage the load on your pool?

Hi,

This is explained in this KB article -- https://help.vates.tech/kb/en-us/30/21

Regards,

Dan

Check to see if the VM is running in PV mode -- https://xcp-ng.org/blog/2022/01/17/removing-support-for-32-bit-pv-guests/

What type of storage are you using? FYI, shared storage is only accessible by hosts within the same pool. You can't safely share the same SR with multiple pools.

From your description, it sounds like the warm migration was proceeding as expected. The VMs will crash if you live migrate them because of the difference in supported operations between the different CPUs.

Yes, it should work correctly if you use fields. Also, I think uuid need to be lower case.

There isn't an ID field. Change this to UUID and it should work as you intended.

@sixela I understand. I'm not an expert on HA functionality, but I suspect that the new pool master would need to be designated as a first step. That is why I am suggesting that you investigate why this didn't automatically occur.

@sixela There's likely more information in the logs that would explain why a new pool master wasn't designated.

Can you describe in more detail this dom0 crash? You should investigate in the logs for why HA didn't kick in and promote a new pool master.

Have you confirmed that HA is enabled on the pool's Advanced tab? Also, did one of the other hosts automatically take the role of pool master?

Hi @sixela

Is the VDI sitting on shared or local storage?

Dan

@DustinB No, but dev team has been notified so that they can investigate.

@ainsean See the bottom of https://help.vates.tech/kb/en-us/31/48 for the procedure to reset the database.

@irtaza9 AFAIK, that is how it is intended to function when using a cloud-init enabled template.

I think this is standard behavior for hub templates because they are cloud-init enabled. Does it allow you to change the size if you select a different option than "No config drive" under the Install Settings category?

Two things you could try --

• user filter set to (sAMAccountName={{name}})
• Remove the entry under Certificate Authorities

Can you show us the settings that you configured for this plugin?

@irtaza9 I'm not sure that I understand your question. If you select a template that isn't a good match for the OS being installed, then it is possible that the VM will under perform or I suppose it could crash. Is that what you are asking?

@irtaza9 You should try to select the template that is the best match for the ISO being used.