@bberndt that's why I mentioned uefi, wondering if legacy is part of the problem. I won't have time to fiddle with this for a while, broke a couple things today that I need to fix, and need to set up glpi for some testing.

Thanks @joncuddy We have to get back to Dell with a very large customer to change their mind. Catch 22 issue, but we have more and more (very) large customers, so this will change. @stormi we need to note that somewhere internally and monitor the opportunity to get back to Dell with a deal big enough to change their mind.

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.

@msupport Right! I'm sure it's a great product, the goal for this is to have no licenses, unlimited users, ported for several hypervisors. It's just a pet project I've wanted to do since I started in IT, and if other people besides me can use it, great! I know one of my employers may work on making it a polished project if the Omnissa renewal is too expensive. And if I can build it, why pay for it? I might not be a programmer by trade, but there's no reason I can't learn and ask around for help!

@ATSandrearicci Check the compatibility [image: 1744296853670-0877c1cb-2ac5-4afb-a993-a96fd66c7474-image.png] You must configure the license for the client on the license server: [image: 1744296959393-01b3b16d-8f06-4fe9-94ce-87b5c1cc1fcf-image.png] On the windows 11 client in the Nvidia control panel you have to specify the license server: [image: 1744297049623-8d883042-fc27-4678-8a05-e3c96b7a38a4-image.png] Check the authorization on the file: [image: 1744298130266-796ee95b-956e-4e9e-b178-cf60e92a0c97-image.png]

@CodeMercenary I had a simillar issue to you, check the time and the date on the host. If this might be any help to you: https://xcp-ng.org/forum/topic/10687/after-an-update-the-nic-s-has-disappeared-but-still-works-somehow/10?_=1743764792775

Ok, found a solution. Seems there is nothing I could do via cli or xo-ce to see the virtual GPUs, had to install xcp-ng center, specifically from: https://github.com/xcp-ng/xenadmin/files/13800584/XCP-NG-Center-2023-Release.zip Using the center, I was able to assign the GPU to the VM and everything worked well from then on. Now to figure out licensing....

@TeddyAstie Any idea how to debug this? I'd hoped that enabling VM console output with the following might help: xenstore-write /local/logconsole/@ /tmp/console.%d.log With the xl toolstack and pvshim, you see the shim xen kernel start on the VM serial console before handing over to the PV domU kernel. In XCP-ng, there is no output.

@dinhngtu Hi everyone, Thank you all so much for your help and suggestions. After several tests, I’ve decided to stop troubleshooting and stick with Windows 10 in BIOS mode. UEFI doesn’t work properly for me, whether with Windows 10 or 11, but everything runs fine in BIOS mode. I really appreciate the time and support from this great community!

@gduperrey I thought I had. I was replying to that thread and the forum software prompted me to click to reload. It continued to show the contents of the thread above as I clicked to post my reply, so if it opened a new thread, I count that as a bug in the forum, not user error

@Denson After enabling HA, the host has to be manually rebooted, which I think you're already aware of. OK, well, that leaves pretty much a network issue. Hmm. The statefile created OK on the shared SR within the pool? The "not found" error message doesn't give you much to go on, unfortunately.

@Andrew, @bvitnik and @DustinB In my tests, I did the following. I did this process twice and it worked. To simulate a hardware failure on the master node, I simply turned it off. If the master pool is down or unresponsive due to a hardware failure, follow these steps to restore operations: Use an SSH client to log in to a slave host in the pool. Run the following command on the slave host to promote it as the new pool master: xe pool-emergency-transition-to-master Confirm the change of the pool master and verify the hosts present in it: xe pool-list xe host-list Even if it is down, the old master node will appear in the listing. Remap the pool in XCP-ng or XO using the IP of the new master node. After resolving the hardware issues on the old master node, start it up. When it finishes booting, it will be recognized as a slave node. In testing, I did not need to run any other commands. However, if the node is not recognized, try typing on it after accessing it via SSH: xe pool-recover-slaves I didn't understand why it worked. It seemed like "magic"!

@bvitnik Thank you -- very useful information!

Confirmed, that works. Thanks!

@nim81 said in Support licensing structure update: but there's no way I can possibly justify the levels of increase being asked here. As Olivier has said, your comparing paying for XOA with no support, to XOA and XCP-ng supported in a package deal. I don't know that the Vates team has specifically cancelled the XOA only package, but that is a bit germane to the conversation. Just use XO from Source, or one of the scripts and move on with your day. If your business grows you can always sign up for support again.

got it @michael.manley . thanks . unchecked that , will monitor and let you know . thanks so much

A powershell SDK? Oh, you just made me a rather happy guy.