@Pilow Agreed however as our xcp-ng hosts are in the cloud with OVH Cloud we cannot use a physical appliance. We are currently setting up a dedicated OVH server for pfSense.

@Andrew What a day... Have two hosts and needed a RAM upg so scheduled these with OVH, one for 4pm and the other for 8pm. Plan was to migrate the VMs off the host being upgraded to maintain uptime. Got an email from OVH stating that due to parts availability the upg will not proceed and then they downed both hosts at 8pm to upg at the same time and that caused havoc today.

@McHenry said in pfSense Guest Tools: I have been using pfSense with xcp-ng for a while now without installing the guest tools. Due to some networking complications I have decided to install the guest tools to eliminate this as the cause. Q1) Are the guest tools required on pfSense and what do they do? Actually no, their main functionnality is to provide some data (memory usage, IPs) to XCP-ng to report them upward, AFAICT, it doesn't impact behavior in a significant way. It's actually not "PV drivers". Q2) Are these tools being maintained? This version of the guest agent is very limited and ancient (I don't exactly what it does, but not much IIRC). We're working on a new guest agent in Rust, which actually works pretty well on Linux, Windows (actually used in latest Windows drivers) and FreeBSD (NetBSD is also possible, but current code lacks some platform-specific bits). But we still need to sort-out some issues (some technical and some others non-technical) before making it broadly available / making it packaged.

@olivierlambert Host started and issue resolved.

The problem with those providers is, that the additional IP is usually L3 routed to the physical hosts IP. A better solution would be to get a /29 subnet or similar, where the gateway is handled by the provider and then configure that subnet on a specific VLAN which is available on all hosts where you want the VM's to be able to run. More work for the provider, since they have to setup the gateway IP within the /29 subnet on their router and then configure the VLAN on the switchports towards your hosts, but its the best way to make the VM's agile.

Good catch Dan and good decision @McHenry Even if you don't run VM, dom0 is used for VM transfer/backup/replication, so having 4GiB or RAM is a lot better in your case

See https://docs.xen-orchestra.com/load_balancing

@McHenry like @olivierlambert said, keep in mind that a VM with 16 CPUs will be less available than a VM with 4 vCPUs, because it's easier to have 4 vCPUs ready to work than 16 simultaneously beware of this graph, it only graph the first 16 vCPU, but you can have more working ! the visual widget is failing you. think of topology too : if you have two sockets, you can have a topology of 2 sockets with 4 cores for a 8 vCPU VM. If you have only one socket, try to keep the topology to "1 socket xx cores" for your VMs, performance wise.

@olivierlambert Here's the new model. We've tried a few combinations and I think with TrueNAS shared storage this will now work well. [image: 1759787234216-f78178c0-3330-4233-8f9b-debc3c61a3e9-image.png]

@flakpyro All this complexity makes me question the advantages of having all hosts in the same pool.

@Danp Thank you.

Question for @florent

It's better to have it to get handy options like IP addresses displayed and so on.

@dinhngtu Thank you so much. If you want me I'll be at the pub.

Hello, I am asking XO team.

That's great, those are companies with 100% backup dedicated products We cannot be everywhere and we have to prioritize on what most people expect. Recovery capabilities on a second site is like one of the most needed feature, that's why we did CR. From a technical stand point, when a VM is replicated, it's on another SR and XO doesn't have any direct access to the SR to mount it. IDK how VEEAM is doing, likely accessing the SR or similar (at least not on XCP-ng )

@McHenry xo-cli backupNg.getLogs --json limit='json:500' should work ( the command line parameter are considered as string )

@olivierlambert Hyper-V has the concept of Dynamic memory as documented below. This allows a startup mem value to be specified and something similar could be used for health checks as this is only needed for the network to connect then them VM gets killed. [image: 1745470452383-f746e366-9f3a-4d78-a6d7-219c8faac555-image.png]

Have you read the doc first? https://docs.xcp-ng.org/xostor/ This gives a nice overview on how it works

This is not a backup but a replication