<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 08/27/2015 08:56 PM, Spanky Horawitz
wrote:<br>
</div>
<blockquote cite="mid:1440723418.10707.43.camel@psdchristensen"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="GENERATOR" content="GtkHTML/4.6.6">
Thanks again!<br>
<br>
Can you tell me the difference in setting things up that way as
opposed to updating (in Ubuntu) /etc/network/interfaces and adding
physical br(idge) interfaces? On my other test box, I setup
networks the way you describe from <a moz-do-not-send="true"
href="https://help.ubuntu.com/community/KVM/Networking">https://help.ubuntu.com/community/KVM/Networking</a><br>
</blockquote>
<br>
The main difference between libvirt's bridges and a bridge setup as
described on that page is that bridges created by libvirt will never
have a physical ethernet device directly attached, so any
communication to the outside from interfaces connected to a
libvirt-created bridge will need to be routed at L3 by an IP stack
on "something" connected directly to the bridge; that could be
another guest which has multiple interfaces (as you're setting up)
or it could be the host itself (when you configure an IP address on
a bridge, that effectively plugs the host's IP stack into a port on
the bridge).<br>
<br>
It's possible to configure bridge interfaces with no directly
attached ethernet outside the scope of libvirt in
/etc/network/interfaces - just skip the "bridge_ports" line. The
effect is the same, just depends on where you want your config.<br>
<br>
<br>
<blockquote cite="mid:1440723418.10707.43.camel@psdchristensen"
type="cite">
<br>
-----Original Message-----<br>
<b>From</b>: Laine Stump <<a moz-do-not-send="true"
href="mailto:Laine%20Stump%20%3claine@laine.org%3e">laine@laine.org</a>><br>
<b>To</b>: <a moz-do-not-send="true"
href="mailto:libvirt-users@redhat.com">libvirt-users@redhat.com</a><br>
<b>Cc</b>: <a moz-do-not-send="true"
href="mailto:shorawitz@gmail.com">shorawitz@gmail.com</a><br>
<b>Subject</b>: Re: [libvirt-users] Isolated networks &&
test lab<br>
<b>Date</b>: Thu, 27 Aug 2015 20:52:04 -0400<br>
<br>
On 08/27/2015 08:25 PM, Spanky Horawitz wrote:<br>
<br>
<blockquote type="CITE"> Sorry, just realized there is a VMmanager
app too (free version seem to only have support for Debian 7
though.) I am using the Virtual Machine Manager GUI
(virt-manager.)<br>
</blockquote>
<br>
virt-manager is what I'm talking about (don't know what you mean
by "VMmanager"). Probably the dialogs have changed - mine is
v1.2.1. 0.9.5 sounds a bit old, you should see if there is a
backport of a newer version somewhere for whatever distro you're
running.<br>
<br>
Alternately, it is dirt simple to create a new network that has no
IP address associated with it. Just do this:<br>
<br>
1) create a file with these contents:<br>
<br>
<network><br>
<name>mynetname</name><br>
</network><br>
<br>
2) "virsh net-define filename.xml" (where filename.xml is the file
containing the above XML)<br>
<br>
3) "virsh net-autostart mynetname; virsh net-start mynetname"<br>
<br>
(all these run as root)<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
libvirt-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:libvirt-users@redhat.com">libvirt-users@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/libvirt-users">https://www.redhat.com/mailman/listinfo/libvirt-users</a></pre>
</blockquote>
<br>
</body>
</html>