Package Base Details: xe-guest-utilities-xcp-ng

Git Clone URL: https://aur.archlinux.org/xe-guest-utilities-xcp-ng.git (read-only, click to copy)
Submitter: 4censord
Maintainer: 4censord
Last Packager: 4censord
Votes: 2
Popularity: 0.000001
First Submitted: 2021-01-14 15:51 (UTC)
Last Updated: 2022-10-26 13:13 (UTC)

Latest Comments

1 2 Next › Last »

n-buck commented on 2023-10-06 07:13 (UTC) (edited on 2023-10-06 07:21 (UTC) by n-buck)

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.

Rockyboa commented on 2022-11-02 12:45 (UTC)

Thank you very much. Worked flawlessly!

Zepman commented on 2022-10-26 06:03 (UTC) (edited on 2022-10-26 06:05 (UTC) by Zepman)

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.

4censord commented on 2022-04-12 20:04 (UTC)

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

wowi42 commented on 2022-04-12 19:14 (UTC)

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

4censord commented on 2022-04-12 19:10 (UTC)

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?

wowi42 commented on 2022-04-12 18:07 (UTC) (edited on 2022-04-12 18:07 (UTC) by wowi42)

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 {

4censord commented on 2021-04-15 09:39 (UTC) (edited on 2021-04-15 09:41 (UTC) by 4censord)

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

kaptain commented on 2021-04-15 03:07 (UTC)

Hello

The xscontainer-prepare-vm is unable to to refresh/read the state of the Arch Linux VM :

xscontainer-prepare-vm -v f4a038a8-e258-8649-b9db-91dec3ebe368 -u ron Would you like to push a pool-specific public SSH key into the ~/.ssh/authorized_keys file of the specified VM and therefore authorize hosts in the pool to interact with the containers inside the VM? Answer y/n: y

Attempting to push the public xscontainer key to ron@192.168.50.22. ron@192.168.50.22's password: Success.

Attempting to refresh the state of the VM Failure diagnosis: Unable to determine cause of failure. Do you wish to retry? Answer y/n: y

The xe-guest-utilities-xcp-ng installed successfully.

I do not know if it is a issue with Arch Linux not being fully supported to manage Docker containers, or if I am missing packages or need to edit files to get things working.

Thanks

kaptain commented on 2021-04-14 11:54 (UTC)

Thank you very much. It did install this time without any problems.