@stormi Sorry for the delay in testing. This looks to be fixed now. Thanks!
Best posts made by onyxfire
-
RE: New guest tools ISO for Linux and FreeBSD. Can you help with the tests?
Latest posts made by onyxfire
-
RE: Guest UEFI Secure Boot on XCP-ng
@stormi Do we have any timing or plans on getting the XCP guest drivers signed properly? This would be essential to ever being able to break fully away from citrix tools. Is there another thread tracking that progress and technical roadblocks?
-
RE: New guest tools ISO for Linux and FreeBSD. Can you help with the tests?
@stormi Sorry for the delay in testing. This looks to be fixed now. Thanks!
-
RE: New guest tools ISO for Linux and FreeBSD. Can you help with the tests?
Also testing Rocky Linux with test tools provided the following results:
-
Shutdown: OK
-
Startup: OK
-
Live Migration: OK
-
-
RE: New guest tools ISO for Linux and FreeBSD. Can you help with the tests?
Just found this thread and tested the updates on the latest updated XCP-ng. They install fine on the Rocky Linux 8.4 GA release but there is a minor issue in the logs when you start the xe daemon:
Started LSB: @BRAND_GUEST@ daemon providing host integration services.
Looks like the branding isn't updated in your RPM.
-
RE: xe-linux-distribution
@olivierlambert Any idea when this will be pulled in to XCP-ng installed tools ISO? Just curious when you will pull in as the version included in XCP-ng still doesn't recognize Rocky Linux though the referenced PR was merged beginning of last month. I am not sure if you can pull that update in or if you are going to wait for them to release another minor release before something like that.
Rocky Linux 8.4 just went GA and I am sure many are ready to upgrade their CentOS 7/8 servers to Rocky Linux 8.4 but the linux agent won't start/install on Rocky Linux.
Thanks for any timeline/info you can share on this.
-
RE: XCP-ng Center 8.0.1: Switch from MBps to MBit/s for Networks Graphs
@borzel In my humble opinion, I would say no because then you are deviating from industry standard naming. The reason for standards is so that everyone will know what you are talking about as long as you follow the standard.
Lowercase b always means bit and uppercase B always means Byte. Please do not change this. It is trivial to learn the standard. It is less than trivial when people start making up their own abbreviations for things (though admittedly this one isn't rocket science to figure out).