On Fri, Nov 19, 2010 at 09:51:33AM -0800, Mark Foster wrote: It's because of this: --- postinstall scriptlet (using /bin/sh): /sbin/ldconfig # We want to install the default network for initial RPM installs # or on the first upgrade from a non-network aware libvirt only. # We check this by looking to see if the daemon is already installed /sbin/chkconfig --list libvirtd 1>/dev/null 2>&1 if [ $? != 0 -a ! -f /etc/libvirt/qemu/networks/default.xml ] then UUID=`/usr/bin/uuidgen` sed -e "s,</name>,</name>\n <uuid>$UUID</uuid>," \ < /usr/share/libvirt/networks/default.xml \ ln -s ../default.xml /etc/libvirt/qemu/networks/autostart/default.xml fi /sbin/chkconfig --add libvirtd --- I put in a request to get it removed. -- James M. Leddy Technical Account Manager Red Hat Inc. work: 212-510-4119 cell: 631-891-8703

On 20/11/2010, at 5:17 AM, James M Leddy wrote: <snip> Hmmm, pretty sure that removing it isn't the best strategy in this instance. :) dnsmasq is kind of essential to the way libvirt uses virtual networks. Having the "default" virtual network not be created, just creates a different set of problems. If a SysAdmin creates some other virtual network on the host (a fairly standard thing to do), then dnsmasq will be started up for that instead, and we're back to the same problem of conflicting with a system install of dnsmasq. The info on the wiki page is part of the right technical solution, as it allows a system wide installation of dnsmasq to not conflict with the libvirt spawned versions. Not sure how to make it more automatic though. We should definitely document it properly in the RHEL 6.x Virtualization Guide though. Something for Laine to include in this content for the VG I reckon. :) Regards and best wishes, Justin Clift