[Bug 281256] sysutils/xe-guest-utilities
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 281256] sysutils/xe-guest-utilities"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 281256] sysutils/xe-guest-utilities: Updates to the latest format for xenstore attributes."
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 281256] sysutils/xe-guest-utilities: Updates to the latest format for xenstore attributes."
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 281256] sysutils/xe-guest-utilities: Updates to the latest format for xenstore attributes."
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 281256] sysutils/xe-guest-utilities: Updates to the latest format for xenstore attributes."
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 03 Sep 2024 20:56:06 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281256
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=253309&action=edit
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 shell
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 = 10.1.1.1, whereas the
current code creates an attribute like attr/eth0/ip = 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 = '10.1.1.1 10.1.1.2').
The new code would send one IP per attribute (e.g., attr/vif/0/ipv4/0 =
10.1.1.1, attr/vif/0/ipv4/1 = 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 volunteering
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. :)
Paco
--
You are receiving this mail because:
You are the assignee for the bug.