Skip to content
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

Open
celestialtao opened this issue Feb 15, 2022 · 3 comments
Labels
bug Something isn't working help wanted Extra attention is needed question Further information is requested

Comments

@celestialtao
Copy link

celestialtao commented Feb 15, 2022

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:

Starting syslogd: OK
Starting syslogd: OK
Starting syslogd: OK
Starting klogd: OK
Starting klogd: OK
Starting klogd: OK
Running sysctl: OK
Running sysctl: OK
Running sysctl: OK
Initializing random number generator... [   43.352936] random: dd: uninitialized urandom read (512 bytes read)
done.
Initializing random number generator... [   43.476458] random: dd: uninitialized urandom read (512 bytes read)
done.
Initializing random number generator... [   44.130296] random: dd: uninitialized urandom read (512 bytes read)
done.
Starting network: OK
Starting network: OK
Starting network: OK
udhcpc: started, v1.31.0
udhcpc: started, v1.31.0
/etc/init.d/S90bridge_setup: line 12: brctl: not found

Welcome to Buildroot
[   53.859732] random: mktemp: uninitialized urandom read (6 bytes read)
[   53.967484] random: mktemp: uninitialized urandom read (6 bytes read)
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover

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?

@axel-h axel-h added the question Further information is requested label Jul 4, 2022
@wom-bat
Copy link
Member

wom-bat commented Jul 20, 2022

I'm not sure this has ever worked with the qemu-arm-virt target. The simulate script generated doesn't set up a network, so udhcpc will never return an address.

axel-h added a commit to axel-h/ci-actions that referenced this issue Jan 27, 2024
will fail, see also seL4/camkes-vm-examples#18
Signed-off-by: Axel Heider <axelheider@gmx.de>
@axel-h axel-h added bug Something isn't working help wanted Extra attention is needed labels Jan 27, 2024
axel-h added a commit to axel-h/ci-actions that referenced this issue Jan 27, 2024
will fail, see also seL4/camkes-vm-examples#18
Signed-off-by: Axel Heider <axelheider@gmx.de>
axel-h added a commit to axel-h/ci-actions that referenced this issue Jan 27, 2024
will fail, see also seL4/camkes-vm-examples#18
Signed-off-by: Axel Heider <axelheider@gmx.de>
axel-h added a commit to axel-h/ci-actions that referenced this issue Jan 28, 2024
will fail, see also seL4/camkes-vm-examples#18
Signed-off-by: Axel Heider <axelheider@gmx.de>
@axel-h
Copy link
Member

axel-h commented Feb 1, 2024

I'm not sure this has ever worked with the qemu-arm-virt target. The simulate script generated doesn't set up a network, so udhcpc will never return an address.

Maybe the simulate script does not do it explicitly, but in apps/Arm/vm_multi/settings.cmake we have this:

    set(
        qemu_sim_extra_args
        "-netdev tap,id=mynet0,ifname=tap0,script=no,downscript=no -device virtio-net,netdev=mynet0,mac=52:55:00:d1:55:01"
    )

@simone-arcari
Copy link

Has this issue been resolved?
I also have another issue, again on vm_multi running on qemu:

vm_ram_touch@guest_ram.c:165 Failed to touch ram region: Not registered RAM region
udhcpc: sending discover
vm_ram_touch@guest_ram.c:165 Failed to touch ram region: Not registered RAM region
udhcpc: sending discover
vm_ram_touch@guest_ram.c:165 Failed to touch ram region: Not registered RAM region
udhcpc: sending discover
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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants