Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 703276 - <app-emulation/qemu-4.2.0: sys-apps/portage-2.3.79 - _configure_loopback_interface does not work properly in qemu-aarch64 chroot.
Summary: <app-emulation/qemu-4.2.0: sys-apps/portage-2.3.79 - _configure_loopback_inte...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Virtualization Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-18 10:30 UTC by anonymous
Modified: 2020-12-29 03:26 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description anonymous 2019-12-18 10:30:23 UTC
When I execute equery or emerge in qemu-aarch64 chroot, I see the following error message many times.

Unable to configure loopback interface: Operation not supported

I traced the error back to _configure_loopback_interface function in sys-apps/portage by searching the internet.
Comment 1 Mike Gilbert gentoo-dev 2019-12-18 16:48:35 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.
Comment 2 anonymous 2019-12-18 23:58:24 UTC
FEATURES="-network-sandbox" works around this issue. It seems qemu doesn't yet support pid-sandbox and network-sandbox
Comment 3 Alexei Colin 2020-12-29 01:55:55 UTC
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.
Comment 4 Zac Medico gentoo-dev 2020-12-29 03:26:44 UTC
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.