propolis-standalone(?) virtio NIC migration seems funky

I have a Debian 13 VM with

[dev.net]
driver = "pci-virtio-viona"
pci-path = "0.10.0"
vnic = "vnic_prop0"

which works fine on first start - I can reach 192.168.0.1 or other local addresses outside the VM - but I noticed that if I have a ping 192.168.0.1 ongoing while I stop a ./propolis-standalone -s config.toml, resuming that VM with ./propolis-standalone -r <the_snapshot>.tar, the NIC seems to not.. do things anymore. ping is hung, ctrl+c kills it and a new ping yields a fascinating

64 bytes from 192.168.0.7: icmp_seq=1 ttl=64 time=0.000ms

which is curious because that computer is about 0.2ms away via ethernet. I figure either something is funky about migrating NICs in the first place, or specifically in propolis-standalone, or may be something specific about the guest state when I took the snapshot. I'll get the snapshot and image up to catacomb for reference since I probably won't be looking soon.