Just a quick update. I tried changing the time to see if somehow doing it at midnight was causing the issue. I also tried changing the destination for the health check to restore to in case it was some issue with the HDD. Neither were successful.

@tsukraw we will have to improve the doc First migration : [vm source] => [vm on xcp] Check [vm source] => [vm on xcp] => [copy/clone of vm on xcp] test on [copy/clone of vm on xcp] <-- remove [copy/clone of vm on xcp] Final migration stop [vm source] launch the same migraiton. The data already transfered won't be retransfered applues the fixes you had to do during previous test start [vm on xcp]

@Danp My apologies for not being more specific. I’m encountering an issue with XOA deployment on a home lab environment. Environment Details: Installation source: USB Hardware: 16GB RAM, 1TB NVMe HDD Initial install: Completes successfully Dashboard: Displays expected status Steps Taken: Installed XCP-NG from USB — installation and setup completed without errors. Verified dashboard — all components appeared healthy. Deployed XOA to the existing HDD — process executed as expected. Observed Behavior: After deployment, XOA appears healthy overall, but the final item labeled “NEW” does not appear in the interface. Expected Behavior: The “NEW” item should be visible after deployment. Mark

@Pilow You might be right, this may be simpler to implement than we imagined. We'll keep you informed when we progress on this.

Thanks @Pilow for the test

@rizaemet-0 I've also enabled SAML and the login interface is a little bit odd, not only the remember me button but also the capitalization of SAML which is lowercase. It is a cosmetic issue, but still an issue.

@olivierlambert Yes I previously was. now back on VHD. This was in my home lab, not work enviorment.

@bvitnik Thank you for the great response. I have had great success with Terraform - great work. I'm not touching ocaml myself. And yes, Citrix... they are still above VMware/Broadcom on my list. But SMH. I keep promoting XCP-ng hoping some large companies take advantage of it. It's much more valuable to me than nautobot, for example.

To anyone still having this issue or finding this thread when searching online: "How to clone a VM between hosts in Xen Orchestra" or similar... The key piece of information missing from all these answers is that you must first connect both hosts (XCP-ng) servers to the same Xen Orchestra instance before you can clone (copy (export/import)) a VM from one host to another while using the Xen Orchestra GUI. Note that as mentioned in the first reply that this is only one solution, given both hosts can see each other over the network. You can also manually export and import the VM as an image file to your local PC's storage if needed. To do this, first navigate to "Settings->Servers" and configure/connect the destination host alongside the existing host so you end up with two hosts connected to the same Xen Orchestra. Note that Xen Orchestra can display information and manage multiple hosts if required (does not have to be tied to a single XCP-ng instance). Then navigate back to "Home->VMs" and you should now see all VMs listed for both hosts in the same list. From here you can select the VM to clone and from the copy dialog menu when you select a "SR" you should now be able to select between both host's disks (Local Storage or Pools) to copy the VM onto. Note that this command will spin up two separate tasks: an export and import task simultaneously on each host to complete the copy (sort of streaming it at the same time). Also don't forget to first shutdown the VM first before you copy it so you do not risk losing/corrupting any live data while it is cloning. Hope this helps everyone.

Adding this to our topics to discuss

Since GPU passthrough is involved I'd ping @Team-Hypervisor-Kernel

@florent Hi @all, sorry for my late reply, but i was on site at a customer yesterday. I can confirm its working again as expected. Not only this, but it also cleaned up all the additional Replikas now. Great work and thanks for all your efforts. Kind regards Alex

Can you share how you created the template? And copy here the template object from xo-cli or the rest api: xo-cli list-objects type=VM-template id=<your_template_id>?

For completeness sake. Confirming that the fix also works in my second lab as well.

@stevewest15 these errors are normal on XO from source, since you don't have licenses the configuration to use for ipmi sensors depends on the bios strings . Could you post the bios string of your hosts ? Dell configuration is used if system-manufacturer' contains the string dell

What is the output of the following command: cloud-init schema --system

@McHenry said in pfSense Guest Tools: I have been using pfSense with xcp-ng for a while now without installing the guest tools. Due to some networking complications I have decided to install the guest tools to eliminate this as the cause. Q1) Are the guest tools required on pfSense and what do they do? Actually no, their main functionnality is to provide some data (memory usage, IPs) to XCP-ng to report them upward, AFAICT, it doesn't impact behavior in a significant way. It's actually not "PV drivers". Q2) Are these tools being maintained? This version of the guest agent is very limited and ancient (I don't exactly what it does, but not much IIRC). We're working on a new guest agent in Rust, which actually works pretty well on Linux, Windows (actually used in latest Windows drivers) and FreeBSD (NetBSD is also possible, but current code lacks some platform-specific bits). But we still need to sort-out some issues (some technical and some others non-technical) before making it broadly available / making it packaged.

@AlexanderK You're welcome, i'm happy my tests are useful !

@Bastien-Nollet nice !

Again, XCP-ng and Xen Orchestra are really meant to work together: that’s by design. Our goal is to offer a unified stack with one consistent REST API to manage everything, across any number of pools. XO already handles a ton of things: auth (with oidc, SAML etc.), multi-pool aggregation, RBAC/ACLs, task tracking, templates, backups, live migrations, etc. By building on top of XO, we can focus on adding real value instead of re-implementing all that logic again in any 3rd party program we maintain in full open source and for free. And honestly, I don’t see any issue relying on XO: everything is fully open source, and all features are available for free from the sources, just like it’s always been. Nobody’s forcing you to use one or the other: if you’d rather build directly on XAPI, you absolutely can.