@julien-f Thank you, that's super helpful and even easier than I thought it would be.

I guess I'll partially answer my own question by pointing out that I can background the commands with & so it should run them all at once anyway. Sorry, still new to bash scripting and my Linux skills are a bit rusty but improving.

@olivierlambert Hi, I really appreciate your time!

I'm using a US QWERTY keyboard on a 2-year old MSI laptop running Windows 11. I first noticed this issue a few weeks ago when I first deployed xo-server v5.151.0 / xo-web v5.152.1 built from your sources.

A little bit ago I actually tried this in Brave browser and using shift worked perfectly fine. Then I tried it in vanilla FireFox and it worked fine there too...

I daily drive LibreWolf, a security/privacy version of FireFox and I usually don't ever have issues with it but I'm gonna chalk this keyboard thing up to something related to that.

Sorry about that!

The task is green, meaning it's done 🙂

@olivierlambert @stormi is the one who helped me find and fix the issue. I just wanted to update my old thread in case someone else happened across the problem until it gets fixed in XO.

Yay! You should try XO 6 UI on mobile, maybe it will be better 🙂

It's 2 different things. It's not because you add RAM that you might need to raise the Node memory either. First, add memory and see if it's enough 🙂

@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

@tsrats Actually had it bookmarked 😉 (like a few others)

IIRC, XO doesn't know, it's a message coming from XCP-ng. It will compare the CPU info between source and destination.

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%:

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,