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,

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

@Niall-Con Thank you! I'll take a look to that and will ping you to test on real hardware. Just need to find time (in the middle of storm right now), so it'll take one or two weeks most probably.

Yeah I remember it wasn't that easy

@kagbasi-ngc said in VM Console Screen Suddenly Inaccessible: Hmm, interesting observation about potentially this being a failed migration issue. I can confirm that none of my users in the lab are migrating any VMs or this particular one, for that matter. However, I do have the Load Balancer plugin running and it could be the source of a migration that could've failed. How can I confirm this in the logs? I mean, what should I be looking for? While trying to find logs, you can try to find the VM in question and see if it is using local storage rather than shared.

Don't worry, glad you asked to avoid having bigger problems later edit: there's a Python SDK for XAPI if you need.

@flakpyro From my experience, VM with UEFI boots faster than BIOS. For some OS versions UEFI runs faster IF there are no Xen drivers. But for most installs it does not matter much, except for Debian... which has given me problems with pool/migration/reboot with the UEFI installs on XCP (there's a workaround). So, I would vote for UEFI as the default for all OS/VMs that support it correctly since most are moving to that anyway (including XCP hosts).

@DustinB Go to the VM Advance Tab and change the two settings [image: 1748393969926-6e4b44f0-54cc-401d-8c12-42b067ca9750-image.png] [image: 1748393980963-42474d00-96fe-430d-8f5f-49dfb5cb38fb-image.png]

@amosgiture xcp-ng 8.2 and 8.2.1 is working without any issue. Have you checked the logs? it is recognized as xenserver 8.2.1 [image: 1747995496573-91f8952f-3e5e-4ed2-9990-2dc7ffc8a8a9-image.png]

Adding @stormi

@dinhngtu Thanks for your help. I solved to install XS Tools uninstalling old XS version 9.0, running XenClean and installing version 9.4. Also Disk stats now are correct. Now I get these good performances: [image: 1747727185969-a6beabc3-793e-41d7-9f03-4689db372275-immagine.png] [image: 1747727202526-20d58e2a-e9f9-4d7b-ba44-844dca2008fa-immagine.png]

@AshleyDe In the last few days, I've had these same issues with a few Server2025 virtual machines (I assume are close ish to Win11 24h2).

Great news Closing this as fixed. Thanks everyone for your feedback!

@plaidypus You can configure the disk within the guest OS to match whatever formatting you want. I would suspect the performance gains would be included as well, but you'd have to test and verify.

@sborrill And for completeness, try pvshim (a.k.a. pv-in-pvh) using xl: Download https://ftp.netbsd.org/pub/NetBSD/NetBSD-10.1/amd64/binary/kernel/netbsd-INSTALL_XEN3_DOMU.gz Create /root/nbpv containing: name = "nbpv" type="pvh" pvshim=1 pvshim_cmdline="pv-shim console=xen pv-linear-pt=true" kernel = "/root/netbsd-INSTALL_XEN3_DOMU.gz" memory = 1024 Boot VM successfully with xl create -c nbpv So pv-in-pvh does work (does require pv-linear-pt=true on shim command line though).

This only affects UEFI VMs running Ubuntu. A default Ubuntu installation includes the linux-modules-extra-<kernel-version>-generic package, which provides the bochs driver—required for proper VGA display in the Xen Orchestra console. If this package is removed, the console display becomes scrambled. Run the following command to install the missing package (replace <kernel-version> with the version in use by the OS): sudo apt install -y linux-modules-extra-<kernel-version>-generic source: https://docs.xcp-ng.org/vms/#distorted-display-console-on-ubuntu-uefi-vms

@tjkreidl Interesting that ASRock is also using the NUC name. ASUS also has the new NUC15. This new ASRock box uses the Ultra 7 255H which has 6P/8E/2LPE cores (no HT).

I'm having similar issue with A400 on xcp-ng8.3 Proprietary driver fails with following message when running nvidia-smi : NVRM: GPU 0000:00:05.0: RmInitAdapter failed! (0x24:0x72:1568) [ 44.619030] NVRM: GPU 0000:00:05.0: rm_init_adapter failed, device minor number 0 [ 45.095040] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint. [ 45.144703] nvidia-uvm: Loaded the UVM driver, major device number 241. system is actually loading the driver : [ 6.026970] xen: --> pirq=88 -> irq=36 (gsi=36) [ 6.027485] nvidia 0000:00:05.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [ 6.029010] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 550.144.03 Mon Dec 30 17:44:08 UTC 2024 [ 6.063945] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 550.144.03 Mon Dec 30 17:10:10 UTC 2024 [ 6.118261] [drm] [nvidia-drm] [GPU ID 0x00000005] Loading driver [ 6.118265] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:00:05.0 on minor 1 xl pci-assignable-list gives : 0000:43:00.0 0000:43:00.1 and gpu is assigned as passthrough,, but when listing test VM i have empty list of devices.. [23:06 epycrep ~]# xl pci-list Avideo-nvidia [23:35 epycrep ~]# Not sure if i want to try more before switching gpu to something else. Any hint where to look for ? Server is gigabyte g292-z20 wih epyc 7402p and single gpu for testing. IOMMU enabled.