1363739444 J * derjohn_mob ~aj@85.182.152.178
1363743253 J * Seattle ~chatzilla@c-24-34-74-228.hsd1.ma.comcast.net
1363743264 M * Seattle Hi All - am trying to compile kernel (http://linux-vserver.org/Installation_on_Linux_2.6).  Have gotten through step "make && make modules_install".  Seemed to run...am on to step "you have to copy the kernel image to your /boot partition and configure your boot loader." but can't find new kernel image...where would this process put it?  Is it possible that while things seemed to run, it...
1363743266 M * Seattle ...didn't work?
1363744614 M * Bertl no, the kernel is there, it is located in arch/x86/boot
1363744638 M * Bertl usually you can install it with 'make install' (similar to make modules_install) 
1363744651 Q * nlm Ping timeout: 480 seconds
1363744674 Q * derjohn_mob Ping timeout: 480 seconds
1363745165 J * derjohn_mob ~aj@85.182.152.178
1363747858 Q * clopez Ping timeout: 480 seconds
1363748114 J * clopez ~clopez@108.30.165.83.dynamic.mundo-r.com
1363750884 Q * derjohn_mob Ping timeout: 480 seconds
1363752450 J * derjohn_mob ~aj@85.182.152.178
1363753069 Q * derjohn_mob Ping timeout: 480 seconds
1363756213 J * derjohn_mob ~aj@d141166.adsl.hansenet.de
1363759753 Q * clopez Ping timeout: 480 seconds
1363761114 J * nerdpunk ~user@2001:470:50b6:0:4061:c227:9583:c5a9
1363761123 Q * distemper Ping timeout: 480 seconds
1363761719 Q * derjohn_mob Ping timeout: 480 seconds
1363761842 M * Bertl off to bed now ... have a good one everyone!
1363761852 N * Bertl Bertl_zZ
1363762077 J * Ghislain ~aqueos@adsl1.aqueos.com
1363762820 J * derjohn_mob ~aj@87.253.171.208
1363768788 J * thierryp ~thierry@home.parmentelat.net
1363770761 J * _WildPikachu_ ~nkukard@196-210-204-27.dynamic.isadsl.co.za
1363770891 Q * nkukard_ Ping timeout: 480 seconds
1363771341 J * Walex ~Walex@94.197.190.194.threembb.co.uk
1363774340 J * mekt ~mekt@0001b319.user.oftc.net
1363775904 Q * jrklein_ Read error: Operation timed out
1363775947 J * jrklein ~osx@proxy.dnihost.net
1363776476 M * mekt Are Linux features needed for VServer now in the linux-stable branch?
1363776636 M * Seattle Thanks Bertl - can't find it (does arch/x86/boot mean the /boot for my setup?)...think it's there somewhere....tried a reboot, but only have original 2.6.32-5-686.  Sorry, stumped
1363776796 M * Seattle mekt - hi - my understanding is that the versions of the kernel and util-vserver where ancient when did straight forward install for debian 6
1363776855 M * daniel_hozac mekt: no, but more and more is getting added.
1363776999 M * Seattle I ran vserver-info, and that's what Bertl thought...
1363777031 M * Seattle would be happy to skip compiling if I could..
1363777234 M * mekt Thanks for the info. Presently i am running a 3.9 Linux with completely custom configuration. I shall watch the patches at linux-vserver.org/Downloads .
1363777260 M * daniel_hozac 3.9 certainly isn't in linux-stable :)
1363777272 M * mekt as RC2.
1363777279 M * mekt which is.
1363777299 M * Seattle Sorry - didn't mean to interrupt thread...
1363777342 M * mekt Seattle: multiple concurrent threads is usual on IRC.
1363777398 Q * ircuser-1 Read error: Operation timed out
1363777424 M * Seattle OK
1363777450 Q * mekt 
1363778002 J * clopez ~clopez@fanzine.igalia.com
1363778762 J * nlm ~nlm@host187.190-228-227.telecom.net.ar
1363778869 M * Seattle Wanted to post again...new to trying to get through compile process.  Got through "make && make modules_install" and things seemed to compile (didn't see errors).  Trying to do "copy the kernel image to your /boot partition and configure your boot loader" but can't find kernel image.  Where would this process put it?  Think I'm doing something dumb... 
1363778959 N * quasisan1 quasisane
1363778972 M * Seattle Suggestion it's in "arch/x86/boot" - would guess that means /boot for my dist ... think I only see original initrd, vmlinuz, and system.map there....again, new to this so am fumbling...
1363781135 Q * Seattle Remote host closed the connection
1363781230 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net
1363781491 Q * wmp Ping timeout: 480 seconds
1363781508 J * wmp ~wmp@2001:41d0:1:8616::1
1363783206 Q * Walex 
1363783274 Q * thierryp Remote host closed the connection
1363786346 Q * Aiken Remote host closed the connection
1363786500 N * Bertl_zZ Bertl
1363786512 M * Bertl morning folks!
1363788101 Q * eyck Server closed connection
1363788103 J * eyck ~eyck@nat08.nowanet.pl
1363789396 Q * wmp Remote host closed the connection
1363789535 Q * aurel42 Ping timeout: 480 seconds
1363789776 J * Walex ~Walex@92.41.246.162.threembb.co.uk
1363790554 Q * clopez Ping timeout: 480 seconds
1363792267 J * wmp ~wmp@2001:41d0:1:8616::1
1363795246 M * Bertl off for now ... bbl
1363795250 N * Bertl bertl_oO
1363795254 N * bertl_oO Bertl_oO
1363798728 J * clopez ~clopez@108.30.165.83.dynamic.mundo-r.com
1363799024 Q * Romster Ping timeout: 480 seconds
1363799397 J * WiuEmPe ~wmp-freen@62.244.149.110
1363799843 J * thierryp ~thierry@home.parmentelat.net
1363800007 Q * mnemoc Server closed connection
1363800088 J * mnemoc ~amery@geeks.cl
1363800534 Q * clopez Ping timeout: 480 seconds
1363800804 Q * derjohn_mob Ping timeout: 480 seconds
1363806103 J * Seattle ~chatzilla@c-24-34-74-228.hsd1.ma.comcast.net
1363806173 Q * Seattle 
1363806186 J * Seattle ~chatzilla@c-24-34-74-228.hsd1.ma.comcast.net
1363806193 J * ksn ~ksn@00019501.user.oftc.net
1363806269 M * Seattle Hi All - I'm working on compiling kernel for Debian 6, am getting kernel panic, was hoping to review steps I've taken and see where I'm going wrong (am I using the wrong versions or incompatible versions?):
1363806270 M * Seattle - fresh install (debian squeeze)
1363806272 M * Seattle - mkdir ~/src
1363806274 M * Seattle - cd ~/src
1363806275 M * Seattle - wget https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.6.11.tar.xz (to pull down 3.6.11 kernel)
1363806277 M * Seattle - tar -xJf linux-3.6.11.tar.xz
1363806278 M * Seattle - copied contents of "vs2.3.4.6" from http://linux-vserver.org/Downloads, and created file in ~/src called "patch-3.6.11-vs2.3.4.6.diff" and pasted contents into it.
1363806299 M * Seattle cp -la linux-3.6.11 linux-3.6.11-vs2.3.4.6 -cd linux-3.6.11-vs2.3.4.6 -cat ../patch-3.6.11-vs2.3.4.6.diff | patch -p1 -copied "config-2.6.32-5-686" from /boot to ~/src/linux-3.6.11-vs2.3.4.6 and rename file as ".config" -installed build-essential and ncurses-dev libncurses-dev libncurses5-dev -from  ~/src/linux-3.6.11-vs2.3.4.6, ran menuconfig -took all the defaults for Linux Vserver...
1363806301 M * Seattle ...configuration options -from  ~/src/linux-3.6.11-vs2.3.4.6, ran "make" -from ~/src/linux-3.6.11-vs2.3.4.6, make install -ran update-grub
1363806320 M * Seattle The compile seems to complete succesully, and in /boot "config-3.6.11-vs2.3.4.6", "System.map-3.6.11-vs2.3.4.6" and "vmlinuz-3.6.11-vs2.3.4.6" are added.
1363806393 M * Seattle Upon reboot, I select vmlinuz-3.6.11-vs2.3.4.6 but end up in kernel panic.  Thoughts on what I'm doing wrong?
1363806849 J * FireEgl ~FireEgl@173-25-83-57.client.mchsi.com
1363806865 M * Bertl_oO could be a bunch of things, please upload the bootup log somewhere
1363806905 M * Seattle OK - is there a link you'd prefer (I think there's on off of the site...)?
1363806961 M * Bertl_oO doesn't matter, whatever works for you is fine
1363806977 M * Bertl_oO (you can use paste.linux-vserver.org)
1363807017 M * Seattle Thanks Bertl - I'm not sure Debian has a boot log - let me research...hang on...
1363807032 M * Bertl_oO the messages you get when booting the new kernel
1363807040 N * Bertl_oO Bertl
1363807073 M * Bertl record them (best done via serial console) and upload them somewhere so that I can take a look at it
1363807234 M * Seattle Not sure serial console is option, but think I can enable boot logging.  Let me try that and will come back in a bit...
1363807398 Q * Seattle Quit: ChatZilla 0.9.90 [Iceweasel 3.5.16/20121207230533]
1363808365 J * clopez ~clopez@108.30.165.83.dynamic.mundo-r.com
1363808951 Q * ksn Quit: WeeChat 0.3.8
1363809171 J * bonbons ~bonbons@2001:a18:209:1001:9989:94af:87ff:846
1363809413 Q * clopez Ping timeout: 480 seconds
1363809669 Q * WiuEmPe Quit: Konversation terminated!
1363809950 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com
1363810335 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f
1363810461 Q * Romster Read error: Operation timed out
1363810484 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com
1363810734 J * Seattle ~chatzilla@c-24-34-74-228.hsd1.ma.comcast.net
1363810852 M * Seattle Hi All - am working on compiling new kernel/vserver patch.  Trying to get logs, but appears that boot log in debian is overwritten at each boot and logs not generated (Bertl suggested serial console...saw something on net about netconsole...may need to resort to these but look like are a challenge in and of themselves).  Have hand typed what I see on the screen...not sure this helps...
1363810883 M * Seattle  Early console in decompress_kernel
1363810884 M * Seattle Decompressing linux....Parsing ELF...done.
1363810884 M * Seattle Booting the kernel.
1363810884 M * Seattle [  1.024148] Kernel panic - not syncing :  VFS:  Unable to mount root fs on unknown-block(0,0)
1363810884 M * Seattle [ 1.024203] Pid:  1, comm:  swapper/0 Not tainted 3.6.11-vs2.3.4.6 #2
1363810884 M * Seattle [ 1.024.2501] Call Trace:
1363810886 M * Seattle [  xxxxx] [<cxxxxxx>] ? panic+0x80/0x170
1363810886 M * Seattle [  xxxxx] [<cxxxxxx>] ? mount_block_root_0x1df/0x200\
1363810903 M * Seattle [  xxxxx] [<cxxxxxx>] ? do_signal_0x88/0x4ab\
1363810903 M * Seattle [  xxxxx] [<cxxxxxx>] ? mount_root+0x30/0x4d\
1363810903 M * Seattle [  xxxxx] [<cxxxxxx>] ? prepare_namespace+0x10e/0x13e\
1363810903 M * Seattle [  xxxxx] [<cxxxxxx>] ? kernel_init+0x17d/0x189\
1363810903 M * Seattle [  xxxxx] [<cxxxxxx>] ? repair_env_string+0x4f/0x4f\
1363810904 M * Seattle [  xxxxx] [<cxxxxxx>] ? kernel_thread_helper+0x6/0xd}
1363810907 M * Bertl (please use paste.linux-vserver.org for everything longer than 3 lines)
1363810985 M * Bertl also, what I see so far, the root device cannot be mounted, to diagnose this further, I need the output of a verbose bootup
1363811026 M * Bertl most likely, the bootloader adds 'quiet' to the kernel command line (try to remove that in grub/lilo)
1363811079 M * Seattle OK..thanks..hang on
1363811111 M * Bertl chances are good, you are missing a driver or a module is not loaded/available in the initramfs
1363811264 Q * m_ueberall Server closed connection
1363811281 J * m_ueberall dircproxy4@2a01:4f8:100:80e3:0:bc28:af65:5
1363811606 Q * Romster Ping timeout: 480 seconds
1363812136 Q * Seattle Remote host closed the connection
1363813041 J * Seattle ~chatzilla@c-24-34-74-228.hsd1.ma.comcast.net
1363813107 M * Seattle Hi All - have been trying to upgrade kernel, getting panics, and can't seem to find (short of serial console) to get boot log to work (it either overwrites or can't find messages that seem relevant).  Am going to try this all on another machine...
1363813114 M * Seattle Thanks....will post back...
1363813420 J * hijacker_ ~hijacker@cable-84-43-134-121.mnet.bg
1363814433 Q * Seattle Read error: Operation timed out
1363815462 Q * hijacker_ Quit: Leaving
1363816824 Q * bonbons Quit: Leaving
1363818147 Q * Walex 
1363819326 J * WiuEmPe ~wmp-freen@62.244.149.110
1363819330 M * WiuEmPe hello
1363819354 M * WiuEmPe i have problem, after install newest vsrver i cant boot on normal kernel
1363819391 M * WiuEmPe and server with vserver kernel has crashs
1363819423 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com
1363821208 Q * Romster Ping timeout: 480 seconds
1363821226 Q * thierryp Remote host closed the connection
1363822065 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com
1363822121 M * Bertl WiuEmPe: why can't you boot a normal kernel?
1363822132 M * WiuEmPe nvm ;)
1363822153 M * Bertl okay, and in what way does the Linux-VServer crash?
1363822167 M * WiuEmPe i dont know
1363822178 M * Bertl what message do you get?
1363822180 M * WiuEmPe after few hours server dont response
1363822192 M * WiuEmPe i havent message, i havent kvm :/
1363822217 M * Bertl okay, so after a few hours, the host is unreachable or unresponsive?
1363822344 M * WiuEmPe emmm, i dont understand ;) dont ping, ssh dont listing and i must make restart
1363822374 M * Bertl I mean, your only connection to the host (the physical machine) is via network, yes?
1363822414 M * WiuEmPe yes
1363822440 M * Bertl so, you do not know if the kernel has a problem or if you just lose network connectivity, yes?
1363822507 M * WiuEmPe Bertl: kernel problem
1363822515 M * Bertl how do you know?
1363822529 M * WiuEmPe technics in DC can only reboot server becouse dont response
1363822557 M * Bertl okay, so they did access the console?
1363822595 J * clopez ~clopez@108.30.165.83.dynamic.mundo-r.com
1363822597 M * Bertl and we are talking about 3.7.10-vs2.3.5.6 yes?
1363822619 M * WiuEmPe yes
1363822635 M * WiuEmPe and on 3.4.4 i have this same
1363822648 M * WiuEmPe on 2.6.38 work good over 24h
1363822668 M * Bertl 3.4.4 means 3.4.4 + Linux-VServer or 3.4.4 mainline unpatched?
1363822710 M * WiuEmPe 3.4.4 with vserver
1363822743 M * Bertl okay, and there is no kernel panic on the console?
1363822769 M * Bertl because kernel lockups are usually detected by the kernel and logged
1363822780 M * Bertl (unless they are hardware issues)
1363822783 M * WiuEmPe Bertl: display is dark
1363822795 M * WiuEmPe in logs i have nothing
1363822818 M * Bertl well, that's not unexpected, it would require a serial console to get more information
1363822840 M * Bertl did you try to run an unpatched kernel, same version, same config on that machine?
1363822896 M * WiuEmPe Bertl: now i run 3.2.0-39 from ubuntu repos
1363822939 M * Bertl I'd suggest to get a 3.7.10 kernel, no Linux-VServer patch, with the same config you used for the 3.7.10-vs2.3.5.6 one
1363822974 M * Bertl and run that for at least 24 hours to see if that is fine
1363823014 M * WiuEmPe Bertl: heh, my user want work server :D
1363823087 M * Bertl that's up to you, I'm just suggesting options
1363823129 M * WiuEmPe yes, i understand ;)
1363823148 M * WiuEmPe Bertl: but in this server i have problem with xen too
1363823162 M * WiuEmPe booting on xen tell me that i have broken discs
1363823163 M * Bertl I presume it is a hardware issue
1363823193 M * WiuEmPe but i have raid1 and this is very oddly for raid1
1363823203 M * WiuEmPe and work good on normaln kernel
1363823210 M * WiuEmPe without xen
1363823331 Q * Romster Ping timeout: 480 seconds
1363823390 Q * Ghislain Quit: Leaving.
1363823419 M * WiuEmPe Bertl: maybe vserver has problems with 64GB ram?
1363823511 M * Bertl I don't think so, we do not modify the memory management 
1363823518 M * WiuEmPe ok
1363823532 M * Bertl and I know a few sites where 64GB+ is no problem
1363823629 M * Bertl a good indication for a hardware issue is that even ping fails, because usually when the kernel panics, ping still works, as it is answered in the interrupt handler
1363823634 M * WiuEmPe new version has root with context 0 - nice ;)
1363823816 Q * imachine Remote host closed the connection