On Mon, May 12, 2014 at 05:12:14PM +0200, John Smith wrote:
On Mon, May 12, 2014 at 12:49 PM, Dan Kenigsberg
<danken(a)redhat.com> wrote:
>
> oVirt only supports bridge-based VM networks, and Linux
> does not allow you to bridge a WiFi nic.
>
Which is why I was looking at the option of using 'macvtap' instead,
which does allow you to use a wifi nic:
http://libvirt.org/formatnetwork.html#examplesDirect
http://www.libvirt.org/formatdomain.html#elementsNICSDirect
A big limitation of the macvtap approach is that it would let you
connect only a single VM to your WiFi. Is that fine by you?
However, my current knowledge (of libvirt, etc.) is too limited to use
those two links to create a working setup for me, so some more
detailed and/or elaborate instructions and/or documentation would be
appreciated.
It seems to involve the manual creation of xml files, and then feeding
those to virsh in order to change the configuration or something ? Is
there a command i can feed vrish to make it dump the current
configuration in xml, so that maybe i can start to use that as a basis
and hack it up to see what happens ?
Yes, defining a libvirt network requires using
virsh net-define <xmlfile>
(you may need to pass the not-so-secret vdsm@ovirt/shibboleth password
to tinker with libvirt, which is better done on non-production setup)
virsh net-dumpxml <net-name>
could show you what's already defined, but I don't expect you to have
interesting networks as of yet.
It may not be easy, but I'd be grateful if you report here on what you
will have accomplished.