[Barrelfish-users] RTL8029 not recognized in qemu

[Alan Kligman]

I'm curious to try this but I don't have pxegrub-undi in my source tree. Is
this something you build by hand?


On Tue, Jun 25, 2013 at 2:20 PM, Andrew Baumann <
Andrew.Baumann at microsoft.com> wrote:

>  Oh that’s a grub error. You need to use a grub that supports either
> e1000 or PXE boot. The one in the tree that ‘make sim’ points at only
> includes (I think) the RTL driver.****
>
> ** **
>
> After digging back through old email, here’s a qemu invocation that once
> worked for me:****
>
> ** **
>
> qemu-system-x86_64 -smp 1 -m 2048 -net nic,model=e1000  -net
> user,tftp=/.../build,bootfile=/pxegrub-undi -serial file:/dev/stdout****
>
> ** **
>
> Andrew****
>
> ** **
>
> *From:* Alan Kligman [mailto:alan.kligman at gmail.com]
> *Sent:* Tuesday, 25 June 2013 11:12
> *To:* Andrew Baumann
> *Cc:* barrelfish-users at lists.inf.ethz.ch
> *Subject:* Re: [Barrelfish-users] RTL8029 not recognized in qemu****
>
> ** **
>
> Unfortunately, I'm not able to get barrelfish to boot at all with the
> e1000 nic:
>
> root  (nd)
>
> Error 23: Error while parsing number****
>
> Do I need to rebuild the boot image here?****
>
> ** **
>
> On Tue, Jun 25, 2013 at 1:59 PM, Andrew Baumann <
> Andrew.Baumann at microsoft.com> wrote:****
>
>  This rings a faint bell for me.****
>
>  ****
>
> If I remember correctly, the RTL driver has a hardcoded IO port range and
> IRQ, and at some point qemu moved the device. If you’re using a newer
> version of qemu, I’d suggest trying its e1000 support, as that driver is
> generally in much better shape than the RTL driver.****
>
>  ****
>
> Cheers,****
>
> Andrew ****
>
>  ****
>
> *From:* Alan Kligman [mailto:alan.kligman at gmail.com]
> *Sent:* Tuesday, 25 June 2013 10:52
> *To:* barrelfish-users at lists.inf.ethz.ch
> *Subject:* [Barrelfish-users] RTL8029 not recognized in qemu****
>
>  ****
>
> I'm trying to get networking up inside qemu, but barrelfish doesn't
> recognize the emulated network adapter:
>
> Initializing RTL8029(AS)...
> This is not a recognized rtl8029as: ID is 00:00!
> For service [rtl8029] MAC= 00:00:00:00:00:00****
>
> I definitely have an adapter:
>
> (qemu) info network
> ne2k_pci.0: index=0,type=nic,model=ne2k_pci,macaddr=52:54:00:12:34:56
>  \ local: index=0,type=user,net=10.0.2.0,restrict=off****
>
> Here's my menu.lst:
>
> title   Barrelfish
> root    (nd)
> kernel  /x86_64/sbin/elver loglevel=4
> module  /x86_64/sbin/cpu loglevel=4
> module  /x86_64/sbin/init
>
> # Domains spawned by init
> module  /x86_64/sbin/mem_serv
> module  /x86_64/sbin/monitor
>
> # Special boot time domains spawned by monitor
> module  /x86_64/sbin/ramfsd boot
> module  /x86_64/sbin/skb boot
> modulenounzip /skb_ramfs.cpio.gz nospawn
> module  /x86_64/sbin/kaluga boot
> module  /x86_64/sbin/acpi boot
> module  /x86_64/sbin/spawnd boot
> #bootapic-x86_64=1-15
> module  /x86_64/sbin/startd boot
> module /x86_64/sbin/routing_setup boot
>
> # Drivers
> module /x86_64/sbin/pci boot
> module /x86_64/sbin/ahcid boot
> module /x86_64/sbin/rtl8029
> module /x86_64/sbin/NGD_mng cardname=rtl8029
> module /x86_64/sbin/netd cardname=rtl8029
>
> # General user domains
> module  /x86_64/sbin/serial
> module  /x86_64/sbin/fish****
>
> Any help would be appreciated.****
>
> Cheers,
> A****
>
>  ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.inf.ethz.ch/pipermail/barrelfish-users/attachments/20130625/55eef6eb/attachment-0001.html