Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 07 Sep 2011 22:30:41 -0400
From:      "Brian J. McGovern" <mcgovern@beta.com>
To:        mrossi@swin.edu.au
Cc:        freebsd-arm@freebsd.org
Subject:   Re: Suggestions for arm build for qemu?
Message-ID:  <1315449041.1456.4.camel@bmcgover-laptop.beta.com>
In-Reply-To: <4E6605E8.70903@swin.edu.au>
References:  <20110708120025.5C94210656D9@hub.freebsd.org> <1310178351.5681.4.camel@bmcgover-laptop.beta.com> <4E18403C.8010203@gmail.com> <1310344111.1455.3.camel@bmcgover-laptop.beta.com> <4E1A4F18.5000802@gmail.com> <1310412331.1466.41.camel@bmcgover-laptop.beta.com> <4E1B83F8.3070700@gmail.com> <1310439696.1438.6.camel@bmcgover-laptop.beta.com> <4E1C48EE.3070905@gmail.com> <1310674865.1447.71.camel@bmcgover-laptop.beta.com> <4E1FA4E0.5050703@gmail.com> <1311045159.1508.3.camel@bmcgover-laptop.beta.com> <6E4BB877-4039-41A8-96B7-AB36AE2774C0@gmail.com> <1311808468.1465.10.camel@bmcgover-laptop.beta.com> <4E6605E8.70903@swin.edu.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2011-09-06 at 21:37 +1000, Mattia Rossi wrote:
> On 28/07/11 09:14, Brian J. McGovern wrote:
> > On Wed, 2011-07-27 at 16:08 +0200, Damjan Marion wrote:
> >> On Jul 19, 2011, at 5:12 AM, Brian J. McGovern wrote:
> >>
> >>> That got it. The kernel is now booting, and I'm able to run the
> >>> applications in /rescue. The other binaries seem to be hit or miss
> >>> (signal 11s), although the C compiler can build 'hello world', so I'm
> >>> guessing that either the dynamic linker isn't set up right (/etc isn't
> >>> populated by the installworld, so I continue to add files by hand) and
> >>> its having a problem finding all the dynamic libraries it wants, or the
> >>> 64MB memory limit is a problem, and I need to get swap going. In any
> >>> event, its enough to get my hacking until Globalscale ships my board.
> >>
> >> Hi Brian,
> >>
> >> Can you share how did you setup root file system? I tried to play with
> >> qemu network settings but didn't reach far away from:
> >>
> >> Received DHCP Ack packet on smc0 from 10.0.2.2 (accepted) (no root path)
> >> DHCP/BOOTP timeout for server 255.255.255.255
> >>
> >> Thanks,
> >>
> >> Damjan
> >>
> >>
> > Sure. Happy to share what others helped with... I'm going to assume
> > you've read through http://wiki.freebsd.org/FreeBSDMarvell, have built
> > and the exported file system. It looks like you're getting hung up on
> > passing the root filesystem via DHCP. I'm using the isc-dhcp server, so
> > I had to add
> >
> > option root-path "dotted.quad.ip.addr:/path/to/exported root";
> >
> > to the section that will give an address to the device. This will get
> > the device to mount the NFS export as the root filesystem.
> >
> > Once you can boot the device, you can use the standard tools to build
> > local filesystems if you've defined hard disks or other storage.
> >
> 
> Hi Brian,
> 
> Coming back to this whole qemu issue, following the various posts in 
> this thread, I've been able to boot the kernel and to get a DHCP offer 
> from my DHCP server. It also comes as far as trying to set the NFS root 
> up, using the hint you gave above, but then it will fail with an RPC 
> timeout. I suspect that the NFS server wont bind to the tap0 interface?
> 
> I start qemu the following way:
> qemu-system-arm -M connex -m 289 -pflash <flash> -nographic -serial 
> tcp::4000,server -net nic,macaddr=<random mac 
> addr>,vlan=0,model=smc91c111 -net tap,vlan=0,ifname=tap0,script=no
> 
> I have a tap0 interface with the IP address, which I point the option 
> root-path to (it's a 10 dot something address). The NFS server is set to 
> listen on the 10 dot something subnet.
> 
> Do you have some other trick in there to make it working?
> 
> I've tried to bridge tap0 to em0 as well, but couldn't get any DHCP 
> requests on em0 in that case.. The host system is 8.2, the Qemu arm 
> system is CURRENT.
> 
> Any help would be highly appreciated!
> 
> Mat
> 
> 

The one other thing that came to mind is check the NFS client you're
using in your kernel if you're using FreeBSD 9.x... You'll need to make
sure you have the "right" combination of NFS client and mount options
(nfs vs. oldnfs).




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1315449041.1456.4.camel>