Arch Linux User Repository

I was able to compile from source the newer version from https://github.com/xcp-ng/xe-guest-utilities using go 1.22.2.

Nice.

I'm assuming I need your ip-interfaces.patch however do I need the go1.16.patch?

The go1.16 patch has been accepted upstream, so you probably dont need that anymore. (https://github.com/xenserver/xe-guest-utilities/pull/104)

The ip-interfaces path i'm not sure about, but looking at the code it seems that enX(\d) is accepted now by default as well.

So you probably don't need any of the patches anymore.

If you want, you could also update this package, i haven't been using xcp-ng in a while

If you have any furter questions, feel free to ask

Can you give me some tips how to write PKG build for newer version of the xe-guest-utilities. I was able to compile from source the newer version from https://github.com/xcp-ng/xe-guest-utilities using go 1.22.2. I'm assuming I need your ip-interfaces.patch however do I need the go1.16.patch?

I'll get the following error:

go: golang.org/x/sys@v0.0.0-20210414055047-fe65e336abe0: Get "https://proxy.golang.org/golang.org/x/sys/@v/v0.0.0-20210414055047-fe65e336abe0.mod": dial tcp: lookup proxy.golang.org on [::1]:53: read udp [::1]:56453->[::1]:53: read: connection refused
==> ERROR: A failure occurred in build().`

I am not behind a proxy and accessing https://proxy.golang.org works with curl.

Thank you very much. Worked flawlessly!

When started, systemd service xe-linux-distribution.service reports:

CollectOS error: &fs.PathError{Op:"open", Path:"/var/cache/xe-linux-distribution", Err:0x2}

Workaround:

# mkdir /var/cache/xe-linux-distribution
# systemctl restart xe-linux-distribution

Please update PKGBUILD to create the empty directory /var/cache/xe-linux-distribution during installation of this package.

Thank you for reporting this. I have added the patch. That explains why my vms didnt properly show their ip.

@4censord my bad, here is the PR https://github.com/xenserver/xe-guest-utilities/pull/120

The bug is that guestmetric is case sensitive, and with arch on xcp-ng, your interfaces are enX, not enx. At the end, the network information are not send back to xcp-ng, which means no ip inside the xsconsole or xoa.

Okay, i will add that.

May I recommend either linking to the Issue/PR upstream, or maybe describing the bug this fixes for the future?

Hey,

this bug has been reported upstream, but it takes a log time for them to fix (PR already merged). So I was thinking that I would share it here:

diff --unified --recursive --text --color package.orig/guestmetric/guestmetric_linux.go package.new/guestmetric/guestmetric_linux.go
--- package.orig/guestmetric/guestmetric_linux.go   2022-04-12 22:03:17.974041006 +0400
+++ package.new/guestmetric/guestmetric_linux.go    2022-04-12 22:03:43.377333671 +0400
@@ -182,7 +182,7 @@
    current := make(GuestMetric, 0)

    var paths []string
-   vifNamePrefixList := [...]string{"eth", "eno", "ens", "emp", "enx"}
+   vifNamePrefixList := [...]string{"eth", "eno", "ens", "emp", "enx", "enX"}
    for _, prefix := range vifNamePrefixList {
        prefixPaths, err := filepath.Glob(fmt.Sprintf("/sys/class/net/%s*", prefix))
        if err != nil {

I have only used the guest tools for basic features, reading RAM and ip adresses mostly.
I have no experience with the container managemant feature, so i can't tell if/how it should work.
I would recomend to try:

• installing the xentools directly from the guest-tools iso,
• installing directly from upstream,
• and trying some other distribution, just to make sure the container thing works at all.

I it still doesn't work you should open an issue upstream