@Tristis-Oris That's a "known issue": https://xcp-ng.org/forum/topic/7827/xoa-does-not-refresh-quickly-status-of-nics XCP-ng-center is showing the update.

@Danp Thank you i did it'a was disk issue and i see the documentation that's help

This is an issue inside your guest, so take time to read the logs and try to make sense of it. It's possible you don't have enough resources in the VM to make the migration, but from "outside" it's hard to tell.

That machine has suffered a repeated hardware failure, and has been taken offline, and I think I'll reinstall XCP-ng from scratch on it, so the exact problem described here is moot. However, I'm still interested to learn by what mechanism XOA connects to the VM's VNC console, if anybody feels like teaching me? Thanks in advance.

Do read the specific section in docs about virtualizing xcp-ng. https://docs.xcp-ng.org/guides/xcpng-in-a-vm/

@paco said in Storage IOPS and throughput dropouts?: @nikade Short answer is that the spikes seem to have smoothed out. I'm not really sure what happened. I don't have them at any resolution now. Perhaps some kind of heisenbug. Happy to hear that

@bpsingh76 You should be able to run "xe vdi-list" on these and see if they are attached to anything. If not, it would appear they are just leftover templates.

Thank you all! I was on an older release of XOCE. I haven't wanted to update as the last few times I did, it broke the nightly backups. So stuck with an older version of XOCE that seems to have been stable in our environment. I updated XOCE to latest build: Xen Orchestra, commit 32228 Master, commit 32228 I was able to manually update the second host (by running yum update). Then restarted the pool master and now I'm trying to vacate VMs from second host back to master so I can reboot the second host. However the live migration seems to be taking much longer from the second host back to master. All VMs use shared storage connected via NFS to this pool. I was thinking it should just take a few minutes to do a live migrate but so far it's been 12+ minutes and it's only at 12%: [image: 1723571571077-dca691d2-5be0-41f5-8669-92cfcf5175b6-image.png] The network I selected for the live migration is a 20Gbe (bond of two 10 Gbe). UPDATE: The live migration progress sped up and it was completed in about 16 minutes instead of the 1hr it was estimating.

So far this seems to work well. we will test this and inform if there is any issue with it. On behalf of my customer i would like to thank you for the quick response!

hi Brands, In your post when you say "importing xo manually" could you paraphrase or elaborate ? Do you mean installing XO ? By the way yes XO has to be on the same subnet as your XCP-Ng computer. Seems to me it would be easier, for a start, not to block your internet. Best,

@Danp the source. this is a lab to learn this environment to eventually replace VMWare.. Comparing this and Proxmox.

Ok figured it out at the end using xe pool-list on the existing pool gives me a list of existing hosts on the pool, and there was one that has been taken offline, without detaching in XO. So I did a xe host-forget uuid=<host uuid> because xe pool-eject doesn't work on offline host. And now I can add the new host just fine. Thanks everyone for helping!

Hi, Because updating doing an RPU while using XOSTOR is more tricky. The order of operation is slightly different, and applying the existing RPU algorithm will simply break your storage. We need to restart the satellite in a different order. I don't remember where it's documented, let me ask @ronan-a

I don't see the reason, the UUID is completely internal to XAPI. You might want to compare the 2 objects (like doing a diff between 2x xe vdi param list)

Indeed, XenCenter isn't a supported client for XCP-ng. To delete those, you need to use xe CLI. I don't remember exactly which part is used by XenCenter, might worth some community feedback or taking a look at the XenCenter code.

Thanks, In a perfect world, self-service users should be able to manage ACLs on their VMs and show backup tab on VM.

@jasonnix Yeah that folder can fill up quite heavily. See the following on how to clear the cache with yarn https://yarnpkg.com/cli/cache/clean

@Andrew Could that be one of the new options that only apply to XCP-ng 8.3 or later?