-
Notifications
You must be signed in to change notification settings - Fork 16
Troubleshooting
There are two solutions to overcome this error. Either by removing the kvm option from the qemu call and accepting a lower performance of the demo or by switching ON virtualization support in the hardware setting of the PC. This setting differs depending on Bios and UEFI version used. It depends on the underlying CPU architecture and also on the mainboard manufacturer. A clear answer cannot be provided in the official readme. It makes sense to have this as a general trouble shooting knowledge base. Using the wiki of the repo may serve a a base until there is a better solution for it. Potential options could be something like "Intel®Virtualization Technology" or "AMD-V" or "svm support" as on an MSI mainboard. For the MSI mainboard it can be found under "Advanced CPU Configuration" in the ==>overclocking<== section. (see forum report or msi docu The option is not always enabled by default and may sometimes be hard to find.
If you see the following warning, it can be safely ignored:
WARNING: No bb files matched BBFILE_PATTERN_meta-elisa '^/src/home/AGL/koi/meta-elisa/meta-elisa/'
meta-elisa/meta-elisa only has the conf file and does not have any bb file which results in the warning.
If you see the following warning, it can be safely ignored:
WARNING: You are using a local hash equivalence server but have configured an sstate mirror. This will likely mean no sstate will match from the mirror. You may wish to disable the hash equivalence use (BB_HASHSERVE), or use a hash equivalence server alongside the sstate mirror.
You can see that the sstate will work anyway, if you find something similar to this message:
Sstate summary: Wanted 2941 Local 0 Mirrors 2922 Missed 19 Current 0 (99% match, 0% complete)
The sstate itself can be enabled by mofification of the local.conf in your build/conf directory of the yocto build. For ELISA server simply add:
SSTATE_MIRRORS += "file://.* https://elisa-builder-00.iol.unh.edu/sstate/needlefish/PATH"
There is a short comprehensive user guide for post-installation steps, which comes as part of docker documentation.
You can follow the instructions at: Manage Docker as a non-root user
When running the qemu demo, my mouse and keyboard are bound to the qemu window. In order to release the keyboard and mouse from the demo again, since qemu 1.5, you have to type CTRL + ALT + G. Depending on your distro and qemu version you will also find this hint at the top of the open qemu demo window directly.