[Vserver] When to mount lvm? (vs2.0)
Hi, I'm not sure where to mount an LVM2 device with vs2.0. I do not want to mount it on system boot, but when starting the guest vserver. The fstab file in the vserver config directory seems to be the right place. But when including an entry like this in the fstab file, the mount won't show up in the hostsystem and will not be accessible via the mount point in the /vservers directory: /dev/mapper/vg-test01 / ext3 defaults 1 2 But I'm able to enter the vserver with vserver test01 enter, weird. I also tried the prepre-start script, but it seems to be the wrong place, because it's called after the generateOptions function. Any hints? Best, Lars ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] When to mount lvm? (vs2.0)
On Tuesday 13 December 2005 07:38 am, Lars Braeuer wrote: Hi, I'm not sure where to mount an LVM2 device with vs2.0. I do not want to mount it on system boot, but when starting the guest vserver. The fstab file in the vserver config directory seems to be the right place. good question. i run lvm2 and i have found on my system, if i want to be able to administer the guest directly from the host, i must mount it on boot or create a special script to start the guest which mounts the lvm2 mountpoint, then calls vserver to start the guest. if i do not do this, then i cannot administer the guest from the host and must enter the guest to do anything at all. will be interesting to see what the gurus say :) But when including an entry like this in the fstab file, the mount won't show up in the hostsystem and will not be accessible via the mount point in the /vservers directory: /dev/mapper/vg-test01 / ext3 defaults 1 2 But I'm able to enter the vserver with vserver test01 enter, weird. I also tried the prepre-start script, but it seems to be the wrong place, because it's called after the generateOptions function. Any hints? Best, Lars ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver -- Chuck ...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] When to mount lvm? (vs2.0)
Chuck wrote: On Tuesday 13 December 2005 07:38 am, Lars Braeuer wrote: Hi, I'm not sure where to mount an LVM2 device with vs2.0. I do not want to mount it on system boot, but when starting the guest vserver. The fstab file in the vserver config directory seems to be the right place. good question. i run lvm2 and i have found on my system, if i want to be able to administer the guest directly from the host, i must mount it on boot or create a special script to start the guest which mounts the lvm2 mountpoint, then calls vserver to start the guest. if i do not do this, then i cannot administer the guest from the host and must enter the guest to do anything at all. will be interesting to see what the gurus say :) so you are doing it the same way, via the fstab config file? it seems like the device is mounted right until after the vserver is up. I included a ls -la /vservers/test01/ ; df -a in the prepre-start script and it actually outputs a listing of the guest system. This might be from a different ctx (i.e. 1)??? Because after the guest system is started, and I return to the normal hostsystem shell, a ls -la /vservers/test01 outputs an empty directory. But when including an entry like this in the fstab file, the mount won't show up in the hostsystem and will not be accessible via the mount point in the /vservers directory: /dev/mapper/vg-test01 / ext3 defaults 1 2 But I'm able to enter the vserver with vserver test01 enter, weird. I also tried the prepre-start script, but it seems to be the wrong place, because it's called after the generateOptions function. Any hints? Best, Lars ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] When to mount lvm? (vs2.0)
On Tuesday 13 December 2005 08:03 am, Lars Braeuer wrote: Chuck wrote: On Tuesday 13 December 2005 07:38 am, Lars Braeuer wrote: Hi, I'm not sure where to mount an LVM2 device with vs2.0. I do not want to mount it on system boot, but when starting the guest vserver. The fstab file in the vserver config directory seems to be the right place. good question. i run lvm2 and i have found on my system, if i want to be able to administer the guest directly from the host, i must mount it on boot or create a special script to start the guest which mounts the lvm2 mountpoint, then calls vserver to start the guest. if i do not do this, then i cannot administer the guest from the host and must enter the guest to do anything at all. will be interesting to see what the gurus say :) so you are doing it the same way, via the fstab config file? it seems like the device is mounted right until after the vserver is up. I included a ls -la /vservers/test01/ ; df -a in the prepre-start script and it actually outputs a listing of the guest system. This might be from a different ctx (i.e. 1)??? Because after the guest system is started, and I return to the normal hostsystem shell, a ls -la /vservers/test01 outputs an empty directory. for the most part i mount them on boot. i have one guest that i dont want mounted until i use it, so i have a special script i run when i want to use that guest which mounts the lvm mount point then calls vserver to start the guest so the mount point is visible in the host until i stop the guest, then the script unmounts it after stopping the guest. its just a specialized init script. But when including an entry like this in the fstab file, the mount won't show up in the hostsystem and will not be accessible via the mount point in the /vservers directory: /dev/mapper/vg-test01 / ext3 defaults 1 2 But I'm able to enter the vserver with vserver test01 enter, weird. I also tried the prepre-start script, but it seems to be the wrong place, because it's called after the generateOptions function. Any hints? Best, Lars ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver -- Chuck ...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. The Book of John, chapter 1, page 1, and end of book ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] vs1.2.11 and vs2.0.1 ?
Hello, During the hollydays I will take some of our servers off-line for maintenance. So, it's a good moment to think about a kernel upgrade. At http://vserver.13thfloor.at/Experimental/ , I found some test releases. Which kernel version should I use? Some servers runs 2.4.30-vs1.2.10 (yes I know it's old, but the users don't want to migrate to the new util-vserver configuration) Other servers run 2.6.12.4-vs2.0 Should we stick to the vserver releases, or is it a good idea to use the latest rc patches? Thanks for your help, Bert. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] When to mount lvm? (vs2.0)
On Tuesday 13 December 2005 13:46, Chuck wrote: On Tuesday 13 December 2005 07:38 am, Lars Braeuer wrote: Hi, I'm not sure where to mount an LVM2 device with vs2.0. I do not want to mount it on system boot, but when starting the guest vserver. The fstab file in the vserver config directory seems to be the right place. good question. i run lvm2 and i have found on my system, if i want to be able to administer the guest directly from the host, i must mount it on boot or create a special script to start the guest which mounts the lvm2 mountpoint, then calls vserver to start the guest. if i do not do this, then i cannot administer the guest from the host and must enter the guest to do anything at all. will be interesting to see what the gurus say :) Not a guru answer : the mount points doesn't appear in the host because they are in a different namespace. Each vserver has its own namespace. Namespaces are a linux VFS feature. A process being in one namespace doesn't have the same view of the mounted filesystems as another process being in another namespace. http://linux-vserver.org/Namespaces So if you want to see the mount points of a vserver from the host (be careful, the paths don't take into account the chroot) : vnamespace vserver cat /proc/mounts When you enter a vserver, the new shell is in the same namespace as the vserver, so you can also administer it. -- Xavier Montagutelli Service Commun Informatique Universite de Limoges Tel : +33 555457720 Cle GPG : http://pgp.mit.edu 1024D/175CE198 ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] When to mount lvm? (vs2.0)
[EMAIL PROTECTED] (Lars Braeuer) writes:
I'm not sure where to mount an LVM2 device with vs2.0. I do
not want to mount it on system boot, but when starting the
guest vserver.
The fstab file in the vserver config directory seems to be the right place.
But when including an entry like this in the fstab file, the mount
won't show up in the hostsystem and will not be accessible via the
mount point in the /vservers directory:
/dev/mapper/vg-test01 / ext3 defaults 1 2
I would recommend to do physical mounting in the host's /etc/fstab
and bind-mount it in the vserver's fstab. E.g.
| [/etc/fstab]
| /dev/mapper/vg-test01 /srv/mnt/test01 ext3 defaults 1 2
| [/etc/vservers/.../fstab
| /srv/mnt/test01/ none bind
This gives the advantage that the partition will be fsck'ed
during the regularly system boot and that you can share it
between multiple vservers ('mount' is allowed only once per
physical partition but you can 'mount --bind' multiple times).
But I'm able to enter the vserver with vserver test01 enter,
weird.
Expected namespace behaviour...
Enrico
pgpPuXyODs6mp.pgp
Description: PGP signature
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] memory problems?
On Mon, 2005-12-12 at 18:41 +0100, Herbert Poetzl wrote: On Mon, Dec 12, 2005 at 07:34:01PM +0200, Roché Compaan wrote: On Mon, 2005-12-12 at 18:19 +0100, Herbert Poetzl wrote: On Mon, Dec 12, 2005 at 07:13:46PM +0200, Roché Compaan wrote: On Mon, 2005-12-12 at 16:53 +0100, Herbert Poetzl wrote: On Mon, Dec 12, 2005 at 03:34:13PM +0200, Roché Compaan wrote: On Mon, 2005-12-12 at 03:06 +0100, Herbert Poetzl wrote: On Sun, Dec 11, 2005 at 10:28:04PM +0200, Roché Compaan wrote: On Sun, 2005-12-11 at 11:34 -0800, Alexander Kabanov wrote: hi, i'm having similar errors (I do have limits and scheduler set, using rlimits (as, rss, nproc) and scheduler) whenever i do stress testing, (overloading mta or web server for example). during a stress test, some applications die because of no memory available or can't fork, some stop with segmentation fault (not able to do vserver vs enter),. when attacking httpd might have httpd defunct. I am experiencing the same problems. The segfaults and not being able to enter a vserver from the host *really* worries me. well, if the limits are reached, the guest can not create new processes and/or instantiate more memory ... of course this might lead to program termination and the fact that a guest cannot be entered (as the limits are hard limits). raising them will make it all work again ... If the vserver is hitting the limit then I'm less worried because I can solve the problem by increasing the limit. I misread and thought that there was plenty of memory to spare. Would I be right in assuming that increasing only the virtual memory will solve the problem? probably that will solve 80% of the issues (see VM vs RSS hit ratio) Where? in the original email you sent (you removed the lines so I could not refer to them ...) Ah, thanks. I don't mind if virtual servers use swap space if they need memory because we have plenty of disk space, but I don't want them to consume all the physical memory on the box. trust me, you do mind as soon as the guests start swapping in and out ... Sorry, you'll have to explain - I don't understand how the vserver or the linux kernel manages virtual memory or what you mean when you say swapping in and out. consider a total of 256 MB memory (RAM) on the host further, consider three guests with a memory footprint of 128MB RSS (means they need to have 128MB in memory to run, that's what Resident Set Size is), now they are alternating and will constantly swap in and out memory, because 3*128 256 ... But what if I limit the sum of virtual server RSS limits to never exceed the total RAM on the host as a rule, and make sure that there is enough virtual memory for all of them? Ie. I have 4 GB RAM on the host and 4 vservers that each have a hard limit of 1 GB RSS and say triple the virtual memory. Would I still get memory errors when vservers reach the RSS limit, or only when they reach the VM limit? assumed that the guests use the RSS equally, you will not get any over RSS limit hits, as the pages will be swapped out when (or slightly before) they reach the limit (but in reality, one or the other guest will try to use slightlly more and will hit the hard limit ...) It seems like the most responsible thing to do now is to abandon hard limits (and wait for soft limits) and babysit vservers in the mean time. Processes that take up to match memory can then either be restarted or killed manually, rather than allowing the kernel to make that decision. -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] VServer seems to work fine basicaly on hppa too ; -) (just some question)
Hello All, Great the kernel was booting fine; just grep the upstream util-vserver tools and hack lib/syscall-faalback.h to match __NR_vserver 263 for hppa to build it with default debian pkg configure options ;-) As I already had some chroot disks that I used for severall test (glibc, ...) and I wouldn't like to re-install a debian debootstrap, I use a vserver build -m skeleton ;-) and gather some more info to start my vserver named DebSid: # vserver-stat CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME 0 68 134.3M 49.3M 7m32s62 28m01s19 4h14m54 root server 49153 15 76.8M 22.5M 0m05s31 0m14s53 2h47m02 DebSid enter it too: # ps -ef UIDPID PPID C STIME TTY TIME CMD root 1 0 0 14:05 ?00:00:52 init [2] root 5294 1 0 14:05 ?00:00:00 /sbin/syslogd 103 5318 1 0 14:05 ?00:00:00 /usr/bin/dbus-daemon-1 --system root 5340 1 0 14:05 ?00:00:00 /usr/bin/netserver root 5355 1 0 14:05 ?00:00:02 /usr/bin/X11/xfs -daemon root 5367 1 0 14:05 ?00:00:00 /usr/sbin/xinetd -pidfile /var/run/xinetd.pid -stayalive daemon5408 1 0 14:05 ?00:00:00 /usr/sbin/atd root 5411 1 0 14:05 ?00:00:00 /usr/sbin/cron root 5426 1 0 14:05 ?00:00:00 /usr/sbin/gdm root 5704 5693 0 14:37 pts/100:00:01 /bin/bash -login root 6418 1 0 15:51 ?00:00:00 /usr/sbin/sshd root 6421 6418 0 15:52 ?00:00:00 sshd: jso [priv] jso 6423 6421 0 15:52 ?00:00:00 sshd: [EMAIL PROTECTED]/6 jso 6424 6423 0 15:52 pts/600:00:00 -bash root 6434 6424 0 15:52 pts/600:00:00 su - root 6435 6434 0 15:52 pts/600:00:00 -su root 7573 5704 0 17:02 pts/100:00:00 ps -ef and after stolen an ipv4 address and configure nic, ssh, ...: ssh 10.24.252.111 Linux patst007 2.6.15-rc1-pa3-d32up #8 Mon Nov 14 13:01:04 CET 2005 parisc GNU/Linux The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. You have new mail. Last login: Tue Dec 13 15:50:52 2005 from wsjso.internal.mce.org debvs007:~ $ su - Password: [EMAIL PROTECTED]:~# ls -lrt total 24 drwx-- 2 root root 4096 Nov 23 2003 Mail -rw-r--r-- 1 root root 26 Apr 20 2005 Vjso drwxr-xr-x 2 root root 4096 Oct 5 15:26 tmp drwxr-xr-x 2 root root 4096 Oct 5 15:51 var drwxr-xr-x 2 root root 4096 Nov 3 19:09 bin drwxr-xr-x 2 root root 4096 Dec 13 14:19 Man [...] (well just basics, I still have to see which startup script I need to start/stop at the reboot/shutdown and other stuff I would like to test as xdmcp, ...) The additional question is (may be non sense but thought): those chroot disk was also bootable, so if I want to reboot I would just have to write and run a script which will would restore /dev /etc/init.d and corresponding rc?.d? Or is it possible to instruct vserver to use better a /dev.vserver as well as /etc/init.d.vserver, ...? Or doesn't it make any more sense at all because of vserver itself? Thanks again for all help, Joel --- NOTE! My email address is changing to ... @scarlet.be Please make the necessary changes in your address book. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] [Release] Stable 2.01
Greetings Community! we proudly present the second stable release of linux-vserver for the 2.6 kernels ... the following fixes and changes were done: * bugfix for task/load accounting * bugfix for interface visibility * fixed endianess issue with loopback * fixed reiserfs attribute handling * utsname fix for ppc64 (tx Serge) * corrected scheduler return codes * proper module support for vroot * dlimit cleanup and improvements * extended and cleaned up debug features * cleanup of the attribute layer * various code cleanups ... * added ioprio support you can get patches and tools here: http://www.13thfloor.at/vserver/s_rel26/v2.01/ enjoy, Herbert ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] vs1.2.11 and vs2.0.1 ?
On Tue, Dec 13, 2005 at 02:24:21PM +0100, Bert De Vuyst wrote: Hello, During the hollydays I will take some of our servers off-line for maintenance. So, it's a good moment to think about a kernel upgrade. At http://vserver.13thfloor.at/Experimental/ , I found some test releases. Which kernel version should I use? Some servers runs 2.4.30-vs1.2.10 (yes I know it's old, but the users don't want to migrate to the new util-vserver configuration) Other servers run 2.6.12.4-vs2.0 Should we stick to the vserver releases, or is it a good idea to use the latest rc patches? the strategical delay in answering that question, now allows me to say, please use the second stable release for 2.6 kernel (vs2.01) ... best, Herbert Thanks for your help, Bert. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] [ANNOUNCE] second stable release of Linux-VServer
Well, as the OpenVZ folks announced their release on LKML I just decided to do similar for the Linux-VServer release, so please let me know if that is not considered appropriate. Short Overview: Linux-VServer, a soft partitioning concept based on Contexts (Process, Network and Filesystem Isolation) which permits the creation of many independent Virtual Private Servers (VPS) that run simultaneously on a single physical server at full speed, efficiently sharing hardware resources. A VPS provides an almost identical operating environment as a conventional Linux Server. All services, such as ssh, mail, Web and databases, can be started on such a VPS, without (or in special cases with only minimal) modification, just like on any real server. The Project is following the kernel development very closely, and provides Stable as well as Development patches for 2.6 and 2.4 vanilla kernels. (more details can be found at http://linux-vserver.org/) The patch is available here: http://www.13thfloor.at/vserver/s_rel26/v2.01/ For the lkml folks, the broken out version of the patch is probably most interesting (if there is some detailed interest, I'll comment on the patches ...) http://www.13thfloor.at/vserver/s_rel26/v2.01/split-2.6.14.3-vs2.01.tar.bz2 (IMHO too huge to attach them inline) best, Herbert ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] VServer seems to work fine basicaly on hppa too ; -) (just some question)
On Tue, Dec 13, 2005 at 05:20:22PM +0100, Joel Soete wrote: Hello All, Great the kernel was booting fine; just grep the upstream util-vserver tools and hack lib/syscall-faalback.h to match __NR_vserver 263 for hppa to build it with default debian pkg configure options ;-) As I already had some chroot disks that I used for severall test (glibc, ...) and I wouldn't like to re-install a debian debootstrap, I sounds reasonable ... use a vserver build -m skeleton ;-) and gather some more info to start my vserver named DebSid: # vserver-stat CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME 0 68 134.3M 49.3M 7m32s62 28m01s19 4h14m54 root server 49153 15 76.8M 22.5M 0m05s31 0m14s53 2h47m02 DebSid enter it too: # ps -ef UIDPID PPID C STIME TTY TIME CMD root 1 0 0 14:05 ?00:00:52 init [2] root 5294 1 0 14:05 ?00:00:00 /sbin/syslogd 103 5318 1 0 14:05 ?00:00:00 /usr/bin/dbus-daemon-1 --system root 5340 1 0 14:05 ?00:00:00 /usr/bin/netserver root 5355 1 0 14:05 ?00:00:02 /usr/bin/X11/xfs -daemon root 5367 1 0 14:05 ?00:00:00 /usr/sbin/xinetd -pidfile /var/run/xinetd.pid -stayalive daemon5408 1 0 14:05 ?00:00:00 /usr/sbin/atd root 5411 1 0 14:05 ?00:00:00 /usr/sbin/cron root 5426 1 0 14:05 ?00:00:00 /usr/sbin/gdm root 5704 5693 0 14:37 pts/100:00:01 /bin/bash -login root 6418 1 0 15:51 ?00:00:00 /usr/sbin/sshd root 6421 6418 0 15:52 ?00:00:00 sshd: jso [priv] jso 6423 6421 0 15:52 ?00:00:00 sshd: [EMAIL PROTECTED]/6 jso 6424 6423 0 15:52 pts/600:00:00 -bash root 6434 6424 0 15:52 pts/600:00:00 su - root 6435 6434 0 15:52 pts/600:00:00 -su root 7573 5704 0 17:02 pts/100:00:00 ps -ef and after stolen an ipv4 address and configure nic, ssh, ...: ssh 10.24.252.111 Linux patst007 2.6.15-rc1-pa3-d32up #8 Mon Nov 14 13:01:04 CET 2005 parisc GNU/Linux excellent, so the patch worked fine for you on 2.6.15-rc1-pa3? could you give the testme.sh and testfs.sh a spin on that machine? The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. You have new mail. Last login: Tue Dec 13 15:50:52 2005 from wsjso.internal.mce.org debvs007:~ $ su - Password: [EMAIL PROTECTED]:~# ls -lrt total 24 drwx-- 2 root root 4096 Nov 23 2003 Mail -rw-r--r-- 1 root root 26 Apr 20 2005 Vjso drwxr-xr-x 2 root root 4096 Oct 5 15:26 tmp drwxr-xr-x 2 root root 4096 Oct 5 15:51 var drwxr-xr-x 2 root root 4096 Nov 3 19:09 bin drwxr-xr-x 2 root root 4096 Dec 13 14:19 Man [...] (well just basics, I still have to see which startup script I need to start/stop at the reboot/shutdown and other stuff I would like to test as xdmcp, ...) The additional question is (may be non sense but thought): those chroot disk was also bootable, so if I want to reboot I would just have to write and run a script which will would restore /dev /etc/init.d and corresponding rc?.d? well, it might be an option to use udev to populate the dev (on a real boot) and just clense them before you use it as guest ... Or is it possible to instruct vserver to use better a /dev.vserver as well as /etc/init.d.vserver, ...? you could also do some --bind mounting on guest startup (see pre/post scripts and fstab) and of course if security is not an issue for your guests, you could also let them run with the fully populated /dev HTH, Herbert Or doesn't it make any more sense at all because of vserver itself? Thanks again for all help, Joel --- NOTE! My email address is changing to ... @scarlet.be Please make the necessary changes in your address book. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
