[Top][All Lists]

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

Re: arm/cadence_gem driver support

From: Kent Dorfman
Subject: Re: arm/cadence_gem driver support
Date: Wed, 25 Sep 2019 11:24:12 -0400

yes.  fully bridged access via a tap is what I was looking for...but I
don't see anything on your command line identifying the guest network
as cadence_gem: no model=cadence_gem.  Is it implicit?

I prefer to run all guests under bridged-tap so that they can be seen
by the host network...I guess this requires the main host nic also be
in promiscuous mode before assigning it to the bridge interface.

On 9/25/19, Alexei Colin <address@hidden> wrote:
> On Wed, Sep 25, 2019 at 08:52:45AM -0400, Kent Dorfman wrote:
>>  This seems to negate the ability to
>> set up the guest in a fully bridged network configuration where it is
>> seen as a generic station on the host network.  I need a fully bridged
>> network connection.
> FWIW, on Xilinx's fork of Qemu (~v2.11.1) I had Cadence Ethernet working
> in tap mode (with Linux guest), where the Qemu guest is recheable via a
> first class tap interface on the host; not sure if that's what you refer
> to as fully bridged or not.
> Create a bridge device on the host and assign it an IP:
> # ip link add br0 type bridge
> # ip link set up dev br0
> # ip addr add dev br0
> Install helper with setuid:
> # install -o root -g root -m 4775 qemu/qemu-bridge-helper
> /usr/local/bin/qemu-bridge-helper
> Grant permission to non-root users:
> # echo "allow br0" > /usr/local/bin/etc/qemu/bridge.conf
>                      ^ prefix set when ./configure was run
> Run qemu (as non-root user should work, given the above setup) with:
> -net nic,vlan=0 -net
> tap,vlan=0,br=br0,helper=/usr/local/bin/qemu-bridge-helper
> Within guest, assign IP address and host should become reacheable:
> # ip addr add dev eth0
> # ping
> Multiple guests all connected to the same bridge worked too.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]