Thanks all, for chiming in. I was hoping that perhaps someone in the community may have done what AlmaLinux did so the amd64_v2 hardware can still use RHEL 10.x.
I'm working on something in my lab and was wondering if it should support RHEL 10, but looks like I need to table that for now.
Good-day Folks,
My Environment:
Hosts: 3-Node Pool (running XCP-ng v8.3.0)
Patch Level: 20251218
Manufacturer: HP, (,ProLiant DL360p Gen8,)
CPU Model: Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz
BIOS Info: HP (P71)
Xen Orchestra: v5 commit 5fcb6
Anybody experiencing any trouble getting the Red Hat Enterprise Linux v10.x ISO files to boot when creating a new VM in Xen Orchestra? I ran into a similar problem with AlmaLinux 10 (I reported it on this thread and @bogikornel responded and informed me that it was related to v2 CPU support having been dropped).
Giving that AlmaLinux is derived from RHEL, my hunch is that this issue may be related. However, I don't see any releases of the RHEL 10.x ISOs that are for the older v2 CPUs.
Here are a couple of screenshots:
UEFI Only
UEFI + Secure Boot Enabled
@Andrew Hey budd, thanks for the pointer. That ISO worked, thanks.
@lsouai-vates Thanks for the response. I was just looking for a way to create a full screen display for a NOC, without requiring interactive login. Sounds like that's not possible at the moment?
@Andrew Thanks, giving that a shot now to see if it works.
@bogikornel Thanks for pointing that out.
ENVIRONMENT:
HOSTS: XCP-ng v8.3 on HP ProLiant DL360p Gen8
XOCE: commit d7fe4
Does Xen Orchestra support AlmaLinux 10 in UEFI mode?
I ask because I am able to boot the AlmaLinux 9.6 DVD/ISO without any issues, however, the v10 DVD/ISO fails to get past this point:
I also noticed that there is no AlmaLinux 10 listed in the template drop-down list when creating a new VM. I have confirmed the integrity of the downloaded ISO (hashes match): SHA256: 6c443f462b3993d15192a7c43ba8dfa3f232514db47d38796dab007a7455ae1a
SHA256 Hash from XCP-ng point of view:
SHA256 Hash from the storage system's point of view (TrueNAS):
@olivierlambert Agreed. Thanks, still, for pinging them again.
Today being Friday, I'll be in the lab for a bit, troubleshooting other issues unrelated to Xen Orchestra. Would be nice to work on this as well.
No worries, though, I'll sit tight and exercise patience.
@olivierlambert Any word from the team on this?
Good-day Folks,
An idea came to mind recently, to display the Xen Orchestra dashboard on a large screen in a NOC. So I wanted to see if it were possible to pass a user's authentication token to any of the URLs in Xen Orchestra to accomplish this.
For example, if the Dashboard can be reached at https://xoa.local/#/dashboard/overview, how can I pass the authentication token?
I've already tried https://xoa.local/#/dashboard/overview&authenticationToken=xxxxxx and it didn't work.
Is this even supported, currently?
@Forza Good point. I need to apply the latest patches anyway, so I'll be rebooting the pool later today anyway.
@Forza thanks for the caution. I wondered about that as well, so I initially tried with just -f and it didn't work. So this is what ended up working for me.
Perhaps one of the developers from the Vates team can chime in as to how best to handle such a situation properly; where the NFS Server is simple no longer online to support the normal unmounting routine.
@tjkreidl said in Force Remove a NFS Storage Repository:
@kagbasi-ngc See if this thread can help you out:
https://xcp-ng.org/forum/topic/6618/how-to-remove-this-sr-nfs-storage/
A BIG THANK YOU! This was quite helpful, and helped me resolve my issued.
Here's what I ended up doing (after reading the post you shared):
STEP 1: On each host, I ran the mount command (without any parameters).
STEP 2: I identified the mount point of the SR in question - for me it was /run/sr-mount/<SR-UUID>
STEP 3: On each host, I unmounted the NFS share with umount -lf /run/sr-mount/<SR-UUID>
STEP 4: From the pool master, I identified the UUID of the PBDs with xe pbd-list sr-uuid=<SR-UUID>
STEP 5: While still on the pool master, I unplugged each PBD with xe pbd-unplug uuid=<PBD-UUID> force=true (I had three to unplug, adjust accordingly)
STEP 6: I confirmed in Xen Orchestra that the status of each host connection had changed to Disconnected
STEP 7: From the pool master, I forgot the SR with xe sr-forget uuid=<SR-UUID>
Hope this helps someone out there. Thanks again @tjkreidl
Good-day folks,
I have an old NFS storage repository that was previously hosted on a Windows Server 2016 machine running NFS Server for Windows, that is being stubborn and I would like to remove it forcefully, along with anything related to it. The NFS Server is no longer online, so the connection isn't alive and I suspect the removal is failing because XOA can't unmount it.
I have tried being nice by clicking the Disconnect from all hosts button, but the tasks sits there for several hours then mocks me and disappears. I have tried to unplug the connection from each host, one at a time, same results - the wheel spins for some time then goes away.
Any assistance would be greatly appreciated, thanks.
My Environment:
Hosts: 3-node XCP-ng Pool v8.3.0
XOA: v5.106.4 build 20250604
Environment: Airgapped
@olivierlambert You got it, I'll do that. Thank you.
@olivierlambert Understood, however, I'm failing to see what part of my posting was irrelevant to the topic at hand. I was merely sharing what I'd experienced as well and providing context.
I thought this was the kind of feedback expected of community members, who want to see this project flourish?
@Tristis-Oris Just wanted to add my 2-cents that I, too, ran into a similar issue just a couple of days ago and it feels like this could be a bug.
My scenario:
I had a fully working three-node pool. One of the hosts had a 12 CPUs, whereas the other two had 16 each - so I would occasionally run into errors with the load-balancer trying to migrate VMs (usually something like "VM Lacks Feature"). So I decided to replace that host with another one that was identical to the other two hosts.
I did what I thought was logical; detached that host from the pool, installed XCP-ng 8.3 on the new host, gave it the same hostname and IP address, used the same root password, then powered it up. Now, without doing anything at all, when I went into XO and viewed the Pools page I saw the new host in a pool by itself (which was strange, because I wasn't expecting that). I was expecting to have to manually add a new server to XO - but hey, perhaps there is some kinda discovery going on.
Anyway, I attempted to add this new host to the pool but was unsuccessful. I was met with an error about the SDN certificate existing. Unfortunately, I didn't write it down. But ultimately, the solution for me was to run the same xe pool-uninstall-ca-certificate name=sdn-controller-ca.pem command on the new host.
Anyone from Vates care to comment?
@JBlessing At the bottom of the release page (https://github.com/xcp-ng/xenadmin/releases/tag/v25.04) are the links to download either the MSI installer or a Zip file containing the entire application (if you want a portable package).
@lsouai-vates Duly noted.
If amd when you do get a moment, could you have a look at https://xcp-ng.org/forum/post/94297 and offer up any guidance on how I can stop the debug log entries and also the double timestamp entries in the audit.log file?
Thank you.