Subcategories

• Compute

  All Xen related stuff
  624 Topics

  6k Posts

  F

  Got an interesting one: i9-9900 (Coffee Lake) system w/ i915 graphics. This is a signage type mini PC with an HDMI and two Display Port outputs. It has space for NVMe and SSD (SATA) drives. Currently have a 500GB NVMe installed on which I installed xcp-ng 8.3/XOA, created an SR on same and put a Linux Mint 22 VM on. I need to get display outputs from the PC itself as the end user won't understand Xen Orchestra or the rest of the under-the-hood stuff I'm doing with the system. So...isolated the Intel graphics adapter from Dom0, set igd_passthrough=true (via command line on the XOA instance) and added a PCI Device via the VM's Advanced settings. When xcp-ng starts up the HDMI-connected monitor goes blank as it should. I start the Linux VM via XOA on another system, can get a Login screen and then a desktop. Display Settings only shows the Console (bochs-drm) driven screen. inxi -G when run from a terminal on the Console screen shows both bochs-drm and i915 drivers loaded, and only the one screen listed. If I ssh into the system and run inxi -G in the terminal session I see all three physically connected screens listed but no video is displayed on any of them. Doesn't matter if I use Wayland or X11 - results are same; detected monitors are same. Xorg.0.log also shows EDID captures for the two Display Port monitors so I know they're being queried successfully. Thoughts, suggestions on where to go from here?
• XO Lite

  The integrated web UI to manage XCP-ng
  29 Topics

  367 Posts

  O

  The same as @john.c and also XO Lite tends to be less a priority because less critical than the full fledged XO (the priority is to replace entirely XO 5 in the next releases). Why you would need XO Lite outside basic actions? It's mostly meant to bootstrap XO itself and do basic operations (which is already the case, at least with many basic features already). Initially, the goal hasn't moved: replacing XenCenter. We are moving in that direction, but again, I think it's more important to get XO 6 finished first. I'm curious to understand more the use case of XO Lite in your context @unreal-shizzle ?
• Migrate to XCP-ng

  Section dedicated to migrations from VMWare, HyperV, Proxmox etc. to XCP-ng
  128 Topics

  1k Posts

  A

  If i recall from my migration I belive thats all there is to it. I know the docs mention about doing a test migration but mine just migrated and it just worked as you stated after making the needed adjustments. Let other chime in but i think you are good to go. And you could delete the snapshot from the vm.
• Hardware

  Hardware related section
  174 Topics

  2k Posts

  P

  @seanmcg182 's post might be the answer to the original question, two years late. Your lspci -s 0000:05:00.0 -v at post 8 shows (rev ff) and !!! Unknown header type 7f, which is the same pair he had, and in his case it came from bifurcating the wrong PCIe port in the BIOS rather than from anything XCP-ng was doing. He says the unknown header is what then produced the device or resource busy error on VM start, which is the error you opened with. I don't know whether your board exposes bifurcation the way his X10DRH-CT does, so it might not transfer at all. @kuznetcoff777 if that machine is still around, it'd be worth a look either way.
• Development

  The place to discuss new additions into XCP-ng
  254 Topics

  3k Posts

  O

  It's more like "partially"/loosely based on Alma (10, not 9). And yes, the kernel will be far more recent, same for Xen and so on.