Hello,
On Mon, 26 Nov 2007 12:13:34 +0530, Sadique Puthen wrote:
> dnsmasq does not listen on your physical network sockets. It only
> listens on "virbr0" virtual interface that can NAT network connections
> from guests to Dom0. So anything except dom0 and guests can't access the
> service.
Good point - I hadn't noticed that it was listening on the specialized
xen-interface only.
Still, I want to stop the service if it isn't needed.
>> - Can I somehow prevent xen from starting dnsmasq, now that
>> a "chkconfig --level 345 dnsmasq off" doesn't help?
>>
>>
> Check /etc/libvirt/qemu/networks/autostart
I don't use NAT'ed xen geusts, so I changed
<ip ...>
<dhcp>
<range .../>
</dhcp>
</ip>
to simply:
<ip/>
And now dnsmasq isn't running any longer after reboot. The guests still
work fine. But is it too drastic? In other words: Is there potential
trouble related to an empty <ip/> element in the qemu/networks/default.xml
--
Regards,
Troels Arvin <[EMAIL PROTECTED]>
http://troels.arvin.dk/
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
