maybe you want to spread the VM load on the maximum number of server, to get the most of your hardware? (previous example).

This way, the impact of your high load usage on one VM doesn't penalize everyone.īut it's not the only way to see this: there is multiple possibilities to 'optimize' your existing resource usage:

Host 1 has a slightly increased load, but host 2 can be fully used for the 'problematic' VM without disrupting service of other VMs. We are detecting it and now move others VM to the other host, like this: Host 1 still using 5% of its CPUs, but host 2 is now a 95%. Suddenly, one of your VM starts to have a very high CPU load ( in yellow): performance of other VMs on this same host could be impacted negatively ( in pink): Let's say both hosts are using only 5% of all their CPUs So the first objective is to adapt your VM placement in live (without service interruption), depending of the load. Maybe you already heard about VMWare DRS (Distributed Resource Scheduler): that's the same principle here, but for XCP-ng. If you attempt to perform PCI passthrough on a system which does not have VT-d/IOMMU enabled, you may encounter the following error when you start the target virtual machine: In addition, system BIOS updates may reset the feature to its default state, which may require you to re-enable it. Please note that this is not the same as VT-x/AMD-v virtualisation support, and so these options are often listed separately.Ĭonsult your system or motherboard manual for instructions on where to find the setting in your BIOS/UEFI. For Intel platforms the feature is typically referred to as VT-d (Intel Virtualization Technology for Directed I/O) on AMD platforms it is typically listed as IOMMU or AMD-Vi.

It can be enabled in the BIOS/UEFI of systems with CPUs and chipsets which support it. This should be more commonly enabled by default on enterprise hardware than on consumer hardware. In order to use PCI passthrough your host system must have VT-d/IOMMU functionality enabled.

How to install nvidia drivers on xenser