XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 21
    • Groups 0
    P Offline
    1. Home
    2. Pyroteq
    3. Topics

    Topics

    • P

      PCI device doesn't show in XO or xe pci-list

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      28
      1 Votes
      28 Posts
      9k Views
      P
      @andriy.sultanov I finally got around to fixing my capture card and I gotta say, it's a real pain to be using both methods and doesn't feel "correct" especially when there are warnings about possibly losing dom0 configurations after updates and the knowledge base saying that the old hide PCI from dom0 method is now considered obsolete. Perhaps the best solution would just be to provide users with a CLI command that would add that particular device to the xl pci-assignable-list if it doesn't fall into classes 01XX, 02XX or 03XX. Because I had added my GPU to my VM using the webUI, but then I also wanted to add the capture card through the console, but it appears that in the end you basically need to undo what's been done in the webUI and do it all through the console, otherwise you'd add the capture card manually with command line and then that would remove the GPUs... So I think some sort of manual override is necessary, even if it's a CLI option and then once that's done we could go into the webUI to enable it once the device has been marked as safe to passthrough.
    • P

      Issues getting serial to work

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      3
      0 Votes
      3 Posts
      1k Views
      D
      I don't think you need the --unit declaration. Try serial --port=pci,0b:00.0 perhaps?
    • P

      Easy way to find a failed task?

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      2
      0 Votes
      2 Posts
      868 Views
      D
      @Pyroteq said in Easy way to find a failed task?: It seems as soon as you refresh the page everything disappears. The Tasks page only shows logs while you're viewing it. Afterwards I think they get recorded to the Logs, but if your system fell asleep XO wouldn't know what happened. Besides the connection getting dropped and I don't know if that would get recorded.
    • P

      Mellanox ConnectX-3 - Card not working

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      12
      0 Votes
      12 Posts
      8k Views
      olivierlambertO
      That's weird, never heard about this option to be needed to make it work, does it ring a bell @fohdeesha ?
    • P

      After 2 days I FINALLY got GPU passthrough to work... On an ancient card...

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      1
      0 Votes
      1 Posts
      1k Views
      No one has replied
    • P

      Intel GVT-g (vGPU support for Intel iGPU's) - How do I enable this?

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      3
      0 Votes
      3 Posts
      5k Views
      P
      @olivierlambert Unfortunately they don't offer a guide, just a mention of it working. https://docs.citrix.com/en-us/citrix-hypervisor/graphics/hv-graphics-config.html Citrix Hypervisor supports Intel’s virtual GPU (GVT-g), a graphics acceleration solution that requires no additional hardware. It uses the Intel Iris Pro feature embedded in certain Intel processors, and a standard Intel GPU driver installed within the VM. However, they don't actually offer a guide on HOW to set this up besides offering some tips on how to setup BAR in the UEFI settings to change how many vGPU's it will support. I've enabled Above 4G Decoding, Re-size BAR Support and set the Aperture Size to 512MB but that doesn't seem to enable the vGPU options XCP-ng Center or XO. I'm assuming I need to enable it manually on the underlying OS before XCP-ng can see it. Note that the Intel GPU pass through is GVT-d NOT GVT-g. If you use GVT-d (AKA, just your regular PCIe pass through) obviously then I wouldn't be able to use the GPU for the the XCP-ng console on the machine itself. I'm comfortable on how to set that up but I really need the console available on the hypervisor for my use case. This video (in German) demonstrates setting it up in XCP-ng center. https://www.youtube.com/watch?v=FW9TPMrdTYc
    • P

      Nvidia Quadro P400 not working on Ubuntu server via GPU/PCIe passthrough

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      106
      1
      0 Votes
      106 Posts
      99k Views
      B
      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.