1363221283 Q * bonbons Quit: Leaving 1363226074 J * kolorafa_ ~irc@abfw3.neoplus.adsl.tpnet.pl 1363226390 Q * kolorafa Ping timeout: 480 seconds 1363229481 Q * _WildPikachu_ Ping timeout: 480 seconds 1363236664 J * kolorafa ~irc@achn211.neoplus.adsl.tpnet.pl 1363237023 Q * kolorafa_ Ping timeout: 480 seconds 1363238009 Q * clopez Ping timeout: 480 seconds 1363242059 Q * wmp Remote host closed the connection 1363244993 J * thierryp ~thierry@home.parmentelat.net 1363245848 J * Ghislain ~aqueos@adsl1.aqueos.com 1363248503 J * PowerKe ~tom@94-226-105-17.access.telenet.be 1363249694 Q * thierryp Remote host closed the connection 1363252078 J * alpha_one_x86 ~kvirc@186.27.67.73 1363252123 M * alpha_one_x86 Hello, I try update and switch my vserver, my procedure work on generation 2011, but with 2013 updated no: save_ctxinfo: symlink("/etc/vservers/vm1","/etc/vservers/.defaults/run.rev/40000"): No such file or directory 1363252565 M * ard you probably need to mkdir /var/run/vservers.rev;ln -s /var/run/vservers.rev /etc/vservers/.defaults/run.rev 1363252569 M * ard something like that 1363252616 M * ard lrwxrwxrwx 1 root root 21 Feb 11 2008 /etc/vservers/.defaults/run.rev -> /var/run/vservers.rev 1363252622 M * ard is what I have... 1363252648 M * ard or /etc/vservers/vm1 does not exist ;-) 1363252778 M * alpha_one_x86 no, file already exists 1363252824 M * alpha_one_x86 but /var/run/vservers.rev 1363252827 M * alpha_one_x86 not 1363252848 M * alpha_one_x86 what it should be? Folder? 1363252852 M * ard yes 1363252855 M * ard just mkdir 1363252866 M * ard it will contain the context-id to vserver mapping... 1363252898 M * ard (it will symlink to the correct vserver config directory) 1363253006 M * alpha_one_x86 with the mkdir seam work, strange, it's not controled and clearly displayed by vserver script, (well it's gentoo bug witch rm -Rf /var/run/*) 1363253144 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:29f0:8611:47f9:431a 1363257911 J * bonbons ~bonbons@2001:a18:209:1001:1cb8:cb01:4da3:40dd 1363259018 N * Bertl_zZ Bertl 1363259023 M * Bertl morning folks! 1363259176 J * wmp ~wmp@2001:41d0:1:8616::1 1363259242 J * clopez ~clopez@fanzine.igalia.com 1363259546 M * fback alpha_one_x86: /var/run often comes in tmpfs these days 1363259981 M * Aiken on gentoo /var/run is a symlink to /run which is mounted tmpfs 1363260069 M * alpha_one_x86 yes, it's why I have added mkdir ... into my init.d script 1363260099 M * alpha_one_x86 Now I'm testing vserver + 3.7 kernel on modern hardware... 1363260241 M * daniel_hozac util-vserver's initscripts already do that. 1363260266 M * Aiken I am using 3.6.9-vs2.3.4.4 and have no extra mkdir anywhere 1363260517 M * alpha_one_x86 daniel_hozac: seam not, or linked with gentoo 1363260578 M * Aiken reading back and assuming you mean vservers.rev it is auto created for me on gentoo 1363264196 Q * ircuser-1 Ping timeout: 480 seconds 1363267035 N * ensc Guest1814 1363267045 J * ensc ~irc-ensc@p4FFCFCD3.dip.t-dialin.net 1363267451 Q * Guest1814 Ping timeout: 480 seconds 1363267648 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net 1363269821 J * ptitoliv ~ptitoliv@delenn.ptitoliv.net 1363269858 M * ptitoliv hello everybody 1363269908 M * Bertl hello 1363269933 M * ptitoliv i'm new to vserver use and i have a question about /dev that i can't found on the wiki 1363269962 M * ptitoliv i can't find any documentation about vdevmap is it still usable ? 1363269978 M * Bertl unrelated: babylon 5 fan? 1363269985 M * ptitoliv Bertl: yes :) 1363270015 M * Bertl thought so :) 1363270021 M * ptitoliv my hostname betrayed me 1363270087 M * Bertl the device mapping stuff was integrated into util-vserver quite some time ago 1363270088 M * alpha_one_x86 with 3.7, cgroup allow know whitch vm use the hdd? 1363270135 M * ptitoliv Bertl: ok but i have difficulties understanding how it works 1363270143 M * ptitoliv if i give the MKNOD cap to my guest 1363270162 M * ptitoliv i have no restrictions on creating any device node 1363270164 M * ptitoliv is it normal ? 1363270177 M * daniel_hozac did you setup a device map and enable it in your kernel? 1363270224 M * ptitoliv by device map you mean a tree into /etc/vserver//vdevmap . 1363270226 M * ptitoliv ? 1363270319 M * daniel_hozac /etc/vservers//apps/vdevmap, yes. 1363270326 M * ptitoliv yes i did 1363270332 M * ptitoliv an sorry for the path 1363270337 M * ptitoliv but i did it on the correct path 1363270353 M * daniel_hozac so what do you have there? 1363270376 M * ptitoliv i have a mychar1 directory 1363270377 M * ptitoliv and into it 1363270386 M * ptitoliv two empty files 1363270388 M * ptitoliv create and open 1363270425 M * daniel_hozac and what is in device? 1363270479 M * ptitoliv arf 1363270482 M * ptitoliv i forgot it 1363270535 M * ptitoliv thought that the directory name was the identifier 1363270538 M * ptitoliv fixing it right now 1363270639 M * ptitoliv should i put mydrv1 or /dev/mydrv1 ? 1363270651 M * daniel_hozac /dev/mydrv1 1363270827 M * ptitoliv okay i did it 1363270854 M * ptitoliv but in my vps i can still create any char device 1363270892 M * ptitoliv i could create mydrv2 mydrv3 1363270905 M * daniel_hozac you can name them whatever 1363270910 M * daniel_hozac names are irrelevant 1363270917 M * daniel_hozac major minor and type are what matter. 1363270970 M * ptitoliv yes of course : that's why i create mydrv2 and mydrv3 with a differnt major number 1363271016 M * daniel_hozac so do you have device mapping enabled in your kernel? 1363271053 M * ptitoliv hmm i don't think i have done anything about that 1363271112 M * ptitoliv is there a documentation entry for that ? 1363271137 M * ptitoliv hm is it CONFIG_VSERVER_DEVICE ? 1363271145 M * ptitoliv in that case it is enabled on my kernel 1363271225 M * ptitoliv but there is a thing i don't understand 1363271235 M * ptitoliv on my configuration i never specified the major nor the minor number 1363271320 M * ptitoliv should i have to create the nodes on the host level before ? 1363271330 M * daniel_hozac yes 1363271336 M * daniel_hozac that is what device points out. 1363271436 M * ptitoliv so I must create /vserver/guest/dev/mydrv1 on the host first ? 1363271450 M * ptitoliv with the correct major minor 1363271468 M * daniel_hozac no, you should create /dev/mydrv1 with the right major and minor 1363271475 M * ptitoliv ok 1363271477 M * ptitoliv this is done 1363271481 M * ptitoliv on the host 1363271507 Q * alpha_one_x86 Quit: KVIrc KVIrc Aria 4.3.1, revision: 6250, sources date: 20120701, built on: 2013-01-13 18:32:25 UTC http://www.kvirc.net/ 1363271619 M * ptitoliv a d lt 1363271626 M * ptitoliv and nothing on /vserver/guest/dev 1363272181 M * Bertl with nothing you mean, no devices there? 1363272191 M * ptitoliv just the default created by my template 1363272194 M * ptitoliv but not mydrv1 1363272204 Q * clopez Ping timeout: 480 seconds 1363272216 M * Bertl did you create the mydrv1 > 1363272219 M * Bertl s/>/? 1363272247 M * ptitoliv i created on /dev/mydrv1 but on host level 1363272260 M * ptitoliv should i create it on my /vserver/guest/dev tree too ? 1363272377 M * ptitoliv to be honest i don"t understand well how works the vdevmap thing 1363272396 M * ptitoliv because if i create /vserver/guest/dev/mydrv1 1363272401 M * ptitoliv ok i can use it from the guest 1363272410 M * ptitoliv so in that case why should il use vdevmap ? 1363272426 M * Bertl yes, the idea is to have a device in the guest, which is mapped to a different device on the host 1363272463 M * Bertl for example, /dev/ttyS0 has major 4 minor 64 as character device 1363272523 M * Bertl while /dev/tty1 has major 4, minor 1 (char) on the host 1363272566 M * Bertl the device mapping allows you to make one act as the other or to restrict access to one, but allow access to the other 1363272591 M * Bertl nevertheless, you need a device node inside the guest to access 1363273271 M * ptitoliv Bertl: sorry i'm back my boss took me for the coffee 1363273298 M * ptitoliv reading your text now 1363273355 M * ptitoliv ok i see 1363273367 M * ptitoliv so if i just one to give access to mydrv1 into the guest 1363273387 M * ptitoliv i don't have any interest using device mapping and just create the node on the vserver /dev tree on the host level 1363273888 M * Bertl to give unrestricted access to a device, all you need is to create or copy the device node into the guest 1363273921 M * Bertl but usually, you want to limit access in some way and/or map access to other (secure) devices 1363273945 M * ptitoliv like the disks for example ? 1363273981 M * Bertl like for example using the vroot devices instead of the real low level disk devices 1363274020 Q * wmp Remote host closed the connection 1363274033 M * Bertl but it really depends on the device ... for example, giving a specific serial port to a guest should cause no harm 1363274059 M * Bertl I'm off for a nap now ...bbl 1363274066 N * Bertl Bertl_zZ 1363274073 M * ptitoliv Bertl: thanks for your answers 1363274076 M * ptitoliv have a good nap 1363277400 J * nkukard ~nkukard@196-210-205-18.dynamic.isadsl.co.za 1363278441 M * yang How could I assign additional space to guests from the secondary drive ? 1363279526 J * clopez ~clopez@108.30.165.83.dynamic.mundo-r.com 1363282072 Q * Ghislain Quit: Leaving. 1363282191 J * Ghislain ~aqueos@adsl1.aqueos.com 1363282610 Q * thierryp Remote host closed the connection 1363287726 J * wmp ~wmp@2001:41d0:1:8616::1 1363289466 J * kolorafa_ ~irc@avw237.neoplus.adsl.tpnet.pl 1363289669 Q * kolorafa Ping timeout: 480 seconds 1363290259 Q * clopez Read error: Operation timed out 1363290271 Q * kolorafa_ Ping timeout: 480 seconds 1363291123 Q * Ghislain Quit: Leaving. 1363291219 J * hijacker_ ~hijacker@cable-84-43-134-121.mnet.bg 1363294636 Q * hijacker_ Quit: Leaving 1363296919 N * Bertl_zZ Bertl 1363296924 M * Bertl back now ... 1363296942 M * Bertl yang: bind mounts maybe? 1363297020 M * yang yes, I am wondering 1363297046 M * yang I ll look onwebsite about that 1363297073 M * Bertl well, it mainly depends on your setup and what you want to achieve 1363297103 M * Bertl if you're already using lvm, you can easily add the second disk and extend whatever volume is used for the guest(s) 1363297153 M * yang this one isnt lvm 1363297156 M * Bertl if you just want to add a bunch of new guests utilizing the second drive could simply be mounted in a different place (with filesystem) 1363297176 M * Bertl s/drive/drive, it 1363297225 M * Bertl if you need/want to extend the current guest(s), you might consider moving parts (e.g. /home or so) to a different drive/filesystem 1363297378 M * yang is there a manual on that Bertl ? 1363297402 M * Bertl porbably :) nowadays there's a manual for everything ... 1363297425 M * yang ;) 1363297433 M * Bertl but it's basic linux/unix stuff, nothing special there 1363297460 M * yang I could just ln-s /home then on host and it would work ? 1363297505 M * Bertl depends, but it's probably simpler/better to put a bind mount into the guest config's fstab 1363297522 M * Bertl e.g. mount the second disk on /vs_homes 1363297540 M * Bertl then put a directory for each guest there, e.g. /vs_homes/guest1 1363297559 M * Bertl and in the fstab (guest config, not inside the guest), you put 1363297632 M * yang fstab is in /etc/vserver//fstab ? 1363297649 M * Bertl /vs_homes/guest1 /home bind defaults .. 1363297655 M * Bertl yep, that one 1363297669 M * yang ok thansk Bertl 1363297687 M * yang It would be good to put a wiki entry on that one, for future reference 1363297708 M * Bertl feel free to make one 1363297725 M * yang ok 1363297796 M * Bertl just search for similar attempts on the wiki first and collect available information ... and as always, test the stuff before you add it there :) 1363297804 M * yang sure 1363304516 Q * wmp Remote host closed the connection