Re: [Vserver] is there any getting started with vserver documentation anywhere?
I once tried to make the vservers run on a SuSE disto but after serveral weekends gave up. That's basically due to my lack of ability to compile a vanilla kernel on SuSE so that all the modules it has with its standard kernel work. We run vservers under Debian 3.0 (Woody) without any problems. The normal vservers (without setting disk-space limits and without setting the context number :-)) are simple: I started with the introduction by Jacques (in april, I think) and worked up my way through the other docs in mentioned http://linux-vserver.org. Astonishingly there's not really much to do to run vservers: patching, compiling and installing the kernel, getting the tools of choice (either from the Debian distro or Enrico's util-vserver), setting up a vserver, do a vserver xxx start and that's it... As a kernel I use whatever is currently regarded as stable (on the long running system 2.4.18, on the systems to-be-set-up 2.4.22) and where the developers provide a patch. I found it to be very stable, relatively easy to install and extremely useful! Alexander Am Mittwoch, 5. November 2003 05:31 schrieb ian douglas: Considering RedHat's recent press release about discontinuing the RedHat Linux line in favor of the more expensive enterprise version, I'd really like a few answers from others (only had one off-list reply) regarding which operating system is going to be my best bet since I'm going to have to convert my server to another Linux distro now. I'll be starting a whole new server to manage everything but curious, obviously, which distro people have had the most success with other than RedHat. Thanks for any help on that, as well as my other unanswered questions. -id I searched the site's documentation and found the multi-page this is what it's capable of documentation, but didn't see any offhand that answered the following questions. I sent them to Jacques, but I'd like to pose it to the list in general for the 1.0 release so I can get started on vserver in the coming weeks. --- Hi Jacques, I've been daydreaming about a vserver setup for my system. A few things that perhaps would be handy to have in the FAQ: - what OS works 'best'? Kernel version is obviously important, but it would be neat to see some sort of volunteered information from various users as to the OS and version of that OS, that they have the most success with - how does one get started? is it best to start with a totally fresh machine and build from there, or could I start from a medium-sized virtual hosting setup using Linuxconf and build a vserver and go from there? I guess I'm looking for guidance on what should/should not get copied over when building the first vserver - once I build the first one, I can just use the vserver software to duplicate it, but I'm worried about disk space and how to actually mount/share file system areas... - any patched versions of up2date out there? or would I have to tell up2date to save a copy of the RPM's on the disk somewhere and run the vserver rpm utility to patch all vservers? If I have 100 vservers, is there a quicker way to tell it to patch all vservers, or would I have to literally type rpm server1 server2 server3 ... server99 server100 -Uvh *rpm ? --- Thanks for any additional feedback. -id ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver -- --- [EMAIL PROTECTED] tel.: +49 (0)30 / 61 20 26 87 fax: +49 (0)30 / 61 20 26 89 --- lieblinxNET we do software a Marwood Thiele GbR --- reichenberger straße 125 10999 Berlin http://lieblinx.net --- ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] NFS problems with vs1.00
There seems to be a problem with using nfs shares in a vserver with
vs1.00. It appears that it is related to file locking.
The share is mounted like this in the vserver startup script:
/usr/sbin/chbind --ip 192.168.1.145 --bcast 192.168.1.255 mount
-t nfs fileserver:/home /var/lib/vservers/$2/home
After mounting the share it seems to work correctly (cd/ls/touch showing
no problems).
When I start a process (in my case it's eclipse in jvm 1.4.1) which tries
to lock a file on that nfs share, it goes to state D ('uninterruptible
sleep') and cannot be killed. Any other process which tries to access the
share goes to state D as well.
hmm, could you try to reproduce this without eclipse/jvm?
(some small C programm or perl script will do)
I could track down the problem to the fcntl64 syscall.
Strace output:
10:36:19 fcntl64(3, F_SETLKW64, {type=F_WRLCK, whence=SEEK_SET, start=0,
len=0}
I attached a small perl script to reproduce this.
After that syscall the process goes to state D and if the lock would be
granted by the nfs server (if it is not locked already), there is no further
access possible to that nfs share, even umount -f does not work.
As far as I can tell, if the file is already locked by another process, it
just waits, as I would expect.
This problem does not appear in ctx-17c (the last version I tried
before), although the first three syslog messages appear as well.
maybe the patch isn't the only variable in this game,
maybe you patched another (newer?) kernel with v1.00?
(sorry I forgot to include the versions):
Both 2.4.22, same .config, just the vserver patch is different.
Host is debian stable/woody, vserver is debian unstable/sid.
Thank you,
Jan
--
#!/usr/bin/perl
use Fcntl;
open FH, locktest.lock or die Cannot open $fn: $!;
flock FH, 2;
print flock works...\n;
print Testing fcntl...\n;
@list = (F_WRLCK,0,0,0,0); # exclusive write lock, entire file
$struct = pack(SSLLL,@list);
fcntl(FH,F_SETLKW,$struct) or die(cannot lock because: $!\n);
# With vs1.00 I don't get here
print FH blabla;
close FH;
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] is there any getting started with vserver documentation anywhere?
At 13:53 05.11.2003, you wrote: Charles Dale wrote: Re: compiliing a kernel on SuSE, they should provide a .config file that has all the configuration options used for compiling the stock kernel. With RedHat this is in the config/ directory inside the kernel tree. Looking at a SuSE source RPM I can't see anything similar. Hmm. On redhat, if the config is in that directory, what is the config file in /boot ? The other thing: I might be wrong with this, but: Isn't it the case that redhat provides a patched kernel ? I could not fine the whole source kernel. Finally I used a standard vanilla kernel (which I still have little problems with). I could only find some kernel-xxx.src.rpm, but which only installs some other directory structure, not like it would be with a vanilla kernel. Ages ago I searched for the same for rh7.3, that days it was seperated, I also had to install kernel-headers etc..., but I can't find these things for rh9. Hints are appreaciated ! JH ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] is there any getting started with vserver documentation anywhere?
Ages ago I searched for the same for rh7.3, that days it was seperated, I also had to install kernel-headers etc..., but I can't find these things for rh9. I think running a vanilla kernel on rh9/rhel3 is not a good idea (this was what I found with taroon at least) - the red hat kernel has NPTL (native posix thread library) support patched in, and a lot of userspace things expect this kernel support to be there. If you run a vanilla kernel (which won't have NPTL) then you will see problems with threaded apps. Unfortunately the vserver patches won't patch (yet) against the red hat patched kernels. Just to get this right: - vanilla kernel should not be used on redhat - vserver does not patch redhat kernel yet ? It looks a bit like there is no straight way using redhat9 with vserver, am I right with this conclusion ? Anyway, if you still know the place of the kernel sources, I'd still like to know, as I can't find them. And I guess at some point there will be patches for the redhat kernel. What would be the way to go ? Use debian as the host, and maybe use rh vservers ? I'd like to use redhat for some things as I know about it. Just looking into debian... thanks, JH ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
RE: [Vserver] Red Hat kernels (NPTL)
On Thursday, November 06, 2003 10:28 AM NZT, Jan-Hendrik Heuing [EMAIL PROTECTED] wrote: It looks a bit like there is no straight way using redhat9 with vserver, am I right with this conclusion ? Correct... that's assuming redhat9 uses NPTL, I'm pretty sure it does but somebody correct me if I'm wrong... Yes the RH kernel's got NPTL, but I'm using RH9 with a vanilla kernel fine here. That's probably because I'm not using any threaded apps, and my main vserver is running RH6.2 (legacy). There aren't many standard apps that would be threaded, you'd be more talking Java/threaded Apache/etc, so NPTL is only an issue if you actually use threaded apps. Anyone know which standards apps threads? As to the O(1) scheduler well that doesn't really matter too much - it just means you'll get worse performance, everything should work fine without it. Herbert's got O(1) scheduler patches for 2.4 if you want it though. Also you could _possibly_ rip the RedHat NPTL patches out of their kernel SRPM and apply them to a vanilla 2.4.22 kernel. Looking at the spec file you'd need these patches: # threading backport and O(1) scheduler backport; # last because they need to # be ifarch'd and touch a lot of code Patch11000: linux-2.4.20-o1-sched+threading-backport.patch Patch11001: linux-2.4.20-noresched.patch Patch11002: linux-2.4.20-futex-debug.patch Patch11003: linux-2.4.20-softlockup.patch Patch11004: linux-2.4.20-ptrace.patch Patch11005: linux-2.4.22-security-nptl.patch Patch11006: linux-2.4.20-ntpl-signal-delivery-fix.patch Patch11030: linux-2.4.20-noscheduler.patch Patch11031: linux-2.4.20-ptrace-hammer.patch Patch11032: linux-2.4.22-security.patch Still, it would probably get ugly pretty quickly. Anyone up for porting the v1.0 vserver patch to a Red Hat kernel? There'd be lots of happy customers =) ... Chuck ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Vserver rpm errors
Hi. I'm getting RPM errors on all new vserver RPMs (using RH9): error: vserver-0.26-1.i386.rpm: rpmReadSignature failed: region trailer: BAD, tag 61 type 7 offset 48 count 16 error: vserver-0.26-1.i386.rpm cannot be installed Any ideas? Kind regards, Lucian Kafka www.conexim.com.au ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
