A full description is here... http://forums.gentoo.org/viewtopic-t-571440.html You will also find an entry on the OpenVZ site here... http://forum.openvz.org/index.php?t=msg&th=2923&start=0& Any more info required, please contact me and I will help as much as I can. I use this setup for customers and I would be *really* grateful if you can have a look at your earliest convenience (i.e., pretty please). Reproducible: Always Steps to Reproduce: 1.load and configure OpenVZ 2.create an instance (AMD64 Gentoo) 3.start instance and emerge in baselayout 4.stop instance 5.start instance and you'll no longer be able to ping it from the base instance. Actual Results: Networking from instance dead Expected Results: networking still alive
Only baselayout-2 supports vservers ....
(In reply to comment #0) > Actual Results: > Networking from instance dead I can confirm this bug, OpenVZ host system: Gentoo Amd64, VE's with baselayout-1.1.13* and vserver-baselayout are running without problems (ping from Host System, external, ssh login, everything possible). On one VE i did update baselayout to 2.x because 1.1.13 was removed from portage tree, now I get: "RTNETLINK answers: Network is unreachable" when trying "vzctl exec 102 /etc/init.d/net.venet0 start". Some more testing: # vzctl exec 102 ip route 127.0.0.0/8 via 127.0.0.1 dev lo Here I'm missing: 192.0.2.0/24 dev venet0 scope link default via 192.0.2.1 dev venet0 I'm happy I didn't update all VE's ;) # vzctl exec 102 emerge --info Portage 2.1.2.11 (default-linux/x86/2007.0/server, gcc-4.1.2, glibc-2.5-r4, 2.6.18-028stab035 i686) ================================================================= System uname: 2.6.18-028stab035 i686 AMD Sempron(tm) Processor 2800+ Gentoo Base System release 2.0.0_rc1 Timestamp of tree: Fri, 03 Aug 2007 13:20:01 +0000 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r6 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks fixpackages metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo ftp://mirror.icis.pcz.pl/gentoo/ ftp://212.219.56.132/sites/www.ibiblio.org/gentoo/" LINGUAS="de" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://80.80.245.56/gentoo-portage" USE="acl bitmap-fonts bzip2 cli contentcache cracklib crypt ctype cups curl dedicated dnsdb dri encode fortran gdbm geoip gif iconv idn ipv6 isdnlog jpeg libg++ libwww logrotate mailwrapper midi mime ming mng mp3 mp4 mpeg mudflap ncurses nls nptl nptlonly ogg openmp pam pcre pdf perl png pppd python readline reflection session simplexml slang sndfile snmp speex spl sqlite3 ssl svg tcpd truetype truetype-fonts type1-fonts unicode userlocales vhosts webmin-minimal wmf x86 xml xmlrpc xorg zip zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="de" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i740 i810 imstt mach64 mga neomagic nsc nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #2) > I can confirm this bug, OpenVZ host system: Gentoo Amd64, VE's with > baselayout-1.1.13* and vserver-baselayout are running without problems sorry i meant baselayout 1.13.0_alpha12 in my comment, both times. Restoring this version of baselayout takes the networking of the VE back to life.
Well, I was excited to hear that baselayout 1.13.0_alpha12 would restore my networking; however it hasn't worked for me. I also noted the enormously increased time it takes to shut down an instance after the emerge. ff_dev 503 # vzctl enter 506 entered into VE 506 ff_pgdev / # ping 192.168.1.2 connect: Network is unreachable ff_pgdev / # emerge --info Portage 2.1.2.9 (default-linux/amd64/vserver, gcc-3.4.6, glibc-2.5-r4, 2.6.18-028stab035 x86_64) ================================================================= System uname: 2.6.18-028stab035 x86_64 Dual Core AMD Opteron(tm) Processor 280 Gentoo Base System release 1.13.0_alpha12 Timestamp of tree: Mon, 16 Jul 2007 12:30:01 +0000 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -pipe -O2" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=k8 -pipe -O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 berkdb bitmap-fonts cli cracklib crypt dri fortran iconv ipv6 isdnlog midi mudflap ncurses nls nptl openmp pam pcre perl pppd python readline reflection session spl ssl tcpd truetype-fonts type1-fonts xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i810 mach64 mga neomagic nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
(In reply to comment #4) > Well, I was excited to hear that baselayout 1.13.0_alpha12 would restore my > networking; however it hasn't worked for me. I also noted the enormously > increased time it takes to shut down an instance after the emerge. Hm, when I downgrade to baselayout 1.13* (binary or from source) and restart the VE (even without etc-update/cfg-update, I tested this a few minutes ago), networking is up again. My VE's have public IP's, using the non-bridging network mode of openvz. Perhaps the whole output of "vzctl exec 102 /etc/init.d/net.venet0 start" helps one of the developers: * Bringing down interface venet0 * Bringing up interface venet0 * 80.80.245.57/32 ... [ ok ] * Adding routes * -net 192.0.2.0/24 ... Error: an inet address is expected rather than "192.0.2.0/24". [ !! ] * default via 192.0.2.1 ... RTNETLINK answers: Network is unreachable [ !! ] The only left main difference between Paul's and my setup seems to be that he uses amd64 guests while I use x86 guests on an amd64 hardware node. I also looked at /lib/rcscripts/sh/net.sh of both baselayout versions, they are much too different for me to see a problem... but there could be one.
A workaround for this is to change /etc/vz/dists/scripts/gentoo-add_ip.sh to support the baselayout changes. Simply remove the "-net" portion of the following line. Current Line: put_param3 ${IFCFG} "routes_${VENET_DEV}" \ "-net ${FAKEGATEWAYNET}/24" # dev ${VENET_DEV} Fixed Line: put_param3 ${IFCFG} "routes_${VENET_DEV}" \ "${FAKEGATEWAYNET}/24" # dev ${VENET_DEV}
Thanks for feedback, sorry for the delay in responding. I tried the mod to gentoo-add_ip.sh as follows:- # Original line - broken by baselayout update # put_param3 ${IFCFG} "routes_${VENET_DEV}" \ # "-net ${FAKEGATEWAYNET}/24" # dev ${VENET_DEV} # Fix - remove '-net' arg... put_param3 ${IFCFG} "routes_${VENET_DEV}" \ "${FAKEGATEWAYNET}/24" # dev ${VENET_DEV} and received the following... ff_dev scripts # vzctl start 503 Starting VE ... mounting /usr/portage /vz/root/503/usr/portage VE is mounted Adding IP address(es): 10.0.0.72 bash: line 338: /etc/network/interfaces: No such file or directory bash: line 346: /etc/network/interfaces: No such file or directory cp: cannot stat `/etc/network/interfaces': No such file or directory bash: line 384: /etc/network/interfaces.bak: No such file or directory mv: cannot stat `/etc/network/interfaces.bak': No such file or directory Setting CPU units: 1000 Configure meminfo: 16388608 Set hostname: foo.bar.com VE start in progress... ff_dev scripts # ping 10.0.0.72 PING 10.0.0.72 (10.0.0.72) 56(84) bytes of data. --- 10.0.0.72 ping statistics --- 30 packets transmitted, 0 received, 100% packet loss, time 28995ms Looks like the networking is still broken. Instance still takes several minutes to shut down.
(In reply to comment #7) > and received the following... > ... > Looks like the networking is still broken. I got also the same when trying the workaround from comment #6. Also I don't think that this could be used as good fix, because some people like me are using Gentoo also on VE's on commercial providers where I cannot change anything on the hardware node. Perhaps it would be better to make a newer baselayout-vserver ? Based on 1.13 (networking) and/or 2.0 (other enhancements) ? p.s. I tried Fedora Core 5,6,7 on the same OpenVZ system as guest, all work perfectly without changing anything on the host system... Also Debian 3.x and 4.0 can be installed/started with networking and no problems, I really think Gentoo can make this too :) p.p.s. for now I still use baselayout 1.13* from local overlay without problems
I said it in commet #2, but I'll say it again - you want to be using baselayout-2. baselayout-2.0.0_rc6 is the latest available.
Why nobody closed this bug? Bottom line: we have sys-apps/baselayout-vserver or baselayout-2. baselayout-1 is masked in default-linux/{x86,amd64}/vserver and should not be used inside vservers.
