New Rust Xen guest tools

Theo

@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.

Tristis Oris

But weird that i succesfully install tools on same distro before.

Theo

@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?

Tristis Oris

@Theo @yann

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))))

Theo

@Tristis-Oris said in New Rust Xen guest tools:

@Theo @yann

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

yann

@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.

Tristis Oris

Problem with broken package on rhel8-9 looks resolved now. Done multiple tests.

usuari

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!

olivierlambert

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

yann

@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 )

usuari

Hello,

Than you for your response!

Now we are considering to put the guest-tools in our repository (mirror) in order to get the templates automatically updated, but we couldn't find the right form to do it.

Currently we have a working and operational mirror, but when we put this:

deb [trusted=yes] https://gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64/ release/

Fails because couldn't find indexes:

Processing indexes: [PPPPPPPPPPPPPPPPapt-mirror: can't open index gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64///release//Packages in process_index at /usr/bin/apt-mirror line 800.
P]

We can use rsync or gitlab, but we need some indication of what we need to use.

Regards,

Houbsi

@usuari said in New Rust Xen guest tools:

Now we are considering to put the guest-tools in our repository (mirror) in order to get the templates automatically updated, but we couldn't find the right form to do it.

Currently we have a working and operational mirror, but when we put this:
deb [trusted=yes] https://gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64/ release/
Fails because couldn't find indexes:
Processing indexes: [PPPPPPPPPPPPPPPPapt-mirror: can't open index gitlab.com/api/v4/projects/xen-project%252Fxen-guest-agent/packages/generic/deb-amd64///release//Packages in process_index at /usr/bin/apt-mirror line 800.
P]

Please see current issue on the gitlab repository.
https://gitlab.com/xen-project/xen-guest-agent/-/issues/18

yann

@Houbsi ~~not sure what indeed happened~~ I had messed up and used links to the CI run on commit instead of that of the tag. I had to update the links to point to new job ids. Thanks for the notice!

yann

@usuari what distro/release are you using?

usuari

@yann Hello, our apt-mirror is installed on Debian 11, but the purpose is to install the guest-tools on VMs with, at least, Debian 12 OS. We want to allow each of these VMs to be able to download the package from our repository instead of having to add the line in the sources.list file of every machine.

This method gives us control if there's a future connection issue between both ends. We will have a copy of the package and won't interrupt our workflow.

Once it works well, we would move on to the other operating systems.

Thanks in advance,

Finallf

I have an ISO that I created myself with all the Drivers and tools that we would possibly need:

With the new Rust tools, can I stop using this ISO?
Any features I might miss?
I'm looking forward to having the new Windows tools.

Thank you very much for this great work.

olivierlambert

Those tools are for Linux and BSD only at the moment.

kevdog

Hey do you have actual instructions on how to compile from source? I trying to work with someone creating an arch linux AUR package and was looking for a little more input.

yann

@kevdog do you have any specific issue not addressed by the build instructions in the README?

Tristis Oris

Tools is working on Ubuntu 24 LTS.
Well it obvious, since nothing is really changed)