NFS of qemu mini2440

I trying to boot form the nfs in qemu, but it panic after ROOT-nfs error.
the error message is:
rpcbind server 10.0.0.1 not respoding, time out
root-nfs: unable to get mountd port number form server, using default.

the mini2440 is configue as 10.0.0.10 and tap0 is config as 10.0.0.1
a bridge br0 is set up,and after the kenel painc , I can still ping
10.0.0.10 form the host.

bootargs is set as : set bootargs noinitrd root=/dev/nfs rw
nfsroot=10.0.0.1:/home/yang/linux/rootfs.img
ip=10.0.0.10:10.0.0.1:255.255.255.0 console=ttySAC0,115200

the nfs is config in /etc/exportfs as 
/home/yang/linux 10.0.0.0/24(rw,async,insecure,no_root_squash)
and I cant moutn it to /mnt/nfs.

as I can ping the 10.0.0.10, does it means my net work config is ok?

what's wrong in my case?

I have excatly the same bug.

I become crazy.


Here are my bootargs :

setenv bootargs console=ttySAC0,115200 root=/dev/nfs
nfsroot=192.168.1.84:/home/goooo/mini2440/qemu/mini2440/rootfs rw
ip=192.168.1.70:192.168.1.84:192.168.1.84:255.255.255.0:MINI2440.arm9.net:eth0:o
ff


This is the result :

IP-Config: Complete:
     device=eth0, addr=192.168.1.70, mask=255.255.255.0, gw=192.168.1.84,
     host=MINI2440, domain=, nis-domain=arm9.net,
     bootserver=192.168.1.84, rootserver=192.168.1.84, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.84
rpcbind: server 192.168.1.84 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default



But when I run a ping from my PC to Qemu (ping 192.168.1.84), but I have
100% packet loss.


Please can you tell me what are exacly the differents ip in the bootargs ?
What is the ip of the PC and what is the Ip of the board (Qemu Board).



Please help us !!!!

do you mean ping  192.168.1.70 loss packet?
as your config 192.168.1.84 is pc's ip and qemu is 192.168.1.70.

I has a long time with the same problem like you,before I read this 
http://facetlife.blogspot.com/2011/01/qemu-mini2440-nfs.html

but, nfs still not wrok for me now!

sorry ,the correct url of my reference is this:
http://blog.alantan.com/2007/01/qemu-tap-bridge-network-configuration.html

I don't success.

There is another way, the Sd but I don't success too.

hi Baby. I had at last  fix the nfs connect!
still I can't tell what happen and fix my problem.
but I can tell you how I do it.
1. I make two vm of vmware to test the nfs mounting that bind to the vm
machine net card. I use showmount to test if the nfs dir can be seen form
the second vm machine. at last I can mount the dir to the second vm machine

2 if step 1 is ok. rewrite the exportfs to bing the nfs dir to the
tap0。
for me,it's 10.0.0.1; restart nfs service. and start qemu and the linux
kernel just as my first post.
3 at this time, I get an error 13 of nfs from the host vm. at the syslog
message,I found the vm block the request of qemu. so I stop my firewall as
some guys suggest, and add the 10.0.0.10 to the hosts file.and
"portmap:10.0.0：allow \n ALL:ALL:allow"to the hosts.allow file at
etc.

finally, nfs work for me. It seem no need to add bridge between tap0 and
eth0, since we don't connect the qemu to internet.

hope that you can understand my poor english, and this will help you.