@julien-f what do you think?

So it's the case in an IPv6 context I assume, right?

Add @nathanael-h to take a look

Food for thoughts @thomas-dkmt

So either we need to update pool_migrate to allow a migration network parameter, OR we need to be sure than migrate_send do NOT reset the CBT data if the storage do not change. @psafont Do you have a preference on which one we need to do upstream?

Hi!

We used it since a while internally (before switching to OIDC) but I think we did not use group sync. I wonder if @nathanael-h could take a look to spot anything obvious.

Great news

Adding @psafont in the loop because it seems we should use pool_migrate with a network migration and/or migrate_send not resetting the CBT.

I'm not aware of this problem, have you changed the mode (BIOS vs UEFI) after BIOS update? I think we already tested a BIOS update and it worked well. Let me ping @AtaxyaNetwork about this.

Hi,

Yes, you need a master available to get XO (or any client) to manage it. But without a master, the other pool members will continue to run their existing VMs. You can promote any other node as the master if you need to.

But in a DR case, I don't see the need to have those 2 hosts in the same pool. Having 2 different pools is better because whatever happen into one won't affect the other (which is what one wants in a DR scenario)

Check in the health view if you have VDI attached to the control domain.

Regarding the other question: the speed limit is in MiB/s: it's Bytes not Bits.

VDI in use is something else, it means the VDI is still mounted somewhere. It's very hard to tell you exactly where, maybe stuck attached to the Dom0.

For the other question, the limit should be per job total, regardless NBD or VHD.

@dinhngtu Does this message rings a bell to you?

    "error_info": [
      "INTERNAL_ERROR",
      "xenopsd internal error: Failure(\"Error from xenguesthelper: xenguest Invalid argument\")"
    ],
    "other_config": {
      "debug_info:cancel_points_seen": "26"
    },

It has been added to the backlog, thanks!

Disable or prevent are indeed a lot better.

Hi,

Which Debian version and which kernel + which xen tools are you using (and version too!). Thanks

Let me ask the XO team about it

Might worth asking Mikrotik to use our latest Rust agent

Hi!

1. The first video shows an unsupported client (XCP-ng center) and it's 2y old, and not from any official YT channel. So it's not a good guide to do this.
2. You imported it successfully in Xen Orchestra, so the VM should work However, there's no agent install, because I think Mikrotik doesn't bring those tools by default. You should ask Mikrotik community about this. You can build or try the Rust binary that will be the tools in here: https://gitlab.com/xen-project/xen-guest-agent

Pinging @thomas-dkmt