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

jr-m4

I believe I have a reproducible method to make it expand.
The trick aparently is Live migrating the VM.

After reboot

Pre live migration:

Post live migration:

TeddyAstie

Do you have multiple guests agents in the VM (e.g Citrix and XCP-ng ones) that may step on each other for this IP ?

jr-m4

@TeddyAstie

I do not have Citrix ones. This VM was pretty much freshly installed to test Windows2025 on as pure Vates-maintained stack as possible.

Update: Please note my post above. Tha this seems to be triggered by live-migrating the vm

jr-m4

ping @poddingue for visibility as I believe I've found the trigger for IPv6 expanding... Live Migrations

poddingue

Thanks for the ping and for narrowing it down; that live-migration repro is a really useful signal.
I don't know enough about how the guest tools report IPs back through XAPI to say where the canonicalisation should happen, but it sounds like something @Team-Hypervisor-Kernel might want to look at since the trigger is on the agent side after migration.
If it turns out to be reproducible on another Windows guest version (2022, 2019), that might help narrow it further; no pressure though, you've already done the hard part.

jr-m4

@poddingue

I have done some more testing.
Windows Server 2022 is also affected. 9.1.145-77

I also tried the latest WindowsPV drivers from Vates, on Windows Server 2025. 9.1.200-0. And the "problem" still persists.

It is a very low impact and low importance "problem". Since it is afaik purely costmetical.

olivierlambert

Still, something to fix

dinhngtu

I've taken a quick look, looks like it'll be solved as part of the Windows guest agent overhaul, so please look forward to that.

jr-m4

@dinhngtu said:

I've taken a quick look, looks like it'll be solved as part of the Windows guest agent overhaul, so please look forward to that.

Thanks for the info. I will be looking forward to that, indeed.

jr-m4

I just did a quick test to check. And it does indeed seem that this (small) issue has now been resolved.
Tested on Windows Server 25, Management agent 9.2.385-0.

Cheers!