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.
Also testing Rocky Linux with test tools provided the following results:
Live Migration: OK
@onyxfire Thanks for the report. I'll fix it.
@onyxfire This is now fixed in the latest
xcp-ng-pv-toolspackage in the testing repo. Can you test it?
@stormi Sorry for the delay in testing. This looks to be fixed now. Thanks!
kdm last edited by
I'd like to help: I plan to test this against my Mint Linux 20.1 VM and my openmediavault 5 VM.
Question on "3.3 clean shutdown and reboot working". Any time I shutdown XCp-ng, I normally shutdown each VM first. Since I have guest tools installed, should I be able to simply shut down XCP-ng and rely on it to politely shut down my VMs?
@kdm On a pool with several hosts,
xe host-disable uuid=...then
xe host-shutdown|reboot uuid=...will evacuate the host towards the other hosts of the pool.
On a single host pool, the same commands will attempt a clean shutdown on each VM.
theAeon last edited by theAeon
Seems the SUSE Leap 15 assumes the ability to run SysVinit scripts but as of 15.3 (and tumbleweed) insserv-compat is not included and only systemd scripts are supported. It seems there's already a functional systemd script used on RHEL/Fedora, so I have to imagine this is a simple fix of the install.sh.
EDIT: did some pull reqs-should fix MicroOS identification at the least. Could probably handle Tumbleweed the same way. Tried my hand at some systemd rpms too, but god knows if they work.
Thanks. I'll look at your PRs.
I'm all for adding the ability to extract distro data from
/etc/os-release(see my issue there: https://github.com/xenserver/xe-guest-utilities/issues/108) so I'll likely backport the commit that was contributed upstream. This won't change install.sh (you'd still need to use the
-d) but it should make the service able to start and report OS and version in many additional distros.
For systemd vs sysvinit we need either to create twice more DEBs and RPMs and make install.sh able to decide on which to use depending on the distro, or include both kinds of service files in the packages and use post-install scripts to decide which to enable.
theAeon last edited by theAeon
@stormi Fun fact with that one, I actually merged #108 (pr #116) in with one of my two PRs. No backporting needed, really, it just goes right at the end of the detection logic.
The biggest issue with the systemd file as it stands is that it has directories pointing to the ones used on FCOS rather than /usr/sbin. Split that off in the other PR.
@stormi Hi Stormi, firstly, thx for all good work U guys are doing ! And I have problem, that Im not able to get IP address info from my Rocky Linux 8.4(I have only one NIC conencted eth0).
When Im using newest guest tools from EPEL repo (xe-guest-utilities-latest version 220.127.116.11.el8), those tools cant be started at all.
When Im using newest guest tools from xcp-ng-testing repo(ISO:guest-tools-8.2.0-9.xcpng8.2, tools version 7.20.0-9) as you suggested in some previous post, those tools works, I can even get correct information about OS release, and virtualization state is reporting as "Optimized(version 7.20 installed)", but in network tab, no guest IP address is reported (unknown).
What is strange is that I had RC version of Rocky Linux 8.3 laying around from testing in the past, so I tried to install guest tools from my platform (Citrix 7.0), it is able to report IP address correctly.
That leads to me to think, that somehow Rocky Linux 8.4 isnt fully supported yet ?
If you need more info(logs/screens), please let my know, thx
I realize I haven't announced it on this thread (I thought I had) : the guest tools ISO that was tested in this thread have been released as an update to XCP-ng.
You can still provide feedback, of course, but you don't need to try to pull packages from the testing repository for now.