Re: [libvirt-users] dnsmasq does not start

On 04/24/2013 03:23 AM, Alexey Kardashevskiy wrote: libvirtd starts an instance of dnsmasq for each virtual network that is started (unless the network has no <ip> elements). Normally, the network named "default" is preinstalled to be an "autostarted" network. Internally this is implemented by making a symbolic link from /etc/libvirt/qemu/networks/autostart/${netname}.xml to /etc/libvirt/qemu/networks/${netname}.xml. I'm guessing that this was never setup when you installed libvirt. You shouldn't set autostart by creating this link yourself, though. Instead, run the following commands to set the default network as autostart and then start it: virsh net-autostart default virsh net-start default The first command makes sure it will be autostarted in the future whenever libvirtd is restarted, and the 2nd starts it manually this one time. (But before you do this, read below - you've done something else wrong when you manually copied the config file into /etc/libvirt, and I have a complete list of the commands you should run to fix *everything*) This line ^^^^ is unnecessary. However, I see that this network is *missing* a <uuid> element. This tells me that you just copied the file into place manually rather than using the approved API for defining a network. See below for the commands to fix everything... So you've modified it to be an isolated network. (you could also have just completely removed the <forward/> element). This means your guests will not be able to reach anything beyond the virtualization host itself. Is that really what you wanted? If not, that line must instead be <forward mode='nat'/> To fix all of your problems, you should do the following: 1) service libvirtd stop 2) mv /etc/libvirt/qemu/networks/default.xml /tmp 3) [edit /tmp/default.xml and remove the <bridge name='.... line ] 4) service libvirtd start 5) virsh net-define /tmp/default.xml 6) virsh net-autostart default 7) virsh net-start default