On Thu, Jun 20, 2024 at 09:18:30AM +0100, Nicholas Hardiman wrote: > On Wed, Jun 19, 2024 at 7:30 PM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote: > > > > On Wed, Jun 19, 2024 at 06:21:29PM -0000, procmem@xxxxxxxxxx wrote: > > > Hi, we are trying to document a way for our users to run libvirt without > ... > > > > The virtual network driver validates existance of dnsmasq at startup, > > but nothing requires you to actually run the virtual network driver, > > if you're intending to do your own thing with network setup. > ... > > If you're using the new modular daemons, then even if installed, the > > virtnetworkd daemon won't get launched unless some guest is configured > > to use it. So if you're intending to setup network bridges yourself, > > virtnetworkd shouldn't run. > > Just checking my understanding here. > I set up a home lab with a load of RHEL software. I already had DHCP > and DNS and didn't want dnsmasq to run. I defined a bridge, told > libvirt about it, and also ran all the modular daemons (I didn't > really understand them and copied the systemctl commands to start > libvirt modular daemons. > > How useful is virtnetworkd in this situation? > Shall I just leave it off? virtnetworkd is primarily for providing the NAT based connectivity. If you're creating standalone bridges for your LAN, then you don't need virtnetworkd. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
