1381017715 M * user-K Aiken, thank you for sharing that. I was able to find a solution to the problem using your suggestion for rescue mode after creating the guest with an interface with a route to the internet. Problem solved simply at that point. 1381017784 M * Aiken I suggest once you have a basic image you are happy with then use that to make a template instead of the stage3 1381017789 M * Aiken will make it simpler next time 1381018169 M * user-K Where do I find the instructions for adding more network interfaces to an existing guest? I beleive it is done from the vserver host. 1381018242 M * user-K I have a guest with need for multiple interfaces, do some bridging, etc. 1381018246 M * Bertl you cannot add interfaces per se, they will show up in the guest when they carry an IP assigned to the guest 1381018301 M * Bertl the default Linux-VServer guest uses (network) isolation, so you are basically using the host stack to transport guest data 1381018335 M * Bertl if you want/need a separate stack for your guest, you have to configure network namespaces 1381018429 M * user-K where is instruction to assign IPs to guest aside from the option made when it was first created? 1381018481 M * Bertl on the flower page, i.e. just add the necessary configuration files to the guest configuration tree (when the guest is stopped) and you will get whatever you configured 1381018521 M * user-K /etc/vservers//interfaces 1381018522 M * Bertl for adding IPs, just create another subdirectory in /etc/vservers//interfaces (e.g. '1') with similar entries like you have in '0' 1381018649 M * Aiken the stage3 I just downloaded already has sshd installed, all it needed was the net.eth0 symlink and rc-update add ssh default 1381018652 Q * thierryp Read error: Connection reset by peer 1381018677 J * thierryp ~thierry@home.parmentelat.net 1381020123 M * user-K Aiken, yes, it has that included, and the sshd daemon initially needed a working net to play nicely. 1381020159 M * user-K at least that is how it appeared to me. 1381020387 M * Aiken I created the net.lo -> net.eth0 symlink 1381020441 M * Bertl it sounds a little odd to me that there is no syslog configured in stage3, but maybe that's how the gentoo folks prefer it 1381020444 M * user-K configuring the sshd_config needs a terminal too, which rescue mode did not provide me 1381020600 M * Aiken all I needed to get the stage 3 working was the symlink for net.eth0 and rc-update for sshd which --rescue bash was enough for 1381020765 M * user-K Aiken, you are my here now. I used a hardened stage 3 yesterday, and perhaps my ssh requirements are more stringent than you have. In any case, the problem was solved after some fiddling anyway, thanks to your pointer about rescue mode in part. 1381020787 M * user-K * my hero 1381022448 M * user-K In my guests /etc/vservers/interface were created only bcast and mask files during creation although I had specified the name of the physical interface as well, using the "--netdev" option (unless perhaps I had removed it on the second go around when if failed to work as I had expected it would. It is important to me that only this device be used for this purpose, and none of the others. 1381022518 M * user-K I need to associate this particular device with this IP now. 1381022545 M * Bertl you usually specify the device with the --interface option (like eth0:xxx) 1381022571 M * Bertl note that this will only be the interface util-vserver will add the given IP to (as I explained before) 1381022608 M * user-K Yes, I thought that I did it that way during creation, as I mentioned. Now that it exists, the IP, can I make such an association after the fact? 1381022638 M * Bertl sure, make sure the guest is stopped, add the 'dev' entry containing your interface 1381022870 M * user-K Bertl, I still need to get a better feel for what commands, etc., can be done to the guest only from outside of it, i.e., from the host command line. 1381022919 M * Bertl think of it like this: normally a system has a stage where hardware is configured (like devices, disks, networks, etc) 1381022939 M * Bertl and then there is a stage where services get started (ssh, cron, syslog, ...) 1381022987 M * user-K somewhat like the run levels 1381022989 M * Bertl basically everything device, mount, and network related as well as many 'per guest' limits are only configureable from outside the guest (admin) 1381023017 M * Bertl everything service related happens inside the guest (i.e. inside the isolation context) 1381023045 M * Bertl this makes Linux-VServer guests almost hardware ignostic 1381023045 M * user-K okay, that paradigm is helpful generally. 1381023048 M * Bertl *agnostic 1381023081 M * Bertl i.e. it allows you to move a guest from hostA to hostB even if they have completely different hardware, as long as they are binary compatible 1381023118 M * Bertl think i386 with scsi disks and 100Mbit 3com ethernet card, containing a guest 1381023141 M * user-K yet, I look inside this guest, for instance, and I see "resolv.conf", which is part-and-parcel with networking services. 1381023148 M * Bertl now you move to a different host, which is x86_64, has SATA disks and a 1GBit intel card 1381023182 M * Bertl all you need to change is a single entry telling the system that the guest should be considered 32bit (which isn't even necessary in many cases) 1381023620 M * user-K Bertl, back to my question on the networking devices, at this point I see only this command, vserver-build, where the option "netdev" is mentioned in a manual. Yet, with that command there appears also an option for method of creation, namely, "-m method", which would seem to be only for creation of a guest, not maintenance, and it is mandatory parameter. 1381023900 M * user-K I read a portion of the manual yesterday, where it indicated that guests could be made from existing physical systems, merely by copying over much of the content, cutting a part away here and there. Is that method successful in most cases? 1381023964 M * user-K Seems to me that it would be advenageous to make use of the settings, etc, already configured, if possible. 1381025663 M * user-K what happened to Bertl? I stepped away myself... Did I miss something? 1381026702 M * Bertl still here, although I'm almost off to bed 1381026739 M * Bertl yes, you can use for example the rsync build method to copy the data from an existing system 1381026835 M * Bertl but note that you still have to configure stuff like IPs and limits and in most cases you also need to modify services inside the guest to address the fact that certain hardware related setup procedure are not possible inside the guest 1381026844 M * Bertl (mainly because they happen on the host) 1381026883 M * Bertl anyway, off to bed now .. have fun! 1381026888 N * Bertl Bertl_zZ 1381026897 M * user-K thanks again for the help today, Bertl_zZ 1381027939 M * user-K I am hardly believing how incredibly efficient this program is. It runs on minimal resources. Very impressive to me. :) 1381030337 Q * jrklein Remote host closed the connection 1381030374 J * jrklein ~osx@proxy.dnihost.net 1381037475 Q * user-K Quit: leaving 1381044094 Q * Walex Ping timeout: 480 seconds 1381047230 Q * ex Ping timeout: 480 seconds 1381050584 J * bonbons ~bonbons@2001:a18:20f:4601:1842:a79d:299c:aba5 1381052814 N * Bertl_zZ Bertl 1381052817 M * Bertl morning folks! 1381055610 J * ex ~ex@valis.net.pl 1381057217 Q * ircuser-1 Ping timeout: 480 seconds 1381059741 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net 1381063499 Q * thierryp Remote host closed the connection 1381063521 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:d0cd:579b:f9fc:d257 1381064004 Q * thierryp Ping timeout: 480 seconds 1381064650 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:8c74:7ef9:16d4:de4f 1381064810 Q * thierryp Remote host closed the connection 1381064830 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:8c74:7ef9:16d4:de4f 1381065314 Q * thierryp Ping timeout: 480 seconds 1381066690 J * thierryp ~thierry@home.parmentelat.net 1381067412 Q * thierryp Ping timeout: 480 seconds 1381072695 J * thierryp ~thierry@home.parmentelat.net 1381072843 Q * thierryp Remote host closed the connection 1381072990 J * thierryp ~thierry@home.parmentelat.net 1381082023 Q * thierryp Remote host closed the connection 1381082044 J * thierryp ~thierry@home.parmentelat.net 1381082085 J * thierryp_ ~thierry@home.parmentelat.net 1381082085 Q * thierryp Read error: Connection reset by peer 1381082827 Q * ircuser-1 Quit: ircuser-1 1381084032 J * Walex ~Walex@cl-203.lon-02.gb.sixxs.net 1381086758 Q * thierryp_ Remote host closed the connection 1381086779 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:dc06:9c8a:fcfe:38 1381086884 J * thierryp_ ~thierry@home.parmentelat.net 1381087264 Q * thierryp Ping timeout: 480 seconds 1381088073 M * Bertl off for a nap ... bbl 1381088078 N * Bertl Bertl_zZ 1381090190 N * l0kit Guest1567 1381090196 J * l0kit ~1oxT@0001b54e.user.oftc.net 1381090592 Q * Guest1567 Ping timeout: 480 seconds 1381091573 Q * sannes Remote host closed the connection 1381093332 Q * bonbons Quit: Leaving 1381094741 Q * Walex 1381094933 Q * thierryp_ Remote host closed the connection 1381094954 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:ac12:699b:d117:5a25 1381095439 Q * thierryp Ping timeout: 480 seconds 1381099190 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:dd74:d82a:5f15:a5d1 1381099674 Q * thierryp Ping timeout: 480 seconds 1381101010 N * Bertl_zZ Bertl 1381101015 M * Bertl back now ...