Ummm... Your documentation sure makes a lot of us jealous!
Was that just a layout program like draw.io, or are you using something like Netbox for that work?
I'm starting on GLPI to handle more than just flow paths going forward, need to track serial numbers, date of purchase, maybe installed software as I go forward. A project for the summer.
So there might be two other things to look into if you get bored.
My master host hung on reboot, after about 10 minutes I forced the power off, and then back on. Host is HP T740 Thinclient with AMD v1756b processor, 64GB of DDR4 SODIMM, Intel dual x520 PCIe card, and an Intel i226-v in the a+e slot, plus the onboard Realtek NIC, BIOS at 1.20 which I think is still current for this model. All three hosts are identical with possible exception of x520 card revisions, host 3 might have an older revision (donations accepted for x710 based cards 
)
Otherwise everything went as planned, all three are updated and all three needed to have the toolstack restarted to see the stats. I only have 2 small Linux VMs on this system right now, and both of them started fine.
There were no stats in XO-Lite either, I was doing the second and third hosts from XO-Lite to see if XO was getting mad. The second and third rebooted without issue and something I'll look into with the next update, the delay on master could have been the VMs trying to auto start where I remembered to turn that off for the other two hosts.
Off topic, XO-Lite is really moving along. I have screen captures for setting up a system from install using XO-Lite. This gets me up to installing Debian for an XO from sources VM to go farther. Keep up the good work!
Not going to be able to test this, my little mini-lab is having a very hard time with passthrough, to the point where the host won't boot. Tried this on my backup host (for backup DR testing) and finally got it back after the last couple of hours fooling with turning passthrough on and then back off. Sorry.
I'm guessing it is something to do with the T1000. I've had so flakyness with them in our workstations. You don't have an older K620 or something do you? I'm also wondering if this might be a case for an Intel ARC GPU, they weren't out when I did my last workstation refresh or I'd probably be using them with Creative Cloud applications.
Also can you try change the Management Agent Service from auto-start to delayed auto-start? Server 2025 has been a bit odd for me for a while, and that was back running on Intel hosts (though they are old CPUs).
I'll see if I can get a VM up this afternoon, but I'm on AMD with the iGPU so not sure it even supports the acceleration that you need out of the T1000 for the camera recorders. I need to go through and configure each host to pass through the GPU, audio, and maybe some USB and then reboot. But if it works, it might make a nice Handbrake transcoding VM for me, dump files in, get back to work while it does it's thing.
Which version of Server are you running? UEFI, vTPM, Secureboot?
I don't have an Windows Server on my lab right now, but I can give it a quick check and see. Not sure I can pass through the iGPU in my lab though, and production doesn't have a GPU (real servers with ASpeed BMC).
For some reason, my hosts stop displaying the stats after about 2 days. I did a rolling pool reboot 2 days ago, then restarted the toolstack on each of 3 hosts (my pool) to restore the stats. As of right now, only 1 of the hosts has the stats working still.
The fourth identical "server" of the same hardware is just running the regular release cycle, it still has stats after many days/weeks being up, so not hardware related.
I also wanted to ask, how often updates come out for this "branch" and is there anything special we need to do to get them installed?
Alma must have dropped everything to push this out. I wonder what Oracle is doing, guessing they were hit by this too. I'd guess Rocky has this out pretty fast, they know it is important.
This may sound stupid, but here goes...
Does Rocky need to update to .50 before it can update to .51?
I'd guess no, but I've been away from RHEL based stuff since the IBM rug pull. Only coming back because I may need it in the future as I jockey around trying to improve my paycheck.
I just updated an Alma 8 and it has the .51 kernel now.
A very minor thing I noticed in XO from sources today, there is no logo next to an Alma8 VM I installed, yet the Debian VM shows their logo.
This is of course, extremely low on the list of issues, just thought I would point it out. I haven't tried Alma 9 yet, my plan was to get this running and then ELevate it up to 9 (or maybe 10 if it is out by then). Kind of a long term testing/planning for GLPI that I haven't really started on yet and may abandon for Netbox as the function I lack can be done by both (inventory).
Management agent 8.4.0-1 installed.
Yes a trivial thing, but fun to have.
Sad that even this documentation is locked behind a Redhat account, I can only read part of the problem description. Not going to make an account because it really doesn't affect me right now.
I'm running the same guest tools.
Could it be a processor related issue? I'm running AMD v1756b in my lab, haven't had time to try in production that is Intel Silver.
Strange that my fresh Alma 8.10 is still working after updates, makes me think k there is more to this than just the kernel.
Restarting the tool stack fixed it. Thanks!
I backed up another Windows Server 2022 that had a lot of free space, setting no compression is the workaround right now. I'll have to get both of these shrunk down to reasonable and see if compression starts working. That's and after lunch task for the second "big" VM. I'll report back after performing the shrink steps on the one I can reboot today.
I agree with the working theory way up at the top... The process is still going, counting each empty "block" and "compressing" it, but with no data moving for over 5 minutes, it errors out. And 120-150GB worth of empty space in a Windows VM is enough to hit that timer.
Why the Linux machines don't do this? Might be because all of mine are done in less than 10 minutes total, which doesn't leave a lot of time where that timer can run. 3 of my linux with "large" disk went just fine, a couple only took 3 minutes to compress and copy to the remote share.
[edit] After shrinking and moving the partitions, I'm finding that XO is not allowed to decrease the size of a "disk", so I might just be stuck with no compression on these two VMs.
I think my original mini-lab did this, I had mistakenly joined these hosts to the big lab pool, found out is was wrong and detached them to make a mini-lab pool. There were some oddities when I did this, but I just worked past them and created their own pool and did my warm migrations. Wish I had taken better notes of this when I did it.
I wiped and rebuilt my mini-lab now, so no going back.
I can't do a lot with testing, but sometime I find the odd things that other don't look at. I have been staring at the stats pages for the last few days trying to work out some backup issues, so it was one of those things I just normally looked at.
Also in my lab, with the little tiny processors, I like to keep track of what's going on, on think that lead me to nuke the lab and start over, the old VMs were just not right and might have been down to over provisioned CPU from the old big lab migration.
No surprise, but those stats are also flat line in XO-Lite. I've been using XO-Lite a bit more, I think it's going to be good when you get done building it.
OK,
I have my three hosts in my lab updated, and while the process went smoothly, I'm missing some things.
You can see that the stats for three things are flatline, and that's impossible. This is after a rolling reboot to make sure everything is back in sync.
These hosts are HP T740 thinclients with AMD v1756b processor and x520 network card, and were working properly before going to testing.
The VMs seem to be fine, I only have 2 of them right now. I just migrated one of the VMs to see if anything would change, but stats are still flatline with no data except for RAM which did show the migration.
Stats for each VM seem to show flatline for CPU and Network, but disk is showing some activity (NFS share).
Not sure what else to check at the moment.
How many of these that are failing have been upgraded from a previous version? Could it be something left over from EL7 or early EL8?
My Alma 8.10 base install is still running fine, did a yum update to apply a few more things and reboot and still working with the same kernel version above. But again, this was a clean fresh install, not something that's been running for a while.