When I am trying x86 qemu and arm qemu, I often meet MOUNTD ERROR even if I deleted all tmp folder and delete all tapX. After reboot, I finally successfully boot. Not knowing what's the reason... Report this bug since this might be an potential issue. Thanks a lot! criping
are you still seeing this after the reboot?
Oh, after reboot, everything is ok. But I may meet the problem again after running for a while. Thanks! criping
I've down-grade it to low+minor to keep track the issue...
Liping, is the mountd error part of the kernel boot-up messages? Can you give me a screenshot or copy the error message and a few messages before/after the error? That will help give me needed context to look into this.
Hi, scott It's script error, I remember that qemu will not be launch but script printing MOUNTD issue. I will copy you the screenshot when I meet the problem again. Just want to make sure what's the reason of MOUNTD failure, my wrong disk status or some other potential issues. Thanks & Regards, criping
Liping, have you run into this error since the last time you commented on this bug? I cannot reproduce it here.
Hi, Scott I have finished RC3 test today, I did not meet the same problem recently. If I can't reproduce the problem in the following days, I will update the bug status. Thanks a lot! criping
O, I just meet the problem again in starting arm qemu. So I just can't close this bug. Please see my screen shot in the attachment. If I restart, the problem is gone. So I am not what's happening. The hardware status of disk is something wrong when meeting MountD Error? Thanks& Regards, criping
Created attachment 61 [details] MOUNTD error
Thanks for the screenshot. An error with mountd starting implies that there could be a pre-existing mountd running. Which would also explain why it keeps happening until you reboot. Is there something that could be killing the poky-qemu process directly? Note that if QEMU hangs and you need to kill it, you should always kill the QEMU process itself and *not* the poky-qemu process - otherwise the poky-qemu script will not be able to shut down the userspace NFS server and that would cause this problem.
Scott cannot reproduce. He will verify that it is not occuring in 1.0 and close. Liping will also try to reproduce.
My understanding is that this bug was only reproduced recently due to issues with firewall settings. Once that was corrected, the images were booting again. The remaining issue has to do with the qemuppc image, and that is being tracked in bug #414. So I am closing this bug.