Summary: | <app-emulation/qemu-4.2.0: sys-apps/portage-2.3.79 - _configure_loopback_interface does not work properly in qemu-aarch64 chroot. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | anonymous <fakih18716> |
Component: | Current packages | Assignee: | Virtualization Team <virtualization> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dev-portage |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://launchpad.net/bugs/1857811 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
anonymous
2019-12-18 10:30:23 UTC
Try setting FEATURES="-network-sandbox" in make.conf. I suspect there is nothing we can do in Portage to make this with in qemu-user. FEATURES="-network-sandbox" works around this issue. It seems qemu doesn't yet support pid-sandbox and network-sandbox Same error and same fix using FEATURES flag with Gentoo chroot launched via systemd-nspawn, no Qemu involved. Btw, doesn't look like there's much point keeping this bug open. According to https://launchpad.net/bugs/1857811 it's supposed to have been fixed in qemu v4.2.0. (In reply to Alexei Colin from comment #3) > Same error and same fix using FEATURES flag with Gentoo chroot launched via > systemd-nspawn, no Qemu involved. Btw, doesn't look like there's much point > keeping this bug open. For systemd-nspawn it's expected because that creates a light-weight container with reduced privileges. |