I updated the doc accordingly: https://xen-orchestra.com/docs/community.html

@mauzilla To boot an ISO in a VM, you need to select "DVD" in the boot order, put it first, and hit "Save". Then boot the VM. For ANY system (real or VM), you need boot it with the same type of bootstrap as it was installed to use. BIOS or UEFI. If you change the boot type then you have to make the OS ready to use the new/different settings (not just a VM problem). If you created a Windows image from a working system that booted with UEFI then you have to copy ALL partitions (the whole disk), not just the C windows drive.

@stormi Thanks for the big help that fixed the issue.

Hi, first of all, thank you for developing and supporting these awesome products. I witnessed a similar issue upon running continuous replication on a VM after growing one of the disks on the source side. I run delta backup to a NFS share and continuous replication to another XCP-ng host in one job. The most important part of the relevant log messages remind me of this issue - this topic is the only similar reference I was able to find, so I hope this is the right place to post. If not, please let me know, and I'll create a new topic Mar 21 01:00:29 xcp-ng-2 xapi: [ info||8947241 INET :::80|Importing raw VDI R:3967654dad6b|vhd_tool_wrapper] Executing /bin/vhd-tool serve --source-format vhd --source-protocol none --source-fd 1f47b1fe-a9ea-4bda-ab8e-2101e5677059 --tar-filename-prefix --destination file:///dev/sm/backend/f7aca870-12e0-8352-9f86-f52d575eb313/6cd16448-6839-476d-93b1-2f8b816c827f --destination-format raw --progress --machine --direct --destination-size 0 --prezeroed Mar 21 01:00:29 xcp-ng-2 xapi: [error||8947241 INET :::80|Importing raw VDI R:3967654dad6b|vhd_tool_wrapper] vhd-tool failed, returning VDI_IO_ERROR Mar 21 01:00:29 xcp-ng-2 xapi: [error||8947241 INET :::80|Importing raw VDI R:3967654dad6b|vhd_tool_wrapper] vhd-tool output: vhd-tool: Non-zero size required (either a pre-existing destination file or specified via --destination-size on the command line)\x0A I'm currently running Xen Orchestra compiled from sources, on commit 5bc44363f9ac9fa534f3247e697f1b3c6991e916. XCP-ng is on version 8.2.0. I know that this is not fully up-to-date, but after retrying that backup as a first measure, Xen Orchestra ran a full backup for that VM, so I can't reproduce that issue anymore, but I figured posting that here might help resolving the aforementioned issue, if the causes correlate.

Hi @LTSFGriffin Netbox sync plugin is available in Enterprise tier

@Darkbeldin I wasn't sure about turning on two-factor. I went through that process and generated the "app password" and it seems to be working. Thanks for the info!

FYI, we modified the deploy script to be able to automatically modify XOA's VIF to run on the management network. So even in case of using only bonded networks like @Low351, this will now work.

@davidg said in Dashboard Health gives 'an error has occurred': 5.58.1 That's ancient, so not a valid comparison. It's likely that a recent commit has broken something that they will eventually identify / fix.

I did for sure. But I noticed that a new commit(886ff2cd7) was made literally in about the last hour and after updating again to that version all is good!

@olivierlambert We are using rrd2csv to get host cpu stats into SQL to provide nice Grafana page sorted by pool. It would be nice to dial even further down to the vm's that are running high cpu or have memory burden.

@BenjiReis XO from the appliance. I hadn't noticed the tasks queue counting up like that before I tried the recipe, but I'm perfectly willing to accept that I'm just not that observant. Thanks!

Community version doesn't have a release number, but a commit version on master. Please check you are on the latest commit and rebuild

That's correct. There's no more updates, that's why you MUST upgrade to 8.2 (see https://xcp-ng.org/docs/releases.html#all-releases )

@wade_solarch Short answer: try to avoid that. Back in the old XenServer days, you had to manually change the cpu feature flags so it would work at all. https://xcp-ng.org/docs/requirements.html#pool-requirements This confirms that you can't mix Intel & AMD in a pool https://xcp-ng.org/docs/requirements.html#pool-requirements This explains Heterogeneous pools a little

@stevewest15 Happy to help

VDI to coalesce number should decrease over time yes. If it's not, you might have a coalesce issue in your storage, check the /var/log/SMlog in the relevant host (master for shared storage, the host attached to its local storage otherwise). Rescan will scan for the LV/VHD files. But coalesce is automatically checked/started every 5 minutes. Coalesce can take time (depending on SR read/write and quantity to "merge"). Next releases will have a visible task for pending coalesce (next major XCP-ng release). Until then, you can do a ps axf | grep coalesce to see if there's something happening.

@olivierlambert Done: https://github.com/vatesfr/xen-orchestra/commit/33b45d2eda2ce6d8071541da246bdcfd06b133b8 It's not perfect but that should help Example: vm.start { "id": "123e4f2b-498e-d0af-15ae-f835a1e9f59f", "bypassMacAddressesCheck": false, "force": false } { "errors": [ "R620-L3: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)", "R620-L1: HOST_NOT_ENOUGH_FREE_MEMORY(216430280704, 18778341376)", "R620-L2: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)" ], "message": "", "name": "Error", "stack": "Error: at Xapi._startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1358:15) at Xapi.startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1393:7) at Api.callApiMethod (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:307:20)" }

@Danp K great, thanks.

@olivierlambert well, yes, there is definitely room for improvement on that part of the gui ;). although I was able to get any other plugin working no worries though, the quick fix is to remove the (optional)