Once upon a time, Neal Becker <ndbecker2(a)gmail.com> said:
Clearly has something to do with libvirt, probably I did some
experiment a
long time back that required it. But just removing libvirt-daemon is not an
option, that would remove a lot of stuff.
Libvirt by default sets up a private local network, NATted towards your
Internet connection, with a local dnsmasq for a proxy resolver. If you
aren't using that network, you can just disable it and set it to not
auto-start:
# virsh net-autostart default --disable
# virsh net-destroy default
Otherwise, you can make dnsmasq only listen on certain interfaces, so
you could set your instance to not listen on the private network (and
IIRC libvirt configures its instance to only listen on that network),
and that should work. libvirt configures its instance for separate PID
files and such, so that part doesn't conflict with a "regular" instance.
--
Chris Adams <linux(a)cmadams.net>