New Rust Xen guest tools
-
@Davidj-0 unfortunately not enabling daemons at first install is the standard behavior in RPM world. I already had a look at changing this for one package, and it turns out to be messy with unforeseen impact, so I gave up with the excuse that admins of RPM-based distros already have to live with this idiosyncrasy anyway.
I added this in install instructions in the Gitlab release notes already. -
IIRC you can just enable and start the service in a
%post
scriptlet. It's does not conform to Fedora's and RedHat policy for packages included in their repositories, but here the repository is external and we know for sure that the vast majority of users just wants it to be enabled. -
@stormi that would need to be done only if not upgrading then, or it would interfere with local admin's choice.
-
@yann This is a common condition in scriptlets, yes.
-
@Davidj-0 @Tristis-Oris I started a pull request for this. Seems to work for simple cases, but if you want to shake it in real life that can help!
[shortcut to test RPM] -
- install over old version. Nothing changed at XO ( waited for about 1-2 min), but after vm reboot it show new tools version.
- install over old version, restart tools service
systemctl restart xen-guest-agent.service
- got new version at XO. - removed old tools first
dnf remove xen-guest-agent
, reboot host, then install new one.
rpm -i xen-guest-agent* Removed "/etc/systemd/system/multi-user.target.wants/xen-guest-agent.service". Created symlink /etc/systemd/system/multi-user.target.wants/xen-guest-agent.service → /usr/lib/systemd/system/xen-guest-agent.service.
So it works good. Maybe also add service reload in case of update?
-
Hi @Tristis-Oris,
I have the same installation problem as you.
When I try to install, it gives me the same error message.
How did you solve this?error: lsetfilecon: (-1 ad2886979f8f9a9f9b404a9e9b3f2018781ceb;65bcebdc, system_u:object_r:lib_t:s0) No such file or directory error: Plugin selinux: hook fsm_file_prepare failed Error: Transaction failed
-
@Theo main point to avoid such issues without tuning the OS.
easy way - disable selinux. -
@Tristis-Oris said in New Rust Xen guest tools:
@Theo main point to avoid such issues without tuning the OS.
easy way - disable selinux.I'd like to point out, while this is useful to test the tools, it is not recommended to do that on a production VM - sorry if that sound obvious, but better safe than sorry
-
@yann I can't recall, but does it kick out a notice about that like BSD does? If not, is that a possible addition?
-
@yann said in New Rust Xen guest tools:
@Theo main point to avoid such issues without tuning the OS. easy way - disable selinux.
I'd like to point out, while this is useful to test the tools, it is not recommended to do that on a production VM - sorry if that sound obvious, but better safe than sorry
Yes, I agree, disabling SELinux should not be the preferred solution.
It looks more like a bug in the RPM package. -
But weird that i succesfully install tools on same distro before.
-
@Tristis-Oris said in New Rust Xen guest tools:
But weird that i succesfully install tools on same distro before.
What version of the RPM package do you have installed?
Is it only xen-guest-agent package that cannot be installed? -
Same with old one aaaand with
dnf update
. Looks i found the cause.https://support.oracle.com/knowledge/Oracle Linux and Virtualization/3002168_1.html
my first tests was at Feb 2-4, and next day it was broken))))
-
@Tristis-Oris said in New Rust Xen guest tools:
Same with old one aaaand with
dnf update
. Looks i found the cause.https://support.oracle.com/knowledge/Oracle Linux and Virtualization/3002168_1.html
my first tests was at Feb 2-4, and next day it was broken))))
Yes, that's probably it.
Some more discussion on the topic:https://community.oracle.com/mosc/discussion/4558317/oel-8-8-8-9-dnf-upgrade-error-plugin-selinux-hook-fsm-file-prepare-failed-since-this-mornig
https://unix.stackexchange.com/questions/767829/cant-run-rpm-due-to-calling-hook-fsm-file-prepare-in-selinux-plugin-on-oracle-l -
@CJ it looks like people really want to get it auto-enabled (which makes sense) so if we don't discover major problems we'll just let it auto-enable on first install. But yes, if it turns out it is better to leave it disabled but default a notice makes sense.
-
Problem with broken package on rhel8-9 looks resolved now. Done multiple tests.
-
Hello,
Recently we test the new Rust Xen Guest Tools and it seems to work well
But we have a doubt about is they are in beta or actually they are in the "final" version, so we can use in production scenario.
Thank you!
-
Frankly, I'm already using them in production without any issue. Due to the nature of what they do, I don't think the risk is big
-
@usuari While we're pretty happy with how they work with XCP-ng as @olivierlambert says, our goal is to have those tools more generally useful for the whole Xen ecosystem, and there will likely be changes related to this. For example, it might be that a configuration becomes necessary to get the more general version to behave like they do today - naturally we would provide such a file, but it could require the installation of an additional package when that is done. (disclaimer: this is the outcome I have in mind, which does not mean it is precisely what's going to happen )