Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Sep 2024 20:56:06 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 281256] sysutils/xe-guest-utilities
Message-ID:  <bug-281256-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281256

            Bug ID: 281256
           Summary: sysutils/xe-guest-utilities
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: freebsd@filter.paco.to

Created attachment 253309
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D253309&action=
=3Dedit
Patch that will modify xe-update-guest-attrs

Hi there,

I use this port a lot and I've discovered a bug in it. The guest agent for
FreeBSD (a) only reports IPv4 addresses for VMs and doesn't report IPv6
addresses, (b) uses a format in the xenstore that is not the right way to do
things these days. There's a github issue that talks about it
(https://github.com/xapi-project/xen-api/issues/5166). Since it's just a sh=
ell
script, I've got a working fix on my system and I'd like to contribute the
patch upward.

xapi has moved toward a format like attr/vif/0/ipv4/0 =3D 10.1.1.1, whereas=
 the
current code creates an attribute like attr/eth0/ip =3D 10.1.1.1. This patch
fixes that. Also, xenstore expects one IP per attribute. The old code would
send several space-separated IPs (e.g., attr/eth0/ip =3D '10.1.1.1 10.1.1.2=
').
The new code would send one IP per attribute (e.g., attr/vif/0/ipv4/0 =3D
10.1.1.1, attr/vif/0/ipv4/1 =3D 10.1.1.2)

The current port is 6.2.0_3. Since this was a significant change, I bumped =
the
version to 6.3.0 and took away PORTREVISION. Happy to do it differently if =
that
isn't how it's supposed to be.

I see that there is no maintainer for this port. I might consider volunteer=
ing
as maintainer for the port, but let's see if I can contribute a patch
successfully first. Long-time listener, first time contributor, so please be
gentle. :)=20

Paco

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281256-7788>