<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">(in before Eric for this :-) Please
don't top-post in responses on this list (or most other technical
lists). Posting your responses in the context of the previous
message makes it much easier for followups that want to respond to
points from several messages at once (and also makes it easier to
understand the discussion by reading just one of those messages).<br>
<br>
On 04/24/2015 11:08 AM, <a class="moz-txt-link-abbreviated" href="mailto:mimicafe@gmail.com">mimicafe@gmail.com</a> wrote:<br>
</div>
<blockquote
cite="mid:CAOqrB6beR1eMvg00V=S3f9v+mXsW1iDYsDFfBTySS5D7Cte+3Q@mail.gmail.com"
type="cite">
<div dir="ltr">HI Michal
<div><br>
</div>
<div><br>
</div>
<div>Thank you for explaining. I have this situation in a number
of production servers where we would always use static IPs for
the host and VMs. In such case we have no requirement for
NATed network in the future. And we we ever do, we can rely on
a DHCP server within the LAN to provide IPs to the VMs.</div>
<div><br>
</div>
<div>I'll look to remove both <span
style="font-size:12.8000001907349px"> </span><span
style="font-size:12.8000001907349px">libivirt-daemon-driver-network, </span><span
style="font-size:12.8000001907349px">libvirt-daemon-driver-network
and dnsmasq.</span></div>
</div>
</blockquote>
<br>
You can't remove libvirt-daemon-driver-network, as
libvirt-daemon-driver-qemu is dependent on it (for very good
reasons). If you try to do this, you will almost surely end up with
a crashing libvirtd.<br>
<br>
<br>
<blockquote
cite="mid:CAOqrB6beR1eMvg00V=S3f9v+mXsW1iDYsDFfBTySS5D7Cte+3Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><span style="font-size:12.8000001907349px"><br>
</span></div>
<div><span style="font-size:12.8000001907349px">Any further
thought from your side?</span></div>
</div>
</blockquote>
<br>
<br>
<blockquote
cite="mid:CAOqrB6beR1eMvg00V=S3f9v+mXsW1iDYsDFfBTySS5D7Cte+3Q@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On 24 April 2015 at 13:12, Michal
Privoznik <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mprivozn@redhat.com" target="_blank">mprivozn@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On <a moz-do-not-send="true"
href="tel:24.04.2015%2012" value="+12404201512">24.04.2015
12</a>:45, <a moz-do-not-send="true"
href="mailto:mimicafe@gmail.com">mimicafe@gmail.com</a>
wrote:<br>
> I am running KVM virtualization with libvirtd
(libvirt) 0.10.2 in bridged<br>
> network mode, however I still have the default
virtual network<br>
> bridge/interfaces and dnsmasq on the host. What I am
trying to understand<br>
</span>> is whether or not dnsmasq and the virtual
network (*virbr0, Vnet0 and Vnet1*)<br>
<span class="">> still play any role. If not, can I
remove them?<br>
</span></blockquote>
</div>
</div>
</blockquote>
<br>
You are mixing together a couple differnet (but related) things.
virbr0 is a bridge device created for libvirt's "default" virtual
network, and the dnsmasq instance that is running is also run by
libvirt for that network. However, the vnet0 and vnet1 devices are
tap devices; one of these is created for each domain interface,
whether you use libvirt's network or you connect to a host bridge
that you've configured yourself - you can't eliminate those devices.<br>
<br>
<blockquote
cite="mid:CAOqrB6beR1eMvg00V=S3f9v+mXsW1iDYsDFfBTySS5D7Cte+3Q@mail.gmail.com"
type="cite">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">
<br>
</span>Yes, you can safely remove
libvirt-daemon-config-network package. It<br>
should disable the default network.</blockquote>
</div>
</div>
</blockquote>
<br>
Actually that won't disable any already-installed default network.
You'll need to do this:<br>
<br>
virsh net-destroy default<br>
virsh net-undefine default<br>
<br>
Once you've done this, the virbr0 device will no longer appear, and
dnsmasq will not be run (although the binary will still be present
on the disk).<br>
<br>
<blockquote
cite="mid:CAOqrB6beR1eMvg00V=S3f9v+mXsW1iDYsDFfBTySS5D7Cte+3Q@mail.gmail.com"
type="cite">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> However,
dropping dnsmasq is a bit<br>
harder, since libivirt-daemon-driver-network depends on it.
We can't<br>
know whether you will not someday like a NATed network with
a DHCP<br>
server, even though now you don't. However,<br>
libvirt-daemon-driver-network takes care about all the
network types<br>
known to libvirt, so you can't really drop it (unless
forcibly removing<br>
the package and let the libvirt just deal with it, which I'd
discourage<br>
you from doing anyway).<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
That's not going to work. There are things in the network driver
other than just libvirt's virtual networks, and qemu isn't setup to
deal with the network driver not being present.<br>
<br>
<br>
</body>
</html>