On Mon, 27 Feb 2006 12:29:11 +0100 Eugen Leitl <[EMAIL PROTECTED]> wrote:
> I've been able to build util-vserver-0.30.210.tar.bz2 as usual > via ./configure etc., by manually resolving missing dependencies until no > more warnings occured during ./configure. i'm using util-vserver 0.30.209 backported from unstable (some weeks ago, so it's probably -1 instead of the newer -2). > However, when trying to build a vserver I'm running into the bug > described at > http://savannah.nongnu.org/bugs/?func=detailitem&item_id=13844 i don't encounter that problem on my amd64 sarge vserver host. > I presume it's an apt sources problem, since > debootstrap --arch amd64 sarge /pure64/ > http://amd64.debian.net/debian-amd64/ completes fine. What should I stick > where to make it work? here's the "vserver build" template that i use: vserver <vserver> build -m debootstrap --context <ctx> --hostname <vserver> --interface <name0>=<if0>:<ip0>/24 -- -d sarge -m http://apt-proxy:9999/debian-sarge-amd64 the backends for that apt-proxy url are (ie "http://apt-proxy:9999/debian-sarge-amd64"; is the same as...): - http://mirror.espri.arizona.edu/debian-amd64/debian - http://debian.csail.mit.edu/debian-amd64/debian (apt-proxy is worth looking into if you are running/providing/supporting multiple debian hosts, real or virtual. i can provide an example apt-proxy-v2.conf and a sources.list that references the apt-proxy server.) to merge my template with your usage (or rather herbert's example in the bug report): vserver test101 build -m debootstrap --hostname t101.foo.org --context 101 --interface hansi=dummy0:192.168.0.101/16 -- -d sarge -m http://bach.hpc2n.umu.se/debian-amd64/debian if that doesn't work, i'd attribute the problem to the util-vserver version (as 0.30.209 works for me). > I'm still not sure whether I should stick with an unsupported AMD64 Sarge > or go with a vanilla i386 Sarge (the machine only has 4 GBytes) -- i.e. > will it hurt performance badly? 2 GByte/process limit won't bite, will > absence of twice as many registers in AMD64 mode? But gcc-3.3/gcc-3.4 > doesn't support AMD64 all that well anyway, right? i don't personally have benchmark numbers (have yet to install a i386 guest), but the performance reported by others (due to the extra registers) is the entire reason i purchased amd64 hardware, waiting until debian had a stable/"sarge" amd64 release. you might be able to get a comparable speed-up on amd64 with a 32-bit kernel and/or user-land by recompiling all packages with a more specific -mtune (ie 32-bit instruction set but including scheduling, MMX, SSE, SSE2 support) than debian's i386 packages (ie -mtune=i486), but i'll leave that trouble to gentoo users. ;-) corey -- [EMAIL PROTECTED] _______________________________________________ Vserver mailing list [email protected] http://list.linux-vserver.org/mailman/listinfo/vserver
