Checking suggestions, the booted image with tap seems to be working by
passing "-monitor telnet:127.0.0.1:1234,server,nowait"
so I will execute testing and update you.
==========================
root@qemuarm64:~# ifconfig
eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:02
inet addr:192.168.7.4 Bcast:192.168.7.255 Mask:255.255.255.0
inet6 addr: fe80::5054:ff:fe12:3402/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:116 errors:0 dropped:0 overruns:0 frame:0
TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:945121 (922.9 KiB) TX bytes:9529 (9.3 KiB)
root@qemuarm64:~# ./remote-test-server -v remote
starting test server
listening on 0.0.0.0:12345!
==========================
Regards,
Vinay
On Mon, May 17, 2021 at 8:02 PM Alexander Kanavin
<[email protected]> wrote:
>
> Thanks, can you please look into the error? The line where it happens and the
> way to get a backtrace is right there :)
> There's no reason it shouldn't work.
>
> Alex
>
> On Mon, 17 May 2021 at 15:21, Vinay Kumar <[email protected]> wrote:
>>
>> Hi Alex,
>>
>> Error on qemu image (ex. Aarch64) booted with tap interface.
>> ===========================
>> root@qemuarm64:~# ./remote-test-server
>> starting test server
>> thread 'main' panicked at 'TcpListener::bind(bind_addr) failed with
>> Cannot assign requested address (os error 99)',
>> src/tools/remote-test-server/src/main.rs:90:20
>> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
>> ===========================
>>
>> On Mon, May 17, 2021 at 5:16 PM Alexander Kanavin
>> <[email protected]> wrote:
>> >
>> > On Mon, 17 May 2021 at 13:34, Vinay Kumar <[email protected]> wrote:
>> >>
>> >> "remote-test-server" on qemu-image with a tap interface throws an error.
>> >> The emulators for rust testing are with tcp port forwarding so used
>> >> slirp method with added rust port.
>> >
>> >
>> > I'm not sure I understand - what kind of error? In both cases the server
>> > starts listening on a port, so in slirp scenario the address is
>> > 127.0.0.1:12345 (prone to breakage if something else on the build host
>> > took that port btw, including another instance of the same test), in tap
>> > it would be 192.168.7.2:12345. For the client you simply supply that via
>> > TEST_DEVICE_ADDR. No?
>> >
>> > Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#151977):
https://lists.openembedded.org/g/openembedded-core/message/151977
Mute This Topic: https://lists.openembedded.org/mt/82883381/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
