@gduperrey Thank you for the reply. The use case is to centralize all of our reporting and monitoring for all of our devices. We have a number of XCP host, various servers, etc, that we are responsible for, and all of them besides our XCP nodes are being monitored for real-time analytics by Netdata. We are also using Zabbix for trending and long term usage but would like to be able to move the XCP nodes into our Netdata cloud versus being just on XOA/XCP. I also understand this would be overidden by updates and that you guys cant support it. I mainly wanted to see if it would "break" anything you already have in place. As a feature request, maybe have a way that you can report to a Netdata cloud instance. That would be nice.

Haha, glad it works now, that's what matters anyway

Do you have any SR using a VM? (like an ISO SR in a NFS share inside a VM). This is freezing NFS and makes host taking half an hour to restart. Logs should tell you why the RPU failed if it failed

@kagbasi-ngc Hi, thanks for your thoughts. I get on well with Linux myself - I’m using XO from source following the documentation, and actually, Ronivay’s script, as you mentioned, makes it all even handier. Still, I can’t help but think - your average home user, a total amateur, is just going to land on the XCP-ng host homepage and click "Deploy XOA". And then they’ve no backup, outside of the trial period. But sure, if XOA is aimed squarely at business and enterprise users with paid licences, fair enough that makes perfect sense. I just feel like backup isn’t really a purely business or enterprise feature, unlike, say, proxy instances or hyper-converged storage. It's something even home users would genuinely benefit from. But as it is mentioned above, that’s just how it’s set up - and like you said yourself, everyone’s got the chance to learn something new. And sure, in the age of AI chatbots, there’s really no excuse not to manage it

Release v2.1.0 This new version builds on the improvements to the Terraform Provider regarding the disk lifecycle of a VM (TF provider release). Full Release Note: https://github.com/vatesfr/pulumi-xenorchestra/releases/tag/v2.1.0

@blackliner said in Sdn controller and physical network: @nikade How do you "pair" the XCP-ng SDN with your routing setup? You cant/dont, you'll have to setup each private network on the vyos router and then have the vm private network routed through it manually. For example if you have private network 1 with subnet 192.168.1.0/24 you'd have to add this network to the vyos router and assign 192.168.1.1/24 on the router. Then set 192.168.1.1 as default gateway in your vm's which uses this network. Then you'll setup ospf or bgp on the vyos router manually with your upstream border/core-router or firewall. If the subnet is a private subnet you'll need to setup NAT as well somewhere before it reaches internet to NAT traffic from 192.168.1.0/24.

@kagbasi-ngc You are welcome.

@olivierlambert Thanks!

Those 5 mirror backups continued to fail over the weekend. The good news is that the normal delta backups succeeded over the weekend and didn't have any random failures I've been seeing.

I probably would have just bought a cheap mini PC and used Virtual Box for this, which is something I did do in the past for an old XP machine when the hardware started to fail. Grabbed a disk to vhd of it before the final failure and loaded it into Vbox. Might be able to do this in nested virtualization in XCP-ng.

@olivierlambert Thank you Olivier

Thank you so much for that hint. Yes, after restarting some xoa service this now works. So cool. You are great. Thank you.

@Danp said in Advanced VM settings Logs: Hi Dustin, Yes... these types of actions are recorded in the Audit log (Settings > Audit) if you have access to this feature and have enabled it. Dan Perfect, thanks!

@dinhngtu I went from Citrix 9.3.3 to 9.4.1, and generally they have remained manual when I've upgraded. All these VMs started out with 9.2.x so this is probably the fourth update to them. And all that said, I know the MAC address did not change, because I had a reservation for one of them and it was found properly before putting it back to manual. I think the XCP-ng side of things worked properly (no MAC change), but the driver side was the issue, and nothing you can fix since you don't write this driver. I probably should have used the cleaner first, but I went straight to the Citrix installer like I've done in the past. Took about an hour to get the 5 VMs updated, now I can move on to other things that have been lacking. I've mentioned it a few times, but this construction has me way behind for the summer, and only a few weeks of work time left before students come back.

@olivierlambert No, For once, i followed the installation step carefully ^^'

Hello, @nikade Yeah i think like this already, but i'm surprised by the result of the calcul. I should i have either: 3 nodes which can die, or "1", but i should not have the same number right ? in my case, i run the command in a 3 hosts cluster and it return me 3 as value. which disturb me. Best regards,

I see your point. Thank you!

Hi, Yes, by default, adding a new host to a pool, it will be lowered on CPU features to the common denominator, in other word, cutting that's not common between all pool members. So: If you add a more recent CPU to an existing pool, the CPU won't use new CPU features If you add an older host to a pool, it will lower down all features from existing CPUs

@ph7 worked, ty.