Re: [Vserver] Trivial Question #1: vreboot
Hello! /dev/initctl is a pipe created by init, so if you start an actual init inside your guest, it will create that pipe, then listen to it and once the reboot (or shutdown) calls through the pipe, issue the reboot to the kernel ... which kind of setup you use is your choice ... Hmmm so how do I supress VServers "fakeinit" and start a "real" one? The one that is running does not create the pipe: foo:/# ps faxu USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 15173 7.0 0.5 4872 1636 pts/0S03:13 0:00 /bin/bash -login root 15187 0.0 0.2 4612 872 pts/0R+ 03:13 0:00 \_ ps faxu root 1 0.0 0.1 1588 516 ?SAug05 0:01 init [2] [...] foo:/# reboot shutdown: /dev/initctl: No such file or directory init: /dev/initctl: No such file or directory It's not really that important, but staying als close to a real server as possible in the default setup would be a good choice. n8, Andreas ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Trivial Question #1: vreboot
On Fri, Aug 05, 2005 at 09:57:32PM +0200, Andreas John wrote: > Hi! > > Next time I will not hijack the thread anymore ... Well, you know I > tried to hide my trivialities inside foreign threads :) I promise! > > But for now I stay within this one ... > > >yep, as the name says /legacy/ the reboot now works > >with a kernel helper, so it is sufficient to change > >nothing at all, just call into the kernel (from the > >guest) and request a reboot (usually done by init > >or with reboot -f) > > ah "-f" does the trick I think aliassing in bashrc will > prevent most questions. > > But can't we make an /dev/initctl ? If yes, how? /dev/initctl is a pipe created by init, so if you start an actual init inside your guest, it will create that pipe, then listen to it and once the reboot (or shutdown) calls through the pipe, issue the reboot to the kernel ... which kind of setup you use is your choice ... > foo:/dev# ./MAKEDEV initctl > ./MAKEDEV: don't know how to make device "initctl" it's no device, and you can not create devices inside a guest anyways ... HTH, Herbert > rgds, > Andreas > > > > ___ > 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] Trivial Question #1: vreboot
Hi! Next time I will not hijack the thread anymore ... Well, you know I tried to hide my trivialities inside foreign threads :) I promise! But for now I stay within this one ... yep, as the name says /legacy/ the reboot now works with a kernel helper, so it is sufficient to change nothing at all, just call into the kernel (from the guest) and request a reboot (usually done by init or with reboot -f) ah "-f" does the trick I think aliassing in bashrc will prevent most questions. But can't we make an /dev/initctl ? If yes, how? foo:/dev# ./MAKEDEV initctl ./MAKEDEV: don't know how to make device "initctl" rgds, Andreas ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Trivial Question #2: What is a "context"?
On Fri, Aug 05, 2005 at 09:20:45PM +0200, Andreas John wrote: > Hello! > > my secondy trivial question is about a context. > I used context "42" for vserver build. I assume every context can be > associated with certain rights, i.e. linux capabilities. So do I have to > set an own context for every guest or do I set up a one context for > every "class" of vhost? the context id (xid) is the essential criterion for context isolation, so same xid, same context and all process will see eachother ... > So, if my first guest is called "foo" with context "42" and I create a > second one called e.g. "OBORONA" - do I set this also to conext "42" or > better a "17" to avoid access to the same devices? separate guests -> separate contexts (usually) so that they do not interfere with eachother ... HTH, Herbert PS: thread hijacking is a bad idea ... why not start your own next time (for all thos folks using a threaded mail client) > Rgds, > Andreas > > ___ > 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] Trivial Question #1: vreboot
On Fri, Aug 05, 2005 at 09:09:31PM +0200, Andreas John wrote: > Hello! > > I just built an vserver guest image with Debian etch and the bootstrap > method (with vs20 and alpaha 208 utils). I'm fiddeling around to get a > cool guest working. > > At the time I'm stuck with rebooting - I copied > /usr/lib/util-vserver/legacy/vreboot to /var/lib/vservers/foo/sbin/reboot > > but this seems to be legacy: > > foo:/# reboot > connect /dev/reboot (No such file or directory) yep, as the name says /legacy/ the reboot now works with a kernel helper, so it is sufficient to change nothing at all, just call into the kernel (from the guest) and request a reboot (usually done by init or with reboot -f) > Or did I forget to set the security "context"? > > Couldn't find the info on the wiki. I also wonder why no one made a > "util-vserver-guest.deb" with all the stuff a guest needs. because the guest does not need anything additional (and it can be installed with vserver ... build) HTH, Herbert > rgds, > Andreas > > > ___ > 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] Trivial Question #2: What is a "context"?
Hello! my secondy trivial question is about a context. I used context "42" for vserver build. I assume every context can be associated with certain rights, i.e. linux capabilities. So do I have to set an own context for every guest or do I set up a one context for every "class" of vhost? So, if my first guest is called "foo" with context "42" and I create a second one called e.g. "OBORONA" - do I set this also to conext "42" or better a "17" to avoid access to the same devices? Rgds, Andreas ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Trivial Question #1: vreboot
Hello! I just built an vserver guest image with Debian etch and the bootstrap method (with vs20 and alpaha 208 utils). I'm fiddeling around to get a cool guest working. At the time I'm stuck with rebooting - I copied /usr/lib/util-vserver/legacy/vreboot to /var/lib/vservers/foo/sbin/reboot but this seems to be legacy: foo:/# reboot connect /dev/reboot (No such file or directory) Or did I forget to set the security "context"? Couldn't find the info on the wiki. I also wonder why no one made a "util-vserver-guest.deb" with all the stuff a guest needs. rgds, Andreas ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [OBORONA-SPAM] [Vserver] newbie: testme.sh errors
Hello [eMAXX], eSA> I tried to setup an alias interface for the vserver, but I can't get it eSA> to work. SSH connections still connect at the host server. The problem you've done correct, all deamons on master host should listen certain ip - NOT 0.0.0.0 !!! bind sshd on master host ip :-) -- Matvey Gladkikh ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] newbie: testme.sh errors
Herbert Poetzl wrote: On Fri, Aug 05, 2005 at 01:20:25PM +0200, [eMAXX] Sys-Admin wrote: you have to restrict the host's sshd to host only IPs That didn't work, I must be doing something else wrong :) well update to 2.6.12.3-vs2.0-rc9 and 0.30.208 tools and the testme.sh should work as expected ... (forget about the sarge packages, they are somewhat broken) Ok I'll try that after my holiday :) The new kernel and tools could be an option, but I'll have to see how it wil fit in to the way we maintain debian systems over here and I have not used the 2.6.12 kernel, so I can't tell if it's stable (it's not even in Debian 'testing' ) Thanks for your info! Vince. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] newbie: testme.sh errors
On Fri, Aug 05, 2005 at 01:20:25PM +0200, [eMAXX] Sys-Admin wrote: > Hi there, > > I just installed Vserver on Debian Sarge mostly with the manual found here: > http://linux-vserver.org/Step-by-Step+Guide+2.6 > > I tried to setup an alias interface for the vserver, but I can't get it > to work. SSH connections still connect at the host server. The problem you have to restrict the host's sshd to host only IPs > could either be my configuration of the interface or a problem I > discovered during the installation from the test script > (http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh): > > -- > > ~# ./testme.sh > Linux-VServer Test [V0.13] Copyright (C) 2003-2005 H.Poetzl > vcontext: vc_create_context(): Invalid argument > chcontext failed! > chbind is working. > Linux 2.6.8 i686/0.30.204/0.30.204 [Ea] (0) > VCI: 0001:0025 273 8374 > --- well update to 2.6.12.3-vs2.0-rc9 and 0.30.208 tools and the testme.sh should work as expected ... (forget about the sarge packages, they are somewhat broken) > -- > > Linux 2.6.8 i686/0.30.204/0.30.204 [Ea] (0) > VCI: 0001:0025 273 8374 > --- > archer:~# vserver-info > Versions: > Kernel: 2.6.8 > VS-API: 0x00010025 > util-vserver: 0.30.204; May 24 2005, 22:22:03 > > Features: > CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-5) > CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-5) > CPPFLAGS: '' > CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W' > CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W > -fmessage-length=0' > build/host: i386-pc-linux-gnu/i386-pc-linux-gnu > Use dietlibc: yes > Build C++ programs: yes > Build C99 programs: yes > Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts >ext2fs Source: e2fsprogs >syscall(2) invocation: fast > vserver(2) syscall#: 273/glibc > > Paths: > prefix: /usr >sysconf-Directory: /etc >cfg-Directory: /etc/vservers > initrd-Directory: $(sysconfdir)/init.d > pkgstate-Directory: /var/run/vservers >Kernelheaders: /lib/modules/2.6.10-1-686-smp/build/include > vserver-Rootdir: /var/lib/vservers > -- > > I CAN enter the vserver en apt-get. Suggestions where to look now? HTH, Herbert > > Thanks! > > Regards, > > Vince. > > > > ___ > 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] newbie: testme.sh errors
Hello, [eMAXX] Sys-Admin schrieb: > Hi there, > > I just installed Vserver on Debian Sarge mostly with the manual found here: > http://linux-vserver.org/Step-by-Step+Guide+2.6 > > I tried to setup an alias interface for the vserver, but I can't get it > to work. SSH connections still connect at the host server. The problem you must set the IP in the /etc/ssh/sshd_config on the Host. ListenAddress -- MfG Karsten Horsmann ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] newbie: testme.sh errors
Hi there, I just installed Vserver on Debian Sarge mostly with the manual found here: http://linux-vserver.org/Step-by-Step+Guide+2.6 I tried to setup an alias interface for the vserver, but I can't get it to work. SSH connections still connect at the host server. The problem could either be my configuration of the interface or a problem I discovered during the installation from the test script (http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh): -- ~# ./testme.sh Linux-VServer Test [V0.13] Copyright (C) 2003-2005 H.Poetzl vcontext: vc_create_context(): Invalid argument chcontext failed! chbind is working. Linux 2.6.8 i686/0.30.204/0.30.204 [Ea] (0) VCI: 0001:0025 273 8374 --- -- Linux 2.6.8 i686/0.30.204/0.30.204 [Ea] (0) VCI: 0001:0025 273 8374 --- archer:~# vserver-info Versions: Kernel: 2.6.8 VS-API: 0x00010025 util-vserver: 0.30.204; May 24 2005, 22:22:03 Features: CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-5) CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-5) CPPFLAGS: '' CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W' CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W -fmessage-length=0' build/host: i386-pc-linux-gnu/i386-pc-linux-gnu Use dietlibc: yes Build C++ programs: yes Build C99 programs: yes Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts ext2fs Source: e2fsprogs syscall(2) invocation: fast vserver(2) syscall#: 273/glibc Paths: prefix: /usr sysconf-Directory: /etc cfg-Directory: /etc/vservers initrd-Directory: $(sysconfdir)/init.d pkgstate-Directory: /var/run/vservers Kernelheaders: /lib/modules/2.6.10-1-686-smp/build/include vserver-Rootdir: /var/lib/vservers -- I CAN enter the vserver en apt-get. Suggestions where to look now? Thanks! Regards, Vince. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Re: [Xen-users] Xen + VServer
On Fri, Aug 05, 2005 at 05:24:44PM +0900, aq wrote: > On 8/5/05, Mark Williamson <[EMAIL PROTECTED]> wrote: > > > yes, xen is just _another_ arch and once it will be in > > > mainline (IIRC they are working on it), we will of course > > > support it out of the box (as we do for UML now) > > > > Yep, they're working on it now. It's in the Real Soon Now category, > > just needs some restructuring. Of possible interest to you is that > > Xen will be a sub arch of i386 rather than a separate architecture > > when it's properly merged. IIRC only really arch dep stuff in > > Vserver is the addition of the syscalls - that code should all > > be common to Xen and i386 so you probably won't have to do much > > (anything) to support it. > > > > > > It'd be good if a reference to this patch could be added to the > > > > Xen wiki at http://wiki.xensource.com so that other people know > > > > where to find it. > > > > > > well, feel free to add links to linux-vserver or to > > > patches there ... we have a link to Xen (not the wiki) > > > on our wiki since ... hmm, well for a very long time now > > > > I saw it a while back. If Michal is agreeable (i.e. if he's > > reasonably happy with the patch) I'll make sure it goes onto the Xen > > wiki so that people can ue the two together. > > > > > well, we all would love to see linux-vserver in mainline, > > > but I guess the disadvantages of trying to get it into > > > mainline (less performant code, only partial implementation, > > > two branches to maintain) would easily outweight the > > > advantages ... > > > > Ack. In the meantime I'll continue hoping that one day we'll see the > > mainline incorporate vserver in a way that makes everyone happy :-) > > Vserver people tried to push it into mainline for several times, but > got some objections. they did? interesting ... > I heard that SElinux people were against it, as they said that they > could extend SElinux to cover Vserver function, so including Vserver > into kernel was not necessary ;-) really? well that would be nice to have ... > Looks like Vserver people dont mind it, so I guess we will not see > Vserver in mainline very soon. best, Herbert > regards, > aq ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] [PreRelease] vs2.0-rc9
On Thu, Aug 04, 2005 at 01:38:27PM -0600, Jon Scottorn wrote: > Have vs2.0 been released yet then? no, but the weekend looks promising ... > Herbert Poetzl wrote: > > >Greetings Community! > > > >this is supposed to be the last release candidate > >for the upcoming stable release 2.0 ... > > > >again, please give it a try and report back any issues > >you encounter ... we are planning to release it as > >final vs2.0 within the enxt few days ... > > > >TIA, > >Herbert > > > >http://vserver.13thfloor.at/Experimental/patch-2.6.12.3-vs2.0-rc9.diff.bz2 > >http://vserver.13thfloor.at/Experimental/patch-2.6.12.3-vs2.0-rc9.diff > >http://vserver.13thfloor.at/Experimental/split-2.6.12.3-vs2.0 > > > >___ > >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 mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
