Summary: | app-emulation/virtualbox-guest-additions: emerge hangs at "Extracting guest kernel module sources ..." | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Didier Colle <didier.colle> |
Component: | Current packages | Assignee: | Viorel Munteanu <ceamac> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=748984 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Didier Colle
2021-01-06 12:45:37 UTC
Any chance you're trying to build this in a docker container? (In reply to Lars Wendler (Polynomial-C) from comment #1) > Any chance you're trying to build this in a docker container? I indeed have docker installed inside this vbox guest. I did however NOT launch this emerge command inside a docker container. Can you check if the error persists when you uninstall docker? You can make a backup of the docker package with /usr/bin/quickpkg: quickpkg app-emulation/docker and later re-install it with emerge -1OKv app-emulation/docker (In reply to Lars Wendler (Polynomial-C) from comment #3) > Can you check if the error persists when you uninstall docker? I tried this. Without success (was hanging at same point for more than half an hour), unfortunately. Plaese check if something is locking your /dev/null device. bug #748984 had been filed for the very same reason and there the offending blocker process was docker. (In reply to Didier Colle from comment #2) > (In reply to Lars Wendler (Polynomial-C) from comment #1) > > Any chance you're trying to build this in a docker container? > > I indeed have docker installed inside this vbox guest. > I did however NOT launch this emerge command inside a docker container. I think you need to stop the docker daemon where you run the emerge cmd (In reply to Lars Wendler (Polynomial-C) from comment #5) > Plaese check if something is locking your /dev/null device. bug #748984 had > been filed for the very same reason and there the offending blocker process > was docker. my apologies for the stupid question: how can I confirm there is no such lock? I thought using flock -u in case such lock exists, but either I don't understand the flock command or it is not reliable: > dcolle@localhost ~ $ flock -n -E 200 -x /dev/null echo; echo $? > > 0 > dcolle@localhost ~ $ flock -n -E 200 -x /dev/null echo; echo $? > > 0 Should the output of the second run not result in 200 instead of 0 after a blank line??? AFAIK, /usr/bin/flock is not the right tool for checking if a file is locked from some application. Better use one of the following two tools for this: /bin/fuser (sys-process/psmisc package) /usr/bin/lsof (sys-process/lsof package) (In reply to Lars Wendler (Polynomial-C) from comment #8) > AFAIK, /usr/bin/flock is not the right tool for checking if a file is locked > from some application. Better use one of the following two tools for this: > > /bin/fuser (sys-process/psmisc package) > /usr/bin/lsof (sys-process/lsof package) Thanks for the pointers. The good news: in the meantime, I could emerge the virtualbox-guest-additions package. The bad news: I am not sure what solved the problem; executing fuser -k /dev/null was a bit too drastic which terminated my emacs over ssh session and was not able to restore that session and consequently rebooted my headless vm. Is the conclusion that the docker package should block the virtualbox-guet-additions package? (no issue for my day to day work, but sporadically I need the docker stuff in that vm, thus both packages blocking each other would be a pity) (In reply to Lars Wendler (Polynomial-C) from comment #5) > Plaese check if something is locking your /dev/null device. bug #748984 had > been filed for the very same reason and there the offending blocker process > was docker. Hi Lars, I don't use docker but cri-o. Once I disable cri-o (systemctl disable cri-o) the issue disappears. I believe I am hitting the same issue. I understand that after removing "&>/dev/null" the kmk command will become too verbose, but will the -s option work? Below is what I get from kmk --help: -s, --silent, --quiet Don't echo recipes. |