@DwightHat No I did schedule a reboot of XO every morning and it seems it has worked because I "forgot" about it No idea if anyone have "fixed" anything

@hitechhillbilly no it doesn't, it just ensures the N-th vCPU of Dom0 only runs on N-th pCPU of the machine. Not sure about the practical impact of it, in the past it has been used for getting meaningful CPU temperatures from coretemp (with physical core matching virtual one), but that doesn't work anymore since Xen filters MSR accesses (including Dom0).

@MajorP93 Thanks for your feedback. I'll look into it over the christmas hollidays

@firereverie Sorry, these last few weeks was very-very busy. So I REALLY hope will do something on this before the december end and come back to you.

Hi, I can't tell it's the cause, but you should first use an officially supported client to manage it.

It's not meant to be used like that. If you are behind a NAT, the right approach is to have your XOA behind the NAT and inside the same network than the hosts. That's because hosts will always use and return their internal IPs to connect to some resources (stats, consoles etc.). XOA deals with that easily as being the "main control point" for all hosts behind your NAT (or a XO proxy if you prefer).

The roadmap depends a lot on the feedback we have on it More demand/popular, faster we'll implement stuff

Ok I've figured out root cause. My config override has only one option: ignoreVmSnapshotResources = true And I had to change it with adding [selfService] on a line below Also I found out that override config for XO5 interface needs to have absolute paths to xo-web and @XenOrchestra in it. With relative paths it didn't work.

Figured it out after some digging, appears it's related to Netbox having ipv4 translated into ipv6 for that field, so to use IPv4 you have to have :ffff:x.x.x.x/128 as your IP address (the x's being your octet). Once you do this it works without issue.

@isdpcman-0 said in Install mono on XCP-ng: Our RMM tools will run on CentOS but fail to install because they are looking for mono to be on the system. How can I install Mono on an XCP-ng host so we can install our monitoring/management tools? Reply I think it is advised to consider hosts as appliances and not install any external packages (repos are disabled for that purpose, that's probably your issue for installing anything) even in case of clusters of many hosts in a pool, you should deploy same packages on all hosts to expect compliancy between hosts... better use SNMP to monitor you hosts ? or standard installed packages ?

Hi Forza, Have you finished migrating the workloads? If you are still looking for an easy migration solution, you can try Vinchin Backup & Recovery. It will replace the driver during migration intelligently.

I hope someone will reply to my post here about how to check status on this but I believe I've resolved the main issue: I disabled and re-enabled the whole task itself yesterday and it ran this morning as scheduled.

October release fixed it

Hi! I'm not sure who to ping exactly for this question @pdonias or @Bastien-Nollet maybe?

@SethNY you could even enhance this VM_LIST = with TAGs on VM, so that you manage the selection directly in XOA

Adding @gregoire in the loop

@olivierlambert I'd like to see replicated vms in netbox, perhaps not syncing their IP address to avoid conflict DR VM as well

I haven't had too much difficulty hitting the esc key in time to get into the EFI config. Click the start VM button, quickly click away from the display area and click in the display area, then toggle the esc key until I see it take effect. I know I have a couple running at 1920x1080, but that's actually kind of a pain. I only did that to try and get a larger RDP window, RDP may be limited by the original "monitor" resolution, but this might also be fixed in later updates. This one VM has been up for a few years. (edit, yes this has been changed, VMs with a 4x3 monitor now RDP is whatever I have set).

@Greg_E said in Building XCP-ng from source code: @olivierlambert Ok, thanks. Yes I'm eagerly awaiting XCP-ng 9 for testing. Hi, check this thread: https://xcp-ng.org/forum/topic/11698/xcp-ng-9.0-demonstrator-early-preview More coming...