-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Faild to run the virtual simulator #6
Comments
Hi, Please make sure all VirtFS dependencies(libattr1-dev and libcap-dev) installed in your environment. And have a try again. Thanks a lot! |
I follow the command and appear this libattr1-dev is already the newest version. But i got the same problem. |
Hi @allenlaitw , Can you check if there is '#define CONFIG_VIRTFS 1" in the generated vp/libs/qbox.build/config-host.h? If not, then it means that the virtfs is not built with QEMU. The QEMU build flow is supposed to check if cap and attr is available and enable this option. If you are sure they are all available, can you try remove the vp/libs/qbox.build and re-build the simulator. You can also use our docker image which includes the development environment and a prebuilt binary. |
http://nvdla.org/vp.html#running-kernel-image-in-the-virtual-simulator
I'm trying this step on the web,but i got the error below.
chi@chi:~/tools_for_cmod/vp$ ./build/bin/aarch64_toplevel -c conf/aarch64_nvdla.lua
No sc_log specified, will use the default setting
verbosity_level = SC_MEDIUM
bridge: tlm2c_elaborate..
toplevel: -device virtio-9p-device,fsdev=r,mount_tag=r: 'virtio-9p-device' is not a valid device model name
I'm on ubuntu14.04.
How i shoud do to solve this problem?
Thanks
The text was updated successfully, but these errors were encountered: