Subcategories

• Management

  VMs, hosts, pools, networks and all other usual management tasks.
  446 Topics

  3k Posts

  G

  I am running NVIDIA P40s on a DELL R720/R730 and a NVIDIA A2000 12GB on a DELL Optiplex 9010 in my playlab. Getting the GPUs to be accessible for VMs was quite easy: shutdown the XCP-ng host, install the GPUs, start the host again, activate the GPU in the advanced settings of the host in the PCI Devices section (“Passthrough enabled”). The host will restart at this point after displaying a warning. That's it – the GPU can now be assigned to a VM in the VMs advanced settings. I do use the GPUs for AI workloads under Debian though, so your use case might vary.
• Advanced features

  ACLs, Self-service, Cloud-init, Load balancing...
  98 Topics

  825 Posts

  D

  @bleader Hopefully the palm print on my forehead isn't visible from where you are sitting. Of course the interface needs an IP address. In my defense, normally for something like this, I wouldn't put it on the bonded interface with all the trunked VLAN's for guest traffic (we don't give that one an IP) and it would go on the other bonded interface that isn't trunked and does get an IP, but these are test hosts and I didn't set up the other bond, so it is pulling double duty. I was able to set the IP's and get SDN working. Thanks!
• Backup

  All XO backup features: full and incremental, replication, mirrors...
  459 Topics

  5k Posts

  P

  @greg_e & @florent I have gone back through the commits, and I believe it is 0a042d2f54a74ecc11a377809272337cb5c880d9 that introduces the bugg. https://github.com/vatesfr/xen-orchestra/commit/0a042d2f54a74ecc11a377809272337cb5c880d9 My last known good and working commit is the one just prior to it, a831ac7b213eb6fc7f05fbd466407d5cf379cfe9. Tried with the latest commit (as the time of writing). 91c5d98489b5981917ca0aabc28ac37acd448396. But this didn't fix it, unfortunately. Filed a issue/bugg-report on github for this https://github.com/vatesfr/xen-orchestra/issues/9472 @pilow A lot of updates can, and do, happen in a month or two cloudrootab created this issue in vatesfr/xen-orchestra open Backup job failed: forbidden operation: destroy is blocked: protected from accidental deletion #9472 0 fbeauchamp committed to vatesfr/xen-orchestra fix(xapi): correctly block operations blocked operation on vm creation does not seem to work also importIncrementalVm was not unlocking it at the end
• REST API

  Everything related to Xen Orchestra's REST API
  76 Topics

  578 Posts

  R

  @Pilow tags can work and the path to them is much more succinct. Thanks!
• Infrastructure as Code

  Terraform, Packer or any tool to do IaC
  48 Topics

  444 Posts

  C

  Kubernetes CCM for Xen Orchestra v1.0.0-rc.1 We’re shipping v1.0.0-rc.1, our first release candidate on the road to a stable 1.0.0! This RC is feature-complete and ready for real-world use. Please try it out and share any feedback—bugs, regressions, or usability notes—so we can polish the final release. Thank you for testing and helping us! https://github.com/vatesfr/xenorchestra-cloud-controller-manager/releases/tag/v1.0.0-rc.1 Golang SDK for Xen Orchestra v1.11.0 SDK v2: VM and Task services now match the latest REST API. Host service has been added for host data retrieval. Integration tests have also been strengthened to boost reliability. The v2 SDK is gradually becoming our main library for all the other DevOps tools (Kubernetes drivers, Terraform provider…). There are BREAKING CAHNGES in the v2 SDK, so please read the release notes carefully. Remember that the v2 SDK is a beta version and can be subject to significant changes. The current semantic versioning we use is mostly for the v1 SDK. When the v2 SDK becomes stable, the major version number will increase. https://github.com/vatesfr/xenorchestra-go-sdk/releases/tag/v1.11.0