I installed all these updates for 8.0 and rebooted the host.

The reboot was extraordinary long. The time from shutting ssh session to getting ping packets back again was about 8 minutes. I don't know what it was doing during all this time as I rebooted remotely.

So I rebooted once more to see whether the boot time would be so long again.
This time it was only 1 minutes 46 seconds.

The VMs seem to run OK so far, but it's just a test host with two VMs doing almost nothing, so I don't know for sure :-).

jcpt928 said in XCP-ng and NVIDIA GPUs:

I have taken the approach of ensuring my VMs, my network, and my edge is secure - if someone can't get into something and run something that takes advantage of the bug in the first place, that's all that really matters.

I seem to remember this question asked at this forum, but can't find it...

Do you use browsers?

woopla I'm not sure if this will work in your setup, but I've thought I'll share the solution which worked for me as I tried hard to get rid of bloody framebuffer (which was making the console in XCP-ng Center and in XOA almost unreadable due to tiny or blurred font).

After many hours of googling and trying various settings in /etc/default/grub (which theoretically should work, but didn't) I found unix.stackexchange.com/questions/346090/disable-framebuffer-in-qemu-guests.

It advised:

" disable the framebuffer via a bochs_drm module parameter - i.e. via setting it on the guest kernel command line: bochs_drm.fbdev=off "

Precisely, I put into /etc/default/grub the following line:

GRUB_CMDLINE_LINUX_DEFAULT="systemd.show_status=1 bochs_drm.fbdev=off"

edit: I forgot to mention: the above line is for a VM system, not for XCP-ng host.

(The systemd entry is unrelated to fb issue, but I'm quoting it here as a additional tip - I need it to at least partially work around systemd fascist plague).

I wonder: will this bochs tip help you?

You're welcome!
I'm happy I could help a little. I'm grateful for XCP-ng!