-
Notifications
You must be signed in to change notification settings - Fork 27
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
Issuse about running vm_multi app on qemu platform, udhcpc can not return. #18
Comments
I'm not sure this has ever worked with the |
will fail, see also seL4/camkes-vm-examples#18 Signed-off-by: Axel Heider <axelheider@gmx.de>
will fail, see also seL4/camkes-vm-examples#18 Signed-off-by: Axel Heider <axelheider@gmx.de>
will fail, see also seL4/camkes-vm-examples#18 Signed-off-by: Axel Heider <axelheider@gmx.de>
will fail, see also seL4/camkes-vm-examples#18 Signed-off-by: Axel Heider <axelheider@gmx.de>
Maybe the simulate script does not do it explicitly, but in
|
Has this issue been resolved? vm_ram_touch@guest_ram.c:165 Failed to touch ram region: Not registered RAM region do you know if there is a solution for this? |
After building vm_multi app for qemu and running ./simulate in my build directory, the console always printed the log "udhcpc: sending discover",which indicating udhcpc can not return. Meanwhile, your prebuilt rootfs did not support brctl in busybox judging from error log "/etc/init.d/S90bridge_setup: line 12: brctl: not found".
The related log was shown as follows:
These two errors may have some interdependency. Is the expected resutl for the vm_multi that an ip address will be respectively given to eth0 and br0?
The text was updated successfully, but these errors were encountered: