Subcategories

• Compute

  All Xen related stuff
  606 Topics

  6k Posts

  F

  @redakula said in Coral TPU PCI Passthrough: Frigate.nvr which is one of the popular uses for the Coral do not recommend it for new installs either. Frigate updated their recommendations because of the Google decision to sunset the device and because there are alternative options available to frigate for image inferencing. The coral is still supported though, and frigate is not the only use case or platform that can benefit from an accelerator. At the end of the day if you've already got the hardware, and it's efficient enough to run, then not using it is a waste or resources that could be allocated to other VMs.
• XO Lite

  The integrated web UI to manage XCP-ng
  26 Topics

  348 Posts

  O

  It's not meant to be used like that. If you are behind a NAT, the right approach is to have your XOA behind the NAT and inside the same network than the hosts. That's because hosts will always use and return their internal IPs to connect to some resources (stats, consoles etc.). XOA deals with that easily as being the "main control point" for all hosts behind your NAT (or a XO proxy if you prefer).
• Migrate to XCP-ng

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

  1k Posts

  D

  @firefly because the underlying hardware that the VM has registered has likely changed, maybe substantially. A sysprep has the Windows system go through and validate what it's hardware is, it removes hardware specific drivers namely, but it does other stuff too.
• Hardware

  Hardware related section
  161 Topics

  2k Posts

  D

  @TeddyAstie Thanks for the update. I do actually have a VBIOS for that GPU, but I wasn't entirely sure what to do with it - is there a process to inject it? I've found resources for Proxmox and others, but I really like XCP and equally I don't want to migrate my entire setup just for that. If it's really tricky then I'm not too worried about it, as I say the VM actually runs the cameras perfectly fine on CPU alone, it's negligible. Edit: Looks like this post might answer my question: https://github.com/xcp-ng/xcp/issues/786 "Even when specifying romfile and rombar properties on the xen-pci-passthrough device in QEMU, the ROM region is not mapped into guest memory." timemaster5 created this issue in xcp-ng/xcp open PCI ROM BAR not exposed to guest when using xen-pci-passthrough #786
• Development

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

  3k Posts

  P

  @olivierlambert said in Rust-based guest-tools... How are things going?: The thing is that it works very well and doesn't need fixes… I know, not usual right? It was so stable that we left it like that waiting for people coming for bugs and nothing happened… We'll cut a 1.0 in the next weeks/months. I have indeed seen the stability of it myself. But the lack of updates made me worry anyway. But I'm really looking forward to the promotion to 1.0 as well. Thanks!