Re: [Qemu-devel] Re: Network bridging without adding bridge with brctl, possible?

[Jan Kiszka <jan.kiszka@web.de>]

[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]

On 2011-02-20 11:19, Gerhard Wiesinger wrote:
> On Sun, 20 Feb 2011, Jan Kiszka wrote:
> 
>> On 2011-02-19 20:32, Gerhard Wiesinger wrote:
>>> Any other suggestions to achieve this?
>>
>> http://virt.kernelnewbies.org/MacVTap
>>
>> Enabling host<->guest communication this way is still a bit unhandy
>> IMHO. You need a fairly recent iproute2 version, then set up macvtap
>> like this
>>
>>    ip link add link eth1 name macvtap0 type macvtap mode bridge
>>
>> And you additionally seem to need a separate macvlan device attached to
>> that bridge, configured to the IP of the host.
>>
>>    ip link add link eth1 name macvlan0 type macvlan mode bridge
>>    ifconfig macvlan0 ...
>>
>> Not sure if this is by design or due to internals of the networking
>> stack, but it looks unintuitive from user perspective. Maybe Arnd can
>> shed a light on this.
> 
> Thnx Jan. That's exactly I'm looking for.
> 
> Is it possible to use then a legacy type network card for "old" guests?
> 
> e.g. ne2k_pci, i82551, i82557b, i82559er, rtl8139, e1000, pcnet
> and also virtio, virtio-net-pci

For sure.

> 
>> Of course, you could also simply offload all that setup to libvirt.
> 
> http://wiki.libvirt.org/page/Networking
> But that still needs a bridge on ethernet level and break up the
> existing interface, right?

http://libvirt.org/formatdomain.html#elementsNICSDirect

But it looks like it doesn't handle the host-guest setup I described,
and bridging is supposed to be done the classic way.

> 
> BTW: From: http://virt.kernelnewbies.org/MacVTap
> As of QEMU 0.12:
> qemu -net nic,model=virtio,addr=1a:46:0b:ca:bc:7b -net tap,fd=3
> 3<>/dev/tap11
> Is there a newer Syntax with tap interfaces possible (QEMU GIT) without
> bash redirects?

Nope. Normally, the fd is passed in by the management tool. So the
existing interface was sufficient.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]