why has dnsmasq started running and taking up 53 so that my unbound can't start

Arch up to date. Through QEMU manager I had recently created a NAT network mapped to my wireless device. The plan is to use the wireless for the VM and the ethernet for the host. Before that the VM and the host unbound were okay. No other system changes. Now, after system reboot, unbound fails to start, complaining that it can't get port 53. Through lsof I see that dnsmasq has taken 53. This happens even though I have the virtual networks to NOT start up on boot. I don't want to change unbound's port because that will require re-configuring its clients. Why is dnsmasq starting? What is the simplest least impactful configuration change?