(Windows) guest IPv6 address doesn't collapse zeroes -> Long IPv6 addresses

jr-m4

I have noticed that on at least Windows Server 2025, using the vates maintaned XCP-ng Windows Gust Tools (v9.1.146.0). XO (same in both 5 & 6) doesn't seem to collapse the IPv6 zeroes as expected. Leading to l00000ng addresses visually.

olivierlambert

So is it a display issue from XO or a problem for the tools? (not sure to get it).

What's the output of xe CLI?

probain

@olivierlambert said:

So is it a display issue from XO or a problem for the tools? (not sure to get it).

What's the output of xe CLI?

This is me (jr-m4) from another (private) account.

Update: Details below are incorrect information.

~~xe Output for another windows 2025 guest, where I'm seeing the same behaviour~~

[16:25 xcp ~]# xe vm-list uuid=3d3b8ba4-09c1-039d-8d58-ec797e7a05c3 params=networks
networks (MRO)    : 0/ip: 192.168.80.234; 0/ipv4/0: 192.168.80.234; 0/ipv6/0: fe80::4496:9d87:690d:ccc7

olivierlambert

Well, I'm not seeing the same behavior here, fe80::4496:9d87:690d:ccc7 is collapsed, unlike in your screenshot

probain

@olivierlambert

I will check back tomorrow when I'm back at that lab-pool. Sorry for taking your time thus far. I will provide more and better info tomorrow

dinhngtu

This seems to be specific to XenServer guest agents?

jr-m4

@olivierlambert said:

Well, I'm not seeing the same behavior here, fe80::4496:9d87:690d:ccc7 is collapsed, unlike in your screenshot

I'm now back with better information from the original pool.

xe vm-list uuid=0513005e-3626-1867-306d-9d5415cd6516 params=networks
networks (MRO)    : 0/ip: 192.168.97.60; 0/ipv4/0: 192.168.97.60; 0/ipv6/0: fe80:0000:0000:0000:a57c:c544:3b03:8910

I will apply latest updates to see if this has any bearing on the matter.

jr-m4

After applying latest updates and commits, to both xcp and XO. The zeroes were still non-collapsed.

However. Rebooting the VM resulted in the zeroes now collapse properly as expected.

I had previously rebooted the VM, so I don't believe that was the solution. But I did not check inbetween pulling latest source, and updating XCP. So I'm unsure which update solved it.

But this then has been resolved.