<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 1, 2021 at 9:08 AM Cédric Le Goater <<a href="mailto:clg@kaod.org">clg@kaod.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 12/1/21 16:59, Peter Foley wrote:<br>
> The container system we're using (<a href="https://research.google/pubs/pub43438" rel="noreferrer" target="_blank">https://research.google/pubs/pub43438</a> <<a href="https://research.google/pubs/pub43438" rel="noreferrer" target="_blank">https://research.google/pubs/pub43438</a>>) provides a set of FDs connected to a pre-configured TAP device, so I don't think manual bridge configuration is an option.<br>
<br>
ok. That's interesting. You are running QEMU BMC machines (Nuvotons and Aspeed ?)<br>
wrapped in containers. Why BMC machines?<br></blockquote><div><br></div><div>We're running BMC machines to validate BMC firmware.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I guess we could reproduce the setup with a single instance to check issues but<br>
it's a lot of work for an uncommon scenario.<br>
<br>
Thanks,<br>
<br>
C.<br>
<br>
<br>
> <br>
> On Tue, Nov 30, 2021 at 7:54 PM Patrick Venture <<a href="mailto:venture@google.com" target="_blank">venture@google.com</a> <mailto:<a href="mailto:venture@google.com" target="_blank">venture@google.com</a>>> wrote:<br>
> <br>
> <br>
> <br>
> On Mon, Nov 22, 2021 at 12:14 AM Cédric Le Goater <<a href="mailto:clg@kaod.org" target="_blank">clg@kaod.org</a> <mailto:<a href="mailto:clg@kaod.org" target="_blank">clg@kaod.org</a>>> wrote:<br>
> <br>
> Hello,<br>
> <br>
> On 11/22/21 08:20, Joel Stanley wrote:<br>
> > On Thu, 18 Nov 2021 at 20:35, Patrick Venture <<a href="mailto:venture@google.com" target="_blank">venture@google.com</a> <mailto:<a href="mailto:venture@google.com" target="_blank">venture@google.com</a>>> wrote:<br>
> >><br>
> >> Hi;<br>
> >><br>
> >> We're working on wiring up our Qemu BMC via a TAP configuration, and we're not seeing packets inside the Nuvoton NIC itself (a level of debugging we had to enable). We're using the npcm7xx SoC device,<br>
> >><br>
> >> -nic tap,fds=4:5:6:7:8:9:10:11,id=net0,model=npcm7xx-emc,mac=58:cb:52:18:b8:f7<br>
> >><br>
> >> For the networking parameters, where the tap fds are valid. I was curious if any of y'all got qemu networking working for your BMC SoCs, either Aspeed or Nuvoton?<br>
> ><br>
> > I've not tried using the -nic tap option with file descriptors. It's<br>
> > not quite clear what you're trying to do, or what your full setup<br>
> > looks like.<br>
> <br>
> yes. could you explain please ? It is simpler to run with a netdev bridge<br>
> backend :<br>
> <br>
> -net nic,macaddr=C0:FF:EE:00:00:03,netdev=net0 -netdev bridge,id=net0,helper=/usr/libexec/qemu-bridge-helper,br=virbr0<br>
> <br>
> <br>
> Thanks for the replies and help. I don't know why my mail didn't decide this should go in my inbox. Probably user error on my part in the filters.<br>
> <br>
> Peter, would a network bridge simplify life? I imagine the file descriptor approach is because of the framework configuring Qemu, but wanted to ask.<br>
> <br>
> <br>
> <br>
> Thanks,<br>
> <br>
> C.<br>
> <br>
> ><br>
> > I did test it out just now with a manually created tap interface:<br>
> ><br>
> > sudo ip tuntap add test0 mode tap group netdev<br>
> > sudo ip link set test0 up<br>
> > sudo tcpdump -i test0<br>
> ><br>
> > And then when I fired up a qemu instance,<br>
> ><br>
> > qemu-system-arm -nographic -M romulus-bmc -kernel arch/arm/boot/zImage<br>
> > -dtb arch/arm/boot/dts/aspeed-bmc-opp-romulus.dtb -initrd arm.cpio.xz<br>
> > -nic tap,ifname=test0,id=net0<br>
> ><br>
> > I could see packets being decoded by the tcpdump instance (my laptop<br>
> > is 'voyager', qemu came up as fe80::5054:ff:fe12:3456):<br>
> ><br>
> > $ sudo tcpdump -i test0<br>
> > tcpdump: verbose output suppressed, use -v[v]... for full protocol decode<br>
> > listening on test0, link-type EN10MB (Ethernet), snapshot length 262144 bytes<br>
> > 15:10:32.683930 IP6 voyager > ip6-allrouters: ICMP6, router<br>
> > solicitation, length 16<br>
> > 15:10:33.655994 IP6 voyager.mdns > ff02::fb.mdns: 0 [2q] PTR (QM)?<br>
> > _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)<br>
> > 15:10:37.795242 IP6 fe80::5054:ff:fe12:3456 > ip6-allrouters: ICMP6,<br>
> > router solicitation, length 16<br>
> > 15:11:05.688413 IP6 voyager.mdns > ff02::fb.mdns: 0 [2q] PTR (QM)?<br>
> > _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)<br>
> > 15:11:07.499841 IP6 voyager > ip6-allrouters: ICMP6, router<br>
> > solicitation, length 16<br>
> > 15:11:11.079030 IP6 fe80::5054:ff:fe12:3456 > ip6-allrouters: ICMP6,<br>
> > router solicitation, length 16<br>
> <br>
> <br>
> Thanks, so with the ftgmac100 nic, you're able to talk to qemu via tap. I didn't see any obvious differences in the npcm7xx_emc device.<br>
> <br>
> ><br>
> > I've cc'd Cédric as he is the king of qemu command lines.<br>
> ><br>
> > Cheers,<br>
> ><br>
> > Joel<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> >><br>
> >> Patrick<br>
> <br>
<br>
</blockquote></div></div>