[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] [PATCH 0/5] macvtap support for Qemu/KVM VMs via libvirt

On Mon, 2010-02-15 at 18:24 +0100, Daniel Veillard wrote:
> On Thu, Feb 11, 2010 at 09:48:07AM -0500, Stefan Berger wrote:
> > Hello!
> > 
> >   This is a re-post of previously posted patches following Daniel
> > Berrange's request for changes along with other fixes PLUS a rebase
> > to the latest code where the conn parameter is missing along with
> > changes requested by Daniel Veillard.
>   Okay, I have applied and pushed the 5 patch set, but I had to do a bit
> of surgery. First the detection code in configure was always setting
> WITH_MACVTAP , so of course thsi didn't compile on my system. I also had
> to reorganize the patch order to have each patch compiling. And I also
> had to fix various things popping up when running "make syntax-check"
> after each patch got applied.
>   But basically that's in and with the new version of [3/5] !
>     thanks !
> Daniel

The attached patch adds a macvtap usage example to the Network Interface
chapter of the Libvirt Application Development Guide.

Best regards, 

Gerhard Stenzel, 
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
Index: libvirt-appdev-guide/en-US/Network_Interfaces.xml
--- libvirt-appdev-guide.orig/en-US/Network_Interfaces.xml
+++ libvirt-appdev-guide/en-US/Network_Interfaces.xml
@@ -134,8 +134,25 @@
+    <example>
+      <title>XML definition of a macvtap interface associated with eth1</title>
+      <programlisting>
+<![CDATA[<interface type='direct'>
+  <source dev='eth1' mode='vepa'/>
+    <model type='virtio'/>
+      </programlisting>
+    </example>
+    <para> The above XML indicates that eth1 is the Ethernet interface to link
+    the macvtap device to and communicate to the network. As a consequence,
+    libvirt will create an instance of a macvtap device, assign it the same
+    MAC address as the VM's interface has and open a file descriptor of the
+    associated character device /dev/tap%d and pass it via command line to
+    Qemu/kvm. In the above XML the mode can be chosen as 'vepa', 'private'
+    or 'bridge' and is by default set to 'vepa'(by the driver) if omitted.
+    </para>
   <section id="Application_Development_Guide-Network_Interfaces-Information">
     <title>Retrieving Information About Interfaces</title>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]