| View previous topic :: View next topic |
| Author |
Message |
wilf
Tux's lil' helper
Joined: 12 Feb 2006
Posts: 131
Location: West Sussex, UK
|
 Posted: Fri Jul 20, 2007 10:42 am Post subject: Install FUSE: Networking now dead |
 |
|
Hello Everyone,
I started this query off here which seems to have been the wrong place. However, it will give you some background.
It looks like the problem is more subtle and may have something to do with Portage and setup.
So here is where I am.
The base instance has the following make.conf:-
| Code: | # These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
#CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu" # Default installation settings (PWI 20060831)
CFLAGS="-march=k8 -pipe -O2" # AMD64 users should use march=k8
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j5" # defines number of parallel compilations - number of CPUs + 1 |
The base instance kernel has FUSE compiled in:-
CONFIG_FUSE_FS=y
from .config.
I run a number of virtual machines, and on one of them I want to run fuse/sshfs. whenever I emerge in sys-fs/fuse, networking breaks and it takes an eon to stop the instance. To make my life easier, I have built an OpenVZ tar image which uses the same make.conf as the base instance but uses a different make.profile, linked to /usr/portage/profiles/default-linux/amd64/vserver.
This allows me to destroy the image (trying to build fuse does the trick) and then very quickly be back up and running again.
To install FUSE, gentoo emerges in a number of other packages prior to emerging FUSE itself. This is done within the instance and does not affect the base instance.
These are the packages that would be merged, in order:
Calculating dependencies ... done!
[ebuild N ] sys-kernel/gentoo-sources-2.6.20-r8 USE="-build -symlink"
[ebuild N ] virtual/init-0
[ebuild N ] sys-apps/baselayout-2.0.0_alpha3-r1 USE="pam -bootstrap -build -static -unicode"
[ebuild N ] sys-apps/module-init-tools-3.2.2-r3 USE="-old-linux"
[ebuild N ] sys-fs/fuse-2.7.0
I have added sys-fs/fuse disable-kernel-config to /etc/packages.use
I test by installing each module in turn, then exiting the instance, stopping and restarting the instance and then pinging the instance to test for a response.
virtual/init goes in OK.
sys-apps/baselayout also emerges sys-apps/module-init-tools without pausing, this is where the problem lies.
I did not reach FUSE as sys-apps/baselayout had already screwed up the instance networking.
Trying to build sys-apps/module-init-tools first builds baselayout first anyway, so I can't tell which is at fault.
exiting the instance and then pinging it the network is still up - as soon as I stop and restart the instance, networking is gone.
As another note, stopping the instance goes from a few seconds to a few minutes after baselayout is merged.
I noticed that available packages for the instance differ from the base instance. | Code: | vz_base private # cd /etc
vz_base private # ls -lasi
(Ed: snip...)
make.profile -> ../usr/portage/profiles/default-linux/amd64/2006.1
vz_base private # equery list -o -p sys-apps/baselayout
[ Searching for package 'baselayout' in 'sys-apps' among: ]
* installed packages
[I--] [ ] sys-apps/baselayout-1.12.9-r2 (0)
* Portage tree (/usr/portage)
[-P-] [ ] sys-apps/baselayout-1.11.15-r3 (0)
[-P-] [M~] sys-apps/baselayout-1.12.10-r3 (0)
[-P-] [M~] sys-apps/baselayout-1.12.10-r4 (0)
[-P-] [M~] sys-apps/baselayout-1.13.0_alpha12 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha1 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha2 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha2-r1 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha3 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha3-r1 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha4 (0)
[-P-] [M ] sys-apps/baselayout-lite-1.0_pre1 (0)
[-P-] [ ] sys-apps/baselayout-vserver-1.11.14-r4 (0)
[-P-] [M~] sys-apps/baselayout-vserver-1.12.3 (0)
[-P-] [M~] sys-apps/baselayout-vserver-1.12.6 (0)
* overlay tree ()
vz_base private # vzctl enter 503
ve_1 / # cd /etc
ve_1 etc # ls -lasi
(Ed: snip...)
make.profile -> ../usr/portage/profiles/default-linux/amd64/vserver
ve_1 etc # equery list -o -p sys-apps/baselayout
[ Searching for package 'baselayout' in 'sys-apps' among: ]
* installed packages
[I--] [ ] sys-apps/baselayout-vserver-1.11.14-r4 (0)
* Portage tree (/usr/portage)
[-P-] [M ] sys-apps/baselayout-1.11.15-r3 (0)
[-P-] [M ] sys-apps/baselayout-1.12.9-r2 (0)
[-P-] [M~] sys-apps/baselayout-1.12.10-r3 (0)
[-P-] [M~] sys-apps/baselayout-1.12.10-r4 (0)
[-P-] [M~] sys-apps/baselayout-1.13.0_alpha12 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha1 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha2 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha2-r1 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha3 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha3-r1 (0)
[-P-] [M~] sys-apps/baselayout-2.0.0_alpha4 (0)
[-P-] [M ] sys-apps/baselayout-lite-1.0_pre1 (0)
[-P-] [M~] sys-apps/baselayout-vserver-1.12.3 (0)
[-P-] [M~] sys-apps/baselayout-vserver-1.12.6 (0)
* overlay tree () |
The point I am taking rather a long time reaching is explained here. The long and short of it is that the vserver should be able to use the latest unmasked baselayout.
As the latest stable unmasked release is sys-apps/baselayout-1.12.9-r2, I specified this in /etc/packages.keywords and /etc/packages.unmask. baseutils compiles, but upon exiting the instance, stopping and restarting, networking is DOA for the instance.
It looks to me as if baselayout/module-init-tools is doing something freaky in an OpenVZ environment.
If you feel you can help me resolve this I will be so very grateful.
Best Regards, Paul. |
|
| Back to top |
|
 |
wilf
Tux's lil' helper
Joined: 12 Feb 2006
Posts: 131
Location: West Sussex, UK
|
| Posted: Sat Jul 21, 2007 11:06 pm Post subject: |
|
|
| Added bug report. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
