Github messages for voidlinux
 help / color / mirror / Atom feed
From: ejolson2005 <ejolson2005@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] qemu-aarch64-static works in glibc but the musl version is missing certain network functions.
Date: Tue, 14 Jul 2020 05:42:31 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23557@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3195 bytes --]

New issue by ejolson2005 on void-packages repository

https://github.com/void-linux/void-packages/issues/23557

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
```
$ xuname
Void 5.4.50_1 x86_64-musl AuthenticAMD notuptodate rF
$ xbps-query -p pkgver qemu-user-static
qemu-user-static-5.0.0_2
```

### Expected behavior'
When used in a qemu chroot expect networking to work.

### Actual behavior

DNS lookups don't work nor does ip address find the network devices.  Note that specifying network addresses by IP number allows things like ssh to connect, but this is not a DNS problem because /etc/resolv.conf is correct and moreover, things begin working if the qemu-aarch64-static binary from the glibc version of Void Linux is copied in order the one compiled with musl and reregistered.

### Steps to reproduce the behavior

With the musl version of qemu-aarch64-static copied into an aarch64 chroot in which a correct resolv.conf has been placed and the proc, dev and sys file systems mounted I get
```
[root@silver images]# chroot iroot
root@silver:/# ping google.com
ping: google.com: Temporary failure in name resolution
root@silver:/# ip address
netlink receive error Message too long (90)
Dump terminated
```
Using exact same chroot but with the glibc version of qemu-aarch64-static copied in from a glibc version of Void  Linux and reregistered I get
```
[root@silver images]# chroot iroot
root@silver:/# ping google.com
PING google.com (172.217.5.206) 56(84) bytes of data.
64 bytes from lax28s10-in-f206.1e100.net (172.217.5.206): icmp_seq=1 ttl=115 time=39.5 ms
64 bytes from lax28s10-in-f206.1e100.net (172.217.5.206): icmp_seq=2 ttl=115 time=38.7 ms
64 bytes from lax28s10-in-f206.1e100.net (172.217.5.206): icmp_seq=3 ttl=115 time=37.4 ms
^C
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 6ms
rtt min/avg/max/mdev = 37.354/38.513/39.486/0.880 ms
root@silver:/# ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: esan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 68:1c:a2:12:af:95 brd ff:ff:ff:ff:ff:ff
    inet 192.168.47.254/25 brd 192.168.47.255 scope global noprefixroute esan
       valid_lft forever preferred_lft forever
    inet6 fe80::1ba9:d1d:c8aa:20f7/64 scope link 
       valid_lft forever preferred_lft forever
```
which is correct.  This error appears related to the musl library and possibly related to

https://github.com/docker/for-mac/issues/1621

which identifies a similar build problem for qemu-aarch64-static on Mac OS.  I've not taken any look at the code, but expect somewhere the build process for aarch64 checks for glibc and assumes it's not Linux otherwise.


             reply	other threads:[~2020-07-14  3:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14  3:42 ejolson2005 [this message]
2020-07-14  3:44 ` ericonr
2020-07-14  3:51 ` ejolson2005
2020-07-14  3:52 ` ejolson2005
2020-07-14  3:52 ` ejolson2005
2020-07-14  3:55 ` ejolson2005
2020-07-14  4:00 ` ejolson2005
2020-07-18  5:24 ` sgn
2020-10-29  2:31 ` ericonr
2020-10-29  2:48 ` richfelker
2020-10-29  5:13 ` ericonr
2020-10-29  6:32 ` richfelker
2021-02-11 18:22 ` [ISSUE] [CLOSED] " ericonr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23557@inbox.vuxu.org \
    --to=ejolson2005@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).