On Fri, Jul 11, 2008 at 01:41:43PM -0000, Soren Hansen wrote: > Will never ever happen. :) By design. Allowing you to pass arbitrary > options to kvm, iptables and/or dnsmasq would result in an unknown and > unmanagable environment. > > If you really, truly want this, you should replace dnsmasq with a > wrapper that uses your configuration file. > > > I'm curious what sort of options you want to add, though? Should we extend > the network description xml to be able to describe it?
I wanted to be able to set a domain name for my guests on my vm network so that dnsmasq can properly resolve dns queries from the host. Another option would be to enable the tftp server to do pxe booting on a virtual network. I've looked into doing that by extending the network description xml, but it required too much work. That's why I thought about starting dnsmasq with an extra configuration file. Being able to specify an extra configuration file would help in customizing the network configuration. But as you pointed out it can lead to an unknown/unmanagable environment. I would consider this as an advanced feature that would help customize the dnsmasq setup without having to change the network description xml. -- Mathias Gug Ubuntu Developer http://www.ubuntu.com -- add option to start dnsmasq with a custom configuration file https://bugs.launchpad.net/bugs/247583 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
