This message shouldn't appear if the license is properly activated. Since you have an active XOA trial, you should open an official ticket through the support portal and we can take a look at this for you.

Still, I remember we had a dedicated CLI tool to test it

@bleader said in Created a new bond interface and lost management connectivity to hosts: The original problem could be a known issue when creating bond including the management interface that we have to investigate. Although the emergency network reset should have fixed that, so maybe it is a mix of the bond creation issue and MTU issue. In the reinstalled pool, did you create the bonds already? If so I would think changing the MTU should be fine, especially as it worked on other PIF, but with MTU issue it is often quite sneaky, so I would not make any promises either. Yes I have recreated them, but I am not game enough yet to change the management interfaces to MTU 9000, though I have done on bridge interfaces for VMs, because I was losing ssh sessions, and this solved the issue. Also, the bonded storage interface is MTU 9000 no problem.

@ph7 Thanks for the tip! Appreciate it.

@olivierlambert we are thinking about implementing a relationnal DB in the future. Maybe it could offer to stock snapshots as "archived"... I don't know for now. I understand that it could be risky to delete old snapshots, and maybe the responsability of setting the snaspshots retention can be an ACL subject... There are plenty of avenues of work on this topic, and more generally on the retention of information about objects, tasks, and other actions. It's a real in-depth topic.

@Tomcatter It's from Citrix: https://www.xenserver.com/downloads

@MathieuRA For this issue, fix-server-connect works for me. Thanks.

@Forza I don't know, I guess that's part of what I am trying to find out. How to get the metrics of the physical cpu usage. I thought that's what I would get with activating Netdata (Advanced Telemetry) from XenOrchestra.

Not a problem, something to be done correctly, and not implemented at all in the current XCP-ng API. In other words, it's not trivial You can create an issue in XO repo with all the details (and the screenshot), this at least needs some serious work to find what would be the best approach (and then sorted from our backlog)

@nathanael-h Alright...will take a look

@astrugatch At this point, I'd submit your ova to the Vates team as they requested to have them look inside it to verify you're exporting what is needed to be able to import into XO

@Andrew Gggrrr...you know what's funny about your response?...I was actually just in the Advanced tab and glossed right over that! hahaha Thanks Andrew

So it looks like it was a browser cache problem, solved by deleting it.

@TeddyAstie Thanks for confirming it's not supported, that saves me some head scratching! I'd based the assumption of it working post boot on the stats for memory usage being low and free -m showing < 48 GiB but guess I just misunderstood. Do you know if this is a fixed limitation or is it a feature that can be added in the future?

@AlexQuorum Nice to hear it In the meantime I've made a bugfix which will soon be available so you can edit the monitors instead of recreating them.

@gduperrey Ok, thank you. Appreciate the explanation.

@blackliner Honestly I never had this use case, but I would imagine terraform has a feature for this. I'll look into it, it's got me curious

Hi, Thanks for your report. Ideally, move XOA VM on another SR than the one doing the maintenance mode. Alternatively, you can do it manually with the CLI or XO Lite. You raised a valid question: XOA should have detected it was itself on the target SR and prevent it. However, even if it sounds simple, it might not be trivial. Anyway, I'm adding @lsouai-vates in the loop so we can improve this in the future

That's a security problem, due to Spectre/Meltdown, it's very dangerous to run a VM that could have more vCPUs than pCPUs on a host.