plans to adopt new MacOS 26+ network topos for features like static IP ranges / cross-VM traffic?

[MatthiasWinzeler]

hi folks

first up, many thanks for this great project - being able to spawn modern Mac VMs via CLI saved us countless hours!

Some pain points we experienced (mostly due to the Apple Virtualization framework, not tart itself) are the following two:

• Truly static IPs for VMs: We have some cases where we need to have static IPs for VMs (I think others have asked for that feature as well). Apple's vmnet framework seems to randomly reassign a new IP subnet range to the bridge (sometimes when the last VM on the bridge reboots) - essentially breaking the static IP setup of the VM.
• Cross-VM traffic doesn't seem to be possible (since each VM is placed into its own little network by AVF)

We could work around that (to some degree) by putting the VMs on bridge network, but that breaks topology/static IPs once the user switches the network (i.e. from home office to the corporate office).

I was excited to see WWDC 26 - Session 224 that MacOS 26+ ships more advanced network topo features which would allow to support for example setting a static subnet (and thus, static IPs for VMs) or allow cross-VM traffic.

Have you folks already looked at it? Are you planning to adopt it? For example, lima already started to work to implement network topos (lima-vm/lima#4394), so it seems to slowly find adoption in the virtualization ecosystem :)