Back to Home / #xen / 2006 / 06 / Prev Day | Next Day
#xen IRC Logs for 2006-06-27

---Logopened Tue Jun 27 00:00:01 2006
00:10|-|jforbes_ [] has joined #xen
00:10|-|jforbes [] has quit [Read error: Connection reset by peer]
00:11|-|Z3R0`c11l [~zerocool@] has quit [Read error: Connection reset by peer]
00:11|-|Z3R0`c00l [~zerocool@] has joined #xen
00:33|-|jforbes_ [] has quit [Ping timeout: 480 seconds]
00:37|-|jforbes [] has joined #xen
00:50|-|jforbes [] has quit [Ping timeout: 480 seconds]
00:52|-|Tv [] has quit [Quit: foo]
01:00|-|jforbes [] has joined #xen
01:04|-|horms [] has joined #xen
01:17|-|mastermind [] has quit [Remote host closed the connection]
01:25|-|Tv [] has joined #xen
01:30|-|Sir_Ahzz [~ahzz@] has quit [Ping timeout: 480 seconds]
02:07|-|muli [] has quit [Remote host closed the connection]
02:09|-|womble [] has quit [Quit: What's behind the round window...]
02:11|-|rusty [] has quit [Quit: Ex-Chat]
02:22|-|Sir_Ahzz [] has joined #xen
02:23|-|mode/#xen [+o Sir_Ahzz] by ChanServ
02:31|-|visik7 [~visi@] has joined #xen
02:43|-|Shoragan_ [] has joined #xen
02:48|-|parabelboi [] has joined #xen
03:06|-|mejlholm [] has joined #xen
03:07|-|horms [] has quit [Quit: Leaving]
03:09|-|mig [] has joined #xen
03:14|-|mejlholm [] has quit [Quit: Leaving]
03:15|-|mejlholm [] has joined #xen
03:15<mig>Hi, where can I get help with crashing xen-installations? (dom0 freezes)
03:28<am88b>you might want to write to xen-users mailinglist or just report bug to bugzilla
03:30<mig>Yes, it just halts. Normaly while writing to disk so I get a corrupted filesystem after reset. Maybe it depends on the harddisk-controller (3ware).
03:31<am88b>sounds like serious bug
03:35<mig>How can I log what happens? I want to know where the bug sits (xend / 3ware-driver). Can xen write a log into a console? I doesn't get a kernel-panic-screen or sth so I have to believe the xen kernel collapses.
03:38<am88b>have you checked the xen logs?
03:39<koki>mig: use a log server
03:40<mig>where should the stay?
03:40<koki>at what stage are u freezing? - boot, running, ...
03:41<mig>running, Its a gentoo-system normaly while rsync
03:41<koki>so when cpu-load goes up?
03:42<mig>its a hyperthread Xeon
03:42<koki>try dd if=/dev/zero of=/my/disk .... to see if it is the controller
03:43<koki>dual cpu, or just one?
03:43<mig>just one
03:44<koki>otherwise i would've turned stupid hyperthreading off
03:44<mig>running a pure linux stable.
03:44<koki>no, u are running xen
03:44<mig>yes that what I want.
03:44<koki>what is "pure linux stable"
03:45<koki>are u running 64bit or 32bit?
03:45<mig>booting a "normal" linux-2.16.xy, the system runs whithout props.
03:46<koki>i can definitely recommend the 64bit version of xen - solves the whole /lib/tls issue
03:46<koki>so, dd works?
03:47[~]koki thinks, maybe the thing just gets hot.
03:49<mig>dd if=/dev/zero of=/root/dd_test hangs again.
03:49<mig>I had to reset.
04:04|-|athomas [] has joined #xen
04:04<mig>Can I definitivly use 32bit domUs on a 64bit xen / dom0 ?
04:11<mig>ok, maybe it solves this problem - I will try!
04:12<am88b>why would you want it, anyway?
04:14<mig>to be able to move the domU to an old machine (as backup). It's more or less a "marketing reason"...
04:18|-|alekibango [] has joined #xen
04:32|-|avdyk [] has joined #xen
04:33|-|mejlholm [] has quit [Ping timeout: 480 seconds]
04:35|-|mejlholm [] has joined #xen
04:58|-|visik7 [~visi@] has quit [Remote host closed the connection]
05:00|-|mdday [] has joined #xen
05:15|-|visik7 [~visi@] has joined #xen
05:24[~]avdyk is away: eating
05:27|-|athomas [] has quit [Quit: Leaving]
05:35<alekibango>hello. i have installed sid and latest xen packages.. using debian xen kernel... and succesfully created some image using xen-create-image... but now i have trouble running it... i keep getting Error: (111, 'Connection refused') or Error: (9, 'Bad file descriptor') (which depends on xend-config.sxp settings)... can someone help? i am new to xen...
05:35|-|athomas [] has joined #xen
05:37|-|mdday [] has quit [Quit: mdday]
05:44|-|gerrit [] has quit [Ping timeout: 480 seconds]
05:50<hensema>sid is?
05:51<hensema>debian unstable?
05:51<hensema>seems like xend isn't running
06:00[~]chax nods
06:00<chax>yes alekibango it looks like xend is not running
06:02[~]avdyk is back (gone 00:37:36)
06:10[~]alekibango is looking into it :)
06:12<alekibango>when its running,i get errror 9 bad file descriptor
06:13<chax>alekibango, does your tool give the location of the conf file it is generating for getting the guest os up ?
06:15<alekibango>yes its in /etc/xen/test.cfg, i used this article:
06:16<chax>can you see what is there for disk = [] in that file ?
06:17<alekibango>path to disk is ok
06:17<alekibango>its ext3 image
06:17<alekibango>mountable using -o loop
06:17<alekibango>i am sending part of log to pastebin... its soo loaded...
06:17<chax>yup :)
06:19<chax>they have this wonderful messages .. which dont say what file they missed to find or what file had a bad file descriptor
06:20<alekibango>its in buildDomain
06:23<chax>not able to access for some reason .. whats the essential error message that it gives ?
06:24<alekibango> File "/usr/lib/python2.3/site-packages/xen/xend/", line 188, in buildDomain
06:24<alekibango> features = self.features)
06:24<alekibango>error: (9, 'Bad file descriptor')
06:25<chax>ok try this .. donno how far it works .. i'm guessting something wrong with the ui thing you are using ..
06:25<chax>try .. xm create -c /etc/xen/test.cfg
06:25<alekibango>yes thats the command
06:25<alekibango>which leads to the error
06:26<alekibango>which is somewhere in self.buildDomain()
06:26<alekibango>but i am really confused :)
06:26<chax>ok do onething
06:27<chax>check if you have /lib/modules/<kernel_version>/xen/ ......
06:27<chax>in the disk image
06:27<chax>i mean
06:27<chax>loop mount it
06:27<alekibango>ok i will
06:27|-|SLot [] has joined #xen
06:28<alekibango>no xen in lib/modules/2.6.16-2-xen-k7
06:29<alekibango>(looked for *xen* in mc)
06:29<chax>1 sec
06:30<alekibango>should i build my domu kernel ? :) and install it?
06:31<chax>no no
06:31|-|jimix [] has joined #xen
06:32<chax>it just uses the base-os's xen kernel specified in that conf file
06:33<alekibango>kernel = '/boot/vmlinuz-2.6.16-2-vserver-k7'
06:33<alekibango>ramdisk = '/boot/initrd.img-2.6.16-2-vserver-k7'
06:33<alekibango>memory = 256
06:33<chax>wth is it calling a bad file descriptor ..
06:33<alekibango>(from config)
06:35[~]chax thinks
06:35<alekibango>its vim /usr/lib/python2.3/site-packages/xen/xend/ +188
06:35<alekibango> features = self.features)
06:35<alekibango>but i do not know why :)
06:36<alekibango>or its another statement near..
06:36<alekibango>chax: could this be by wrong network settings?
06:37<alekibango>like missing bridge or something?
06:37<chax>oh you dont need a bridge to get a xen guest up and running
06:37<chax>i dont even fill that thing
06:38<chax>i leave it at 'vif=o09:04: .... blah'
06:38<alekibango>?? o09:04 ? ?
06:38<chax>no i meant whatever mac address ...
06:39<avdyk>excuse me, I'm new here, do you mean that domU's uses kernel in the dom0 filesystem?
06:39<avdyk>because I have problems creating domU instance but I can boot on a xen-linux kernel
06:40<avdyk>it seems to be a scsi problem
06:40<alekibango>i am on ide now :)
06:40<alekibango>but i was hurted by scsi last time i tried xen
06:40<alekibango>avdyk: do you have initrd ??
06:40<chax>ok gotta rush .. be back later ...
06:40<alekibango>chax: ty anywa
06:41<avdyk>alekibango: yes
06:41<avdyk>ramdisk =
06:41<alekibango>chax: my domu is not starting - thanks to eror 9 : ))
06:41<alekibango>which sucks
06:41<chax>will get back later bye
06:42<avdyk>SCSI subsystem initialized
06:42<avdyk>register_blkdev: cannot get major 8 for sd
06:42<avdyk>/bin/cat: /sys/block/sda/dev: No such file or directory
06:42<avdyk>Waiting 1 seconds for /sys/block/sda/dev to show up
06:42|-|Marco [] has quit [Quit: Client exiting]
06:43<avdyk>/bin/cat: /sys/block/sda/dev: No such file or directory
06:43<avdyk>Device /sys/block/sda/dev seems to be down.
06:43<avdyk>Debugging opportunity, type ^D to continue.
06:43<avdyk>/bin/dash: can't access tty; job control turned off
06:53[~]avdyk is away: I'm busy
06:53[~]avdyk is back (gone 00:00:02)
06:54<hensema>please don't spam away/back messages in the channel
06:55<avdyk>hensema: yep, I'm trying to fix it in bitchX ;-)
07:02|-|mdday [] has joined #xen
07:03|-|mejlholm [] has quit [Quit: Leaving]
07:08|-|bernarde [~bernarde@] has joined #xen
08:01|-|vaggie [~vaq@] has joined #xen
08:01<vaggie>Does XEN work with LILO?
08:02<visik7>yes but really sucks
08:03<vaggie>well grub doesnt work with LVM so i need to use LILO
08:03<vaggie>where can i read more about XEN and LILO?
08:04<visik7>I usally put kernel in a separate partition
08:04<vaggie>i did that but grub still complains..
08:04<vaggie>saying: Grub installation error on hd0
08:04<vaggie>"/boot" is outside the LVM
08:04<visik7>not for me
08:05<visik7>I used grub for lvm
08:05<visik7>with boot outside of lvm
08:05<vaggie>do you have SCSI disks?
08:05<visik7>but I did that 'couse root was in xfs (not officially supported by grub)
08:05<visik7>no sata
08:06|-|um [] has joined #xen
08:06<vaggie>i use scsi, maybe thats why?
08:14|-|Tv [] has quit [Quit: foo]
08:17|-|msinhore [] has joined #xen
08:47|-|visik7 [~visi@] has quit [Remote host closed the connection]
08:50|-|Tv [] has joined #xen
08:52|-|cypa [] has joined #xen
08:53|-|arachnist [] has joined #xen
08:53|-|visik7 [~visi@] has joined #xen
08:53<avdyk>on dom0 I have several ethernet cards, how can I know which is used to make the bridge (debian/etch(testing))
08:54<avdyk>I use the network-bridge script and passes deveth=eth2
08:54<avdyk>but I'd like to be sure it's the good one
08:54|-|arachnist [] has left #xen [Leaving]
08:56<avdyk>I use the network-bridge script and passes netdev=eth2
08:57<cypa>is it possible to run xdmcp on guest domain?
09:02|-|ns [] has joined #xen
09:04|-|rharper [] has joined #xen
09:20|-|cypa [] has quit [Remote host closed the connection]
09:29|-|Hunger [] has quit [Ping timeout: 480 seconds]
09:35|-|mejlholm [] has joined #xen
09:38|-|anball [] has joined #xen
09:47|-|Hunger [] has joined #xen
09:49|-|hollisb [] has joined #xen
09:52|-|bernarde [~bernarde@] has quit [Remote host closed the connection]
09:53|-|visik7 [~visi@] has quit [Remote host closed the connection]
09:59|-|muli [] has joined #xen
10:08|-|visik7 [~visi@] has joined #xen
10:09|-|avdyk [] has quit [Quit: moving]
10:10|-|jerone [] has joined #xen
10:14|-|mig [] has quit [Quit: Kopete 0.11.3 :]
10:17|-|vaggie [~vaq@] has quit [Ping timeout: 480 seconds]
10:19|-|avdyk [] has joined #xen
10:23|-|DV_ [] has joined #xen
10:38<avdyk>re- hi
10:38<avdyk>I got network problems now :(
10:38<avdyk>impossible to ping domU from dom0 and impossible to ping dom0 from domU
10:46<alekibango>having similar problem... just managed to make frist domU running :)
10:48<avdyk>alekibango: my first domU is running now... sometimes ;-)
10:48<alekibango>i just runned it for first
10:48<alekibango>time... trying to ping
10:48<alekibango>and ping loops forever lol
10:48<alekibango>so i am restarting it now :))
10:48<avdyk>same here ;-)
10:48<avdyk>now, I use 'ping -c 2 IP_ADDRESS'
10:49<avdyk>(-c == count)
10:49<alekibango>avdyk: i want to use 1 external ip and to have few servers on it (mail, www)
10:49<alekibango>found some howto for xen2
10:49<avdyk>you need a NAT, don't you?
10:49<alekibango>but people were writing that it does not work fro xen3
10:49<alekibango>i do not know what is best
10:49<alekibango>i can nat + forward ports
10:49<alekibango>but i never used bridges
10:50<avdyk>alekibango: neither do I ;-)
10:50<alekibango>if you will find some tutor or howto, tell me
10:50<avdyk>alekibango: no proble ;-)
10:50<alekibango>yeah, ping -c3 :)
10:51|-|visik7 [~visi@] has quit [Remote host closed the connection]
10:52<avdyk>I already set up xen on another box and domU has a network access, but on this one I can't :'(
10:52<alekibango>anyone here can give advice which network setting is best, if i have 1 ip address and want to run few servers on 1 PC like mail, www etc ?
10:52|-|jforbes [] has quit [Read error: Connection reset by peer]
10:53<alekibango>damn i forgot the -c 3
10:53|-|jforbes [] has joined #xen
10:55<alekibango>avdyk: alias ping='ping -c3'
10:55<avdyk>yeah ;-) even better ;-)
10:55<alekibango>must for me :)))
11:15|-|jerone [] has quit [Quit: Leaving]
11:21|-|avdyk [] has quit [Quit: got to go, cheers]
11:34|-|Basic_py [] has quit [Quit: Leaving]
11:39|-|athomas [] has quit [Quit: Leaving]
11:40|-|jasonmc [] has joined #xen
11:40|-|jasonmc [] has quit [Quit: ]
11:54|-|visik7 [] has joined #xen
11:58|-|bernarde [~bernarde@] has joined #xen
12:04|-|msinhore [] has quit [Quit: Fui embora]
12:08|-|parabelboi [] has quit [Read error: Connection reset by peer]
12:08|-|gerrit_ [] has joined #xen
12:09|-|anball [] has quit [Ping timeout: 480 seconds]
12:09|-|visik7 [] has quit [Read error: Connection reset by peer]
12:10|-|mastermind [] has joined #xen
12:20|-|stekloff [] has joined #xen
12:36|-|Basic_py [] has joined #xen
12:45|-|gerrit_ [] has quit [Ping timeout: 480 seconds]
13:40|-|lilo2_ [] has joined #xen
13:41|-|lilo2 [] has quit [Remote host closed the connection]
13:42|-|athena [] has quit [Remote host closed the connection]
13:43|-|athena [] has joined #xen
13:46<tessier__>Anyone know if xen can tftp the kernel image to boot?
13:46<tessier__>I am trying to build a completely diskless cpu node which uses AoE for disk storage.
13:46<tessier__>These cpu's are warm enough as it is, I don't wnt any disk in there.
13:46<tessier__>PXE can tftp the xen kernel itself but after that I am not clear how xen can get the domain0 kernel.
13:46<tessier__>It would be really nice if xen could tftp it.
13:49<tessier__>oh, wait.
13:49<tessier__>GRUB knows how to tftp! Sweet!
13:50<murb>tessier__: the nbgrub is useful!
14:02<tessier__>Yeah, I never knew grub could do that. Sure hope my network card is supported!
14:03<tessier__>The Linux kernel supports it so it should be at least theoretically possible that grub does.
14:04|-|deshantm [] has quit [Read error: Operation timed out]
14:04|-|elisboa [~elisboa@] has joined #xen
14:05<tessier__>hmm...apparently there is something called nbgrub and something called pxegrub
14:14|-|mdday [] has quit [Read error: Connection reset by peer]
14:22|-|visik7 [] has joined #xen
14:25|-|tobi [] has joined #xen
14:28|-|gerrit_ [] has joined #xen
14:28|-|mdday [] has joined #xen
14:44|-|lilo2_ changed nick to lilo2
15:00|-|riel [] has quit [Ping timeout: 480 seconds]
15:06|-|riel [~riel@2002:425c:4d62:1:4c2b:9dff:fe84:4b47] has joined #xen
15:07|-|cableman [] has joined #xen
15:18|-|riel [~riel@2002:425c:4d62:1:4c2b:9dff:fe84:4b47] has quit [Quit: Client exiting]
15:18|-|riel [] has joined #xen
15:22|-|visik7 [] has quit [Remote host closed the connection]
15:22|-|visik7 [] has joined #xen
15:30|-|zwane_work [] has quit [Ping timeout: 480 seconds]
15:30|-|cableman [] has quit [Remote host closed the connection]
15:48|-|aliguori [] has joined #xen
16:22|-|bernarde [~bernarde@] has quit [Read error: Connection reset by peer]
16:29|-|aliguori [] has quit [Quit: Ex-Chat]
16:33|-|aliguori [] has joined #xen
16:35|-|mejlholm [] has quit [Quit: Client exiting]
16:36|-|tobi [] has quit [Quit: tobi]
17:02|-|rharper [] has quit [Quit: Leaving]
17:05|-|hollisb [] has quit [Quit: leaving]
17:49|-|lucca [] has joined #xen
18:06|-|Basic_py [] has quit [Quit: Leaving]
18:30|-|jimix [] has quit [Quit: jimix]
19:07|-|Shoragan_ [] has quit [Quit: Leaving]
19:38|-|visik7 [] has quit [Remote host closed the connection]
19:43|-|horms [] has joined #xen
19:46|-|horms [] has quit [Quit: ]
19:50|-|gerrit_ [] has quit [Read error: Operation timed out]
20:08|-|mdday [] has quit [Quit: mdday]
21:16|-|rusty [] has joined #xen
21:36|-|rusty [] has quit [Quit: Ex-Chat]
21:37|-|rusty [] has joined #xen
21:40|-|aliguori [] has quit [Quit: Ex-Chat]
22:47|-|zwane_work [] has joined #xen
22:51|-|gerrit_ [] has joined #xen
22:59|-|VS_ChanLog [] has left #xen [Rotating Logs]
22:59|-|VS_ChanLog [] has joined #xen
23:14|-|horms [] has joined #xen
23:37|-|Basic_py [] has joined #xen
23:51|-|muli [] has quit [Quit: My damn controlling terminal disappeared!]
---Logclosed Wed Jun 28 00:00:50 2006