@high-voltages I believe turbo boost takes it up to 3.3GHz. The 2.7 is reduced workload
Best posts made by Affonso
-
RE: Bad Performance CPU? get-cpufreq-para failed
-
RE: Faulty XCP-ng host after update (but only on XO)
Alright I updated XO again and the problem is gone.
I would just like to comment that unlike described by another user that was only happening on single-node installs, this was happening to me in 2 out 4 nodes in a cluster. Two hosts would show normal, and another two showed glitched.Anyway, SOLVED!
-
RE: Faulty XCP-ng host after update (but only on XO)
Well since there is no issue when looking at XOA but only on XO, I am going to disregard this issue and wait to see if it resolves by itself until the weekend and if not I'll try and remove this XO build and make a new one.
Thank you for your suggestions, I'll try and let know how it went.
Latest posts made by Affonso
-
RE: Bad Performance CPU? get-cpufreq-para failed
@high-voltages so nothing there hints you to a problem with the drive SDA on the slow "host"?
-
RE: Multiple XO applications for one pool?
@mestafin Yes, even at the same time.
-
RE: Bad Performance CPU? get-cpufreq-para failed
@high-voltages I believe turbo boost takes it up to 3.3GHz. The 2.7 is reduced workload
-
RE: Bad Performance CPU? get-cpufreq-para failed
This also happens on our servers.
This is from a single node homelab running on a Dell PowerEdge r620
# xenpm get-cpufreq-para [CPU0] failed to get cpufreq parameter [CPU1] failed to get cpufreq parameter [CPU2] failed to get cpufreq parameter [CPU3] failed to get cpufreq parameter [CPU4] failed to get cpufreq parameter [CPU5] failed to get cpufreq parameter [CPU6] failed to get cpufreq parameter [CPU7] failed to get cpufreq parameter [CPU8] failed to get cpufreq parameter [CPU9] failed to get cpufreq parameter [CPU10] failed to get cpufreq parameter [CPU11] failed to get cpufreq parameter [CPU12] failed to get cpufreq parameter [CPU13] failed to get cpufreq parameter [CPU14] failed to get cpufreq parameter [CPU15] failed to get cpufreq parameter [CPU16] failed to get cpufreq parameter [CPU17] failed to get cpufreq parameter [CPU18] failed to get cpufreq parameter [CPU19] failed to get cpufreq parameter [CPU20] failed to get cpufreq parameter [CPU21] failed to get cpufreq parameter [CPU22] failed to get cpufreq parameter [CPU23] failed to get cpufreq parameter [CPU24] failed to get cpufreq parameter [CPU25] failed to get cpufreq parameter [CPU26] failed to get cpufreq parameter [CPU27] failed to get cpufreq parameter [CPU28] failed to get cpufreq parameter [CPU29] failed to get cpufreq parameter [CPU30] failed to get cpufreq parameter [CPU31] failed to get cpufreq parameter [CPU32] failed to get cpufreq parameter [CPU33] failed to get cpufreq parameter [CPU34] failed to get cpufreq parameter [CPU35] failed to get cpufreq parameter [CPU36] failed to get cpufreq parameter [CPU37] failed to get cpufreq parameter [CPU38] failed to get cpufreq parameter [CPU39] failed to get cpufreq parameter [CPU40] failed to get cpufreq parameter [CPU41] failed to get cpufreq parameter [CPU42] failed to get cpufreq parameter [CPU43] failed to get cpufreq parameter [CPU44] failed to get cpufreq parameter [CPU45] failed to get cpufreq parameter [CPU46] failed to get cpufreq parameter [CPU47] failed to get cpufreq parameter
# cat /proc/cpuinfo | egrep -i mhz cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059 cpu MHz : 2700.059
-
RE: Faulty XCP-ng host after update (but only on XO)
Alright I updated XO again and the problem is gone.
I would just like to comment that unlike described by another user that was only happening on single-node installs, this was happening to me in 2 out 4 nodes in a cluster. Two hosts would show normal, and another two showed glitched.Anyway, SOLVED!
-
RE: Help me, this forum software is horribly confusing
@DustinB
You mentioned you come from phpBB which is by itself a whole other beast. It's a very old application, over 20 years old, brings features from other ages when there were less solutions, and very on par with other apps from that time.By the time nodeJS and other web frameworks this forum is built in appeared, phpBB was starting to grow its first pubes. Developers who went into these apps were perfectly acknowledged with phpBB (I mean... it's been around for a while, really), and developers did not intend to replicate it, but to create new, different Bulletin Boards apps. You'll quickly get used to it if you take a while to explore and see it's actually rather simple. Just found weird that you never came across with this type of board, they are quite common and been around for a while.
-
RE: Faulty XCP-ng host after update (but only on XO)
Well since there is no issue when looking at XOA but only on XO, I am going to disregard this issue and wait to see if it resolves by itself until the weekend and if not I'll try and remove this XO build and make a new one.
Thank you for your suggestions, I'll try and let know how it went.
-
RE: Faulty XCP-ng host after update (but only on XO)
@olivierlambert Yes only one server listed
-
RE: Faulty XCP-ng host after update (but only on XO)
Now I just did as you suggested went to Settings > Severs
Disabled the master, counted to 10, enabled the master.Problem persists. (for a moment I thought it was gone but then I realised I was looking to XOA not XO).
-
RE: Faulty XCP-ng host after update (but only on XO)
@olivierlambert well the XO instance is connected to the Master, it's not the master node showing this problem.
As when I rebooted the XO already assumed it was "disconnecting" and "connecting", but I am going to do it manually.I have:
- Rebooted the XO VM
- Rebooted the XCP node
- Rebooted the XCP master
none produced any different result.