Great news 🙂

@Danp @olivierlambert so I'm going to build this out next week and how can I do the build out with the trials and after that how much would a 4 node xoa managed HCI with XOSTOR run for licensing?

Also are there any guides for best practices for deployment of above configuration? IE what type of network configs for the XOSTOR and the pools.

Also the vmware has a citrix deployment on it so do you have a connection aspect for citrix to interface with the pool same as vmware has?

My R730 servers have 8 10gb fiber ports each so take that into consideration for the xostor configuration.

@dinhngtu Great. Let me know if you need anything else. Hope you find the issue. Never worked reliably here.... Sometimes does.

@yann Thanks for the fast reply ❤

Ok, I am opening a ticket, and providing a simple support script.

@olivierlambert No, i changed nothing.The boot Mode is UEFI (see first screenshot).
I will check if a downgrade (if it's possible) fix this issue.

turned out that this is not necessary. An easier option is to simply add the bootparameter

aacraid.numacb=1000

before booting into xcp-ng.

As of my current understanding this makes sure that the xen-specific larger management fib size of 16 is taken into account (the driver default is 8).

Only tested on Version 8.2.1

@Maelstrom96 said in Icon appears in the XOA interface:

do you have pointers on how to build a slackware package for xe-guest-utilities?

If you still want to have a try at building (even though that will not let XO show an icon) the first question is, do you really want to build a slackware package (as in "contribute a package to Slackware so it is available to all Slackware users), or just get it built.
In the latter case, @TeddyAstie answered already, but if you really want to get into packaging, you should look on the Slackware side (e.g. here). I would have added "you may also want to have a look at any existing packaging of a Rust program", but given how "unstructured" the whole thing seems to be (I stand quite surprised of those 1995-looking all-manual instructions), you should be able to build a package once you've built the binary using rustup.

It has been added to the backlog, thanks!

Hi,

You can use delay or if you want specific order, you need to use vApp, that you can configure with the CLI. See https://docs.xcp-ng.org/appendix/cli_reference/#appliance-commands

@Tristis-Oris sharing my google drive link via chat... should be easy to upload it there

@Forza As mentioned, for VMs and the OS to be able to leverage such features as turbo mode and C-states, the BIOS has to be set to enable OS control. Without giving such control to the Linux OS, there are indeed various limitations. The uncore parameter must also be set to "dynamic" (OS DBPM) and if not in the BIOS, has to be set via the command:
xenpm set-scaling-governor performance
to put into effect immediately and to be able to be preserved over reboots, the command:
/opt/xensource/libexec/xen-cmdline --set-xen cpufreq=xen:performance
has to be run. This all assumes there have not been significant changes since I last tried all this out, of course, which was over four years ago, but @abudef has older hardware and I would think that would allow for this to be taken care of in the BIOS. To quote from my first article on this topic:
"Red Hat states specifically in the article https://access.redhat.com/articles/2207751 that a server should be set for OS (operating system) performance as otherwise, the operating system (in this case, XenServer) cannot gain access to control the CPU power management, which ties in with the ability to manage also the CPU frequency settings."

BTW, the article you reference is now just about ten years old and references Xen kernel 3.4. The latest Xen release is 4.18.

Great! You are right! I had completely forgotten about it!
Thanks a lot!

@knightjoel I have not but glad you found something and I wasn't (at least then) crazy.

@olivierlambert Thanks, for at least acknowledging that I'm not crazy. I'm willing to help out with testing, just let me know what's needed of me. I'm not a developer by any stretch of the imagination, but I am a seasoned SysAdmin with just enough Linux knowledge to be a little dangerous...lol.

@techknowbabble said in GRUB waits for confirmation:

What did finally work was re-installing with the 'no serial' option and everything seems to be working as expected now. I only have a handful of XCP-NG installations under my belt but I wonder if this is a known bug or if anyone else has had a similar experience.

It's not something I've ever seen before and I've done quite a few installations but I can think of some possibilities as to why something like that might fix the problem. My best guess is that there's something built into, connected to, or otherwise in your system that looks like a serial port (maybe even a real serial port) that spits out a character or two into the system at boot time, confusing GRUB and stopping the normal boot process. The bad KVM I mentioned before was doing something like that, throwing a bogus keypress into the system at boot time.

@ph7 This is being investigated by the XOA team. We will update this thread when more information is available.

Hi!

Yes, we'll develop the hub in the future, we just lack the resource internally to prioritize this against the rest, but as we a growing fast, expect more things coming in here 🙂