That is not the point Iβm trying to make.
The heart of the OS is going to be end of life December this year. You can probably plaster away but you need to keep track of everything for cveβs etc.. if you donβt want an auditor to trip on this. As they will because itβs end of life.
Posts made by xerxist
-
RE: XCP-ng 8.3 beta π
-
RE: XCP-ng 8.3 beta π
@xerxist said in XCP-ng 8.3 beta :
So which page do need to refer my auditor to for all the patching that is done once the kernel is EOL?
Just in case Iβve asked Lawerence on Youtube what his thoughts are on promoting EOL products to his clients
-
RE: XCP-ng 8.3 beta π
So which page do need to refer my auditor to for all the patching that is done once the kernel is EOL?
-
RE: XCP-ng 8.3 beta π
Not to be negative but in a professional environment auditors will trip on this. No one wants to explain to auditors that its plastered from upstream somewhere. Also itβs good for new hardware support. But good to hear work is progress.
-
RE: XCP-ng 8.3 beta π
Thanks for the explanation.
Will this be added like what there is now as an alternative kernel? -
RE: XCP-ng 8.3 beta π
Which kernel are you looking at since 4.19 will be EOL in 9 months?
-
RE: XCP-ng 8.3 beta π
It seems it would fix my iGPU passthrough issue with the NUC13
-
RE: XCP-ng 8.3 beta π
Any reason why xcp-ng is focussing on back porting kernel drivers and fixes to an old kernel instead of using a newer kernel and porting back in what is needed for xcp-ng?
-
RE: Intel iGPU passthough
Not in the VM itself.
I even went to kernel 6.6 and try it in there, all give the same issue.Something on the hypervisor side in the kernel I meant. This is 4.x something with allot of backports.
I'll probably just wait a wile before moving full XCP-NG.
But its a very nice system -
RE: Intel iGPU passthough
Seems you would need at least Kernel > 5.15 for this to work on the NUC 12-13.
Not sure what got implemented/fixed there but it would need to be back ported for this to work. -
RE: Intel iGPU passthough
NUC13 is still a no go with ASPM turned off.
Not sure if the kernel needs to recognize it as it doesn't give me the type like on the NUC11
But the NUC11 is confirmed working fine BIOS or UEFI
-
RE: Intel iGPU passthough
Strange it works on UEFI too now.
Only thing that changed is "ASPM off" in the BIOS of the NUC.
Need to try that too on the NUC 13. -
RE: Intel iGPU passthough
Got it working !!!!!
Changed the VM from UEFI to BIOS and it started working.
Still though why would it need it be BIOS instead of UEFI
Need to do some more testing as I also disabled something in the BIOS of the NUC11 for ASPM to so I'll bring up another VM with UEFI and test it again.
-
RE: Intel iGPU passthough
Giving this another try
I couldn't find those modules so this is probably not something in xcp-ng.
Is your vm running in EFI or BIOS?
-
RE: Intel iGPU passthough
It was to rule out any permission problems.
But it seems more on the iommu side of things where it goes wrong.
Iβve just tried the same on proxmox and it works right away. (Well not right away, like you need to do some grub adjustments and load modules) Not sure what I can do to fix it. Does the xcp ng kernel take these iommu grub settings too?GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt"
and these modules
vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd -
RE: Intel iGPU passthough
Tried docker/kubernetes Manjaro(just to switch to a later kernel)
Changed it to run as root.
Changed the permissions on the /dev/dri to 777.
Its just weird as it clearly sees the device.Actually got it to repond with FFMPEG
It gives an error and the GPU stays like that so it hangs, which is what happens to Plex too I guess.
-
RE: Intel iGPU passthough
Hello All,
Coming from ESXi 8 where I was doing this for a long time but for some reason I can't get it to work on XCP-NG 8.2.1 and 8.3 on my NUC11 and NUC13.
I can see the device in the VM when I do lspci, Plex also recognizes it.
The (hw) sign comes up but nothing happens after that.
Tried different OS's Ubuntu/Talos nothing seems to make it work then that its detected.Are there some kernel arguments I need to pass in Grub for this to make it work?
Really hate to switch to something else as I'm really like the setup and how everything works out the box, but this is a show stopper for my use case.Hope someone can give me a hint here.