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

---Logopened Tue Jun 13 00:00:58 2006
00:03|-|Q3aiml [] has joined #xen
00:04|-|Netsplit <-> quits: VS_ChanLog, Q3aiml_, unriel, hbaum, killefiz, ag-, mooli, um
00:07|-|killefiz [] has joined #xen
00:12|-|ag- [] has joined #xen
00:18|-|um [] has joined #xen
00:21|-|unriel [] has joined #xen
00:22|-|mooli [] has joined #xen
00:26|-|hbaum [] has joined #xen
00:38|-|VS_ChanLog [] has joined #xen
00:41|-|mastermind [] has quit [Quit: Client exiting]
01:02|-|ag- [] has quit [Read error: Connection reset by peer]
01:02|-|ag- [] has joined #xen
01:10|-|muli [] has quit [Quit: My damn controlling terminal disappeared!]
01:11|-|ag- [] has quit [Remote host closed the connection]
01:12|-|ag- [] has joined #xen
01:20|-|ag- changed nick to Guest168
01:20|-|ag- [] has joined #xen
01:21|-|Guest168 [] has quit [Read error: Connection reset by peer]
01:29|-|ns [~nivedita@] has joined #xen
01:54|-|sdog [] has quit [Remote host closed the connection]
02:02|-|ag- [] has quit [Read error: Connection reset by peer]
02:37|-|parabelboi [~parabelbo@] has joined #xen
02:39|-|cableman [~cableman@] has quit [Remote host closed the connection]
02:49|-|rusty [] has quit [Quit: Ex-Chat]
02:58|-|sdog [~sdog@] has joined #xen
03:14|-|visik7 [~visi@] has joined #xen
03:16|-|mejlholm [] has joined #xen
03:24|-|sdague [] has quit [Remote host closed the connection]
03:24|-|sdague [] has joined #xen
03:26|-|mejlholm [] has quit [Quit: Leaving]
03:33|-|mejlholm [] has joined #xen
03:34|-|sdague [] has quit [Ping timeout: 480 seconds]
03:35|-|pvanhoof [~pvanhoof@] has joined #xen
03:37|-|Shoragan [] has joined #xen
03:56|-|athomas [] has joined #xen
04:41|-|parabelboi [~parabelbo@] has quit [Read error: Connection reset by peer]
04:43|-|parabelboi [] has joined #xen
04:47|-|sdague [] has joined #xen
05:11|-|ivan [~ikelly@] has joined #xen
05:24|-|visik7 [~visi@] has quit [Remote host closed the connection]
06:19|-|sun [] has joined #xen
06:19<sun>question - I'm trying to set up XEN to install Windows on a VT enabled machine
06:19<sun>and I can't seem to get the config right
06:20<sun>It complains that the "name" directive I defined is "not found"
06:32|-|ivan [~ikelly@] has quit [Quit: leaving]
06:32|-|Tv [] has joined #xen
07:00|-|mdday [] has joined #xen
07:01|-|Netsplit <-> quits: jimix, JViz, sdague, lilo2, sun, weasel, dansmith, mooli
07:02|-|Netsplit over, joins: sdague
07:04|-|sun_ [] has joined #xen
07:04|-|mooli [] has joined #xen
07:04|-|lilo2 [] has joined #xen
07:04|-|jimix [] has joined #xen
07:04|-|JViz [] has joined #xen
07:04|-|weasel [] has joined #xen
07:04|-|dansmith [] has joined #xen
07:05|-|JViz [] has quit [Read error: Connection reset by peer]
07:14|-|JViz [Anomaly@] has joined #xen
07:22|-|sun_ [] has quit [Remote host closed the connection]
07:59|-|lilo2 [] has quit [Quit: bbiab]
07:59|-|noni [] has quit [Quit: ]
08:02|-|fabien [~fabien@] has joined #xen
08:04<fabien>I want to test some modifications made on a xen0 kernel but I am a noob and I often get some kernel panic that reboot my machine
08:04<fabien>Anyone have tried to use qemu or boch to prevent this kind of "problem" ?
08:10|-|koki [] has joined #xen
08:11|-|lilo2 [] has joined #xen
08:12|-|chax [~chax@] has joined #xen
08:12<chax>hiyya !!
08:13<chax>a quick question reg xen implementation in linux
08:14|-|sdague [] has quit [Read error: Operation timed out]
08:14<chax>does the guest os see the same disk block <--> partition mapping as the base os ??
08:14<chax>i mean.
08:14<chax>will /usr/lib/a_something be same for both guestos and ring 0 os ?
08:15|-|bernarde [~bernarde@] has joined #xen
08:15|-|parabelboi [] has quit [Read error: Connection reset by peer]
08:20|-|bernarde [~bernarde@] has quit [Remote host closed the connection]
08:23|-|parabelboi [] has joined #xen
08:26|-|noni [] has joined #xen
08:27|-|chax [~chax@] has left #xen [Leaving]
08:31|-|bernarde [~bernarde@] has joined #xen
08:32|-|sdague [] has joined #xen
08:43|-|Tv [] has quit [Quit: foo]
08:45|-|hollisb [] has joined #xen
08:50|-|fabien [~fabien@] has quit [Quit: Quitte]
09:05|-|hollisb [] has quit [Quit: Leaving]
09:30|-|netman1 [~netman1@] has joined #xen
09:31|-|visik7 [~visi@] has joined #xen
09:37|-|rharper [] has joined #xen
09:39|-|Tv [] has joined #xen
09:43|-|jerone [] has joined #xen
09:57|-|hollisb [~hollisb@] has joined #xen
10:01|-|xai [] has joined #xen
10:02|-|xai [] has quit [Quit: ]
10:14|-|johnlev [] has joined #xen
10:28|-|mastermind [] has joined #xen
10:32|-|pvanhoof [~pvanhoof@] has quit [Remote host closed the connection]
10:38|-|parabelboi [] has quit [Read error: Connection reset by peer]
10:42|-|bernarde [~bernarde@] has quit [Remote host closed the connection]
10:44|-|muli [] has joined #xen
10:55|-|um [] has quit [Quit: Leaving]
11:00|-|DV_ [] has joined #xen
11:04|-|sdog [~sdog@] has quit [Remote host closed the connection]
11:15|-|ivan [~ikelly@] has joined #xen
11:30|-|Basic_py [] has joined #xen
11:37|-|Q3aiml [] has quit [Ping timeout: 480 seconds]
11:41|-|Q3aiml [] has joined #xen
11:46|-|pmontesinos [~pmontesi@] has joined #xen
11:47<pmontesinos>I am having soft lockups whenever I turn off domUs that make me restart the machine. Is anyone having thesame problme?
11:47<ns>think there is a bugzilla report open on that..which version of xen?
11:48[~]riel has 2 invites left - anybody ?
11:48<pmontesinos>unstable.. others won't boot my machine
11:49|-|athomas [] has quit [Quit: Leaving]
11:52<pmontesinos>yeah, I saw that bugzilla. I am trying to debug it, but it's funny, because most cpus are in the same function, safe_halt
11:52<pmontesinos>I would think that the softlockup detector would not need to run on those
11:52<pmontesinos>that are being "shut down"
11:55<ns> hmm, can't help you there..but what about races with stuff being shut down? might need to..
11:57<pmontesinos>I don't know.. it's getting frustrating
11:57<pmontesinos>too mnay reboots
11:57<ns>are you running on debug options?
11:57<pmontesinos>the kernel has debug support on it
11:58<pmontesinos>(domO kernel)
11:58<ns>turn it on in xen (hypervisor) too
11:59<pmontesinos>in xend?
12:00<pmontesinos>I already have loglevel debug
12:02<pmontesinos>ahh.. sorry, you mean in xen. Ok, I'll rebuild it
12:05<pmontesinos>ns: do you have an smp machine?
12:06<pmontesinos>more than 8 way?
12:07<ns>we can get hold of one
12:09|-|visik7 [~visi@] has quit [Remote host closed the connection]
12:34<johnlev>aliguori: there?
12:53|-|jerone [] has quit [Quit: Leaving]
12:58|-|muli [] has quit [Quit: Reconnecting]
12:58|-|muli [] has joined #xen
13:00|-|Sir_Ahzz [] has quit [Quit: Client exiting]
13:06<johnlev>hrm, why the heck do the tools set /dev/xen/evtchn non-blocking
13:08|-|lazyb0y_ [~henning@] has joined #xen
13:21|-|jerone [] has joined #xen
13:35|-|mejlholm [] has quit [Quit: Leaving]
13:38|-|pmontesinos [~pmontesi@] has quit [Quit: Leaving]
13:58|-|pvanhoof [~pvanhoof@] has joined #xen
14:09|-|Sir_Ahzz [~ahzz@] has joined #xen
14:09|-|mode/#xen [+o Sir_Ahzz] by ChanServ
14:24|-|swg [] has joined #xen
14:24<swg>is someone here?
14:33<swg> having some problems where Xen wouldn't start domUs... its weird, once I run the install script, they run again, but after I logout SSH, they stopped working
14:33<swg> running Debian atm
14:33<swg> just fails with Error: Device 0 (vif) could not be connected. Backend device not found.
14:33<koki>udevd is running?
14:33<swg> this goes away after I run the install script in the xen source folder but Xen stops working right after
14:34<swg> do I check in /etc/init.d/?
14:34<koki>are you running the debian packages?
14:34<swg> yes, I think I am
14:34<koki>then i do not know
14:35<swg> client-209-158-33-90:~# ps aux | grep udevd
14:35<swg>root 944 0.0 0.7 1568 472 ? S<s 03:19 0:00 udevd
14:36<swg> any ideas?
14:37<koki>can't remember, had that error message but solved it by installing xen 3.0 some months ago
14:38<rharper>swg: check /var/log/xen-hotplug.log
14:39<swg> k let c
14:39<swg> have all these errors
14:39<swg> interface vif1.0 does not exist!
14:39<swg>interface vif2.0 does not exist!
14:39<swg>interface vif3.0 does not exist!
14:39<swg>interface vif4.0 does not exist!
14:39<swg>interface vif5.0 does not exist!
14:39<swg>interface vif1.0 does not exist!
14:39<swg>interface vif2.0 does not exist!
14:39<swg>interface vif3.0 does not exist!
14:39<swg>interface vif4.0 does not exist!
14:39<swg>interface vif5.0 does not exist!
14:40<mikegrb>swg: don't flood
14:40<swg> sorry, it is my IRC client
14:40<swg> can't paste it into one line
14:40<mikegrb>your irc client typed all that stuff?
14:40<swg> it automatically splits the thing
14:40<mikegrb>as it should
14:40<koki>swg: /etc/init.d/xend start
14:40<mikegrb>you shouldn't paste that much text, use something like
14:41<koki>should change your net topology
14:41<swg> nope, didn't work
14:41<koki>can you console into the domu's?
14:42<swg> no, can't even start them
14:42<swg> it just splits out that it cannot find the vif interface and destorys the domU
14:42<koki>swg: you said sthg about ssh, ...
14:42<swg> yea
14:42<koki>doesnt make sense to me
14:42<swg> I think it's something with sessions or something
14:43<rharper>you can pass -c to the xm create command to see how far the domU is going before dying
14:43<swg> if I go in /usr/src/xen*
14:43|-|ns [~nivedita@] has quit [Quit: The voices in my head are telling me to...]
14:43<swg> yes -c is specified
14:43<swg> and run the make install script
14:43<swg> the domU runs again
14:43<swg> but if I logout of SSH
14:43<koki>what ssh?
14:43<swg> I am using SSH to logon
14:43<koki>it is a console
14:44<koki>not ssh
14:44<swg> ?
14:44<swg> I am logged on to root using SSH
14:44<swg> right
14:45<koki>and then. xm create -c bla
14:45<swg> yea
14:45<swg> and it splits out the error
14:45<koki>.. booting xen ....
14:45<swg> saying cannot find vif
14:45<swg> and dies
14:45<koki>well. recheck your config. try with the simplest provided ones
14:45<swg> have this
14:45<swg> Using config file "centos.cfg".
14:45<swg>Error: Device 0 (vif) could not be connected. Backend device not found.
14:46<swg> and then it just dies run after, doesn't boot at all
14:46<koki>sometimes works better using the dom0 kernel to boot even the domu
14:46<koki>not in production, but for testing
14:46<swg> eh what was that?
14:47<swg> I am currently using the xen-dom0 kernel right now
14:47<koki>but also for the domU?
14:47<swg> no, domU is using the domU kernel
14:47<koki>that's what i'm sayin
14:47<swg> but I think there is a problem that lyes on the dom0 kernel or some system settings
14:48<swg> what I don't get is why I could start guests fine until I logout out of SSH
14:48<swg> after running make install in /usr/src/xen* of course
14:48<koki>did you upgrade?
14:49<koki>or just install?
14:49<swg> upgrade Xen?
14:49<koki>why not?
14:49<swg> I just installed Xen off source
14:49<swg> 3.0.2-3
14:49<swg> 2
14:49<koki>ok, so you just installed
14:49<swg> right
14:50<swg> I wonder if this is some kind of Debian or SSH problem... sighs
14:51<koki>your network line .... vif = [ 'mac=00:16:3e:00:89:01, bridge=stud89' ]
14:51<koki>sthg like that?
14:51<swg> it's xenbr0
14:51<swg> and I didn't specify mac
14:51<koki>no need to do
14:52<swg> the thing is that the thing works and boots using that conf after running make install in /usr/src/xen*
14:52<koki>change: kernel = "/boot/vmlinuz-2.6.16-xenU" to kernel = "/boot/vmlinuz-2.6.16-xen0"
14:52<swg> lol will try
14:53<koki>so you might not find your scripts? --- you can alter the debug level in the xend config
14:54<swg> umm it boots for some reason lol
14:54<koki>now you know your client kernel sucks.
14:54<swg> probably let me try restarting SSH and see what happens
14:54<koki>rebuild like it is written in the manual and enjoy the beauty of xen
14:55<koki>swg: is your ssh more secure than mine so you have to shout it all the time?
14:55<swg> ?
14:56<swg> ah
14:56<swg> same thing happens now
14:56<swg> once I restarted the session, it doesn't even boot with the dom0 kernel
14:56<swg> which I don't get at all
14:57<swg> and if I change it back to xenU, it works again
14:57<swg> it seems that it works whenever I make changes to the configs
14:59|-|Q3aiml_ [] has joined #xen
15:02|-|Netsplit <-> quits: sdague, bored2sleep, dhendrix, klapmuetz, deshantm, koki, dansmith, jimix, jerone, weasel, (+8 more, use /NETSPLIT to show all of them)
15:02|-|Netsplit over, joins: DV_, netman1, sdague, mooli, jimix, weasel, dansmith
15:02|-|jimix [] has quit [Remote host closed the connection]
15:02|-|Netsplit over, joins: klapmuetz
15:03|-|jimix [] has joined #xen
15:03|-|[] changed the topic of #xen: || Xen 3.0.2 is now available - bugfixes, 2.6.16, and SVM support
15:03|-|koki_ [] has joined #xen
15:03|-|Netsplit over, joins: hbaum
15:04|-|Netsplit over, joins: deshantm
15:04|-|Netsplit over, joins: unriel
15:05|-|Netsplit over, joins: jerone
15:05|-|Netsplit over, joins: bored2sleep
15:06|-|Netsplit over, joins: jdmason
15:06|-|Netsplit over, joins: dhendrix
15:07|-|Netsplit over, joins: sunny
15:13<johnlev>there seems to be no point in /dev/xen/evtchn being non-blocking since it's only ever read from in response to a select() anyway
15:13|-|ns [] has joined #xen
15:14|-|noni [] has quit [Remote host closed the connection]
15:14|-|lilo2 [] has quit [Remote host closed the connection]
15:15|-|lilo2 [] has joined #xen
15:20|-|noni [] has joined #xen
15:23|-|visik7 [~visi@] has joined #xen
15:24|-|Netsplit <-> quits: jerone
15:30|-|lilo2 [] has quit [Quit: brb]
15:30|-|noni [] has quit [Remote host closed the connection]
15:41|-|zwane_work [~zwane@] has quit [Ping timeout: 480 seconds]
15:46|-|jerone [] has joined #xen
15:48|-|henning__ [~henning@] has joined #xen
15:50|-|pdx6 [~ballew@] has quit [Quit: leaving]
15:50|-|pdx6 [~ballew@] has joined #xen
15:52|-|noni [] has joined #xen
15:53|-|lilo2 [] has joined #xen
15:55<aliguori>johnlev, actually, i believe that was a result of a bug ewan found
15:55<aliguori>something like an event channel becomes active but is closed b/c the domain goes away or something
15:55<aliguori>it was leading to consoled lockups
15:55|-|lazyb0y_ [~henning@] has quit [Ping timeout: 480 seconds]
15:55<johnlev>that sounds like a bug in the evtchn driver
15:56<johnlev>and it's worth pointing out the console code explicitly loops until it can read something!
15:56<johnlev>xenstored does barf_perror()...
15:56<aliguori>johnlev, what, in particular, are you referring to?
15:56<aliguori>you mean a read_sync?
15:57<aliguori>oh, well, what can I say, I guess I'm a coder than Rusty :-P
15:57<aliguori>(yeah right!)
15:57<johnlev>did you leave off the adjective on purpose? :)
15:58<johnlev>is the changeset you're referring to I think
16:00<aliguori>apparently my fingers wouldn't even let me make that claim as a joke :-)
16:01<johnlev>am I right that's what you were remembering? it's not related to the evtchn device...
16:01<aliguori>one sec
16:01<aliguori>it probably is
16:01<aliguori>my memory is likely faulty
16:02<johnlev>I'm just going to send this patch out and see what people think. I may end up looking like a fool but at least I'll find out :)
16:04|-|DV_ [] has quit [Remote host closed the connection]
16:05|-|aliguori [] has quit [Quit: Ex-Chat]
16:06|-|aliguori [] has joined #xen
16:08|-|swg [] has quit [Read error: Connection reset by peer]
16:27|-|tobi [] has joined #xen
16:28|-|netman1 [~netman1@] has quit [Remote host closed the connection]
16:40|-|hollisb [~hollisb@] has quit [Quit: leaving]
16:40|-|jimix [] has quit [Quit: jimix]
16:53|-|ag- [] has joined #xen
17:28|-|Shoragan [] has quit [Quit: Leaving]
17:30|-|zwane_work [~zwane@] has joined #xen
17:38|-|ivan [~ikelly@] has quit [Quit: leaving]
17:40|-|rharper [] has quit [Quit: Leaving]
18:04|-|zwane_work [~zwane@] has quit [Ping timeout: 480 seconds]
18:07|-|rpg [~rpg@] has quit [Remote host closed the connection]
18:37|-|rusty [] has joined #xen
18:42|-|Netsplit <-> quits: noni, sdague, tobi, weasel, dansmith, ag-, mooli, bored2sleep, koki_
18:42|-|pvanhoof [~pvanhoof@] has quit [Remote host closed the connection]
18:42|-|Netsplit over, joins: ag-, tobi, noni, bored2sleep, koki_, sdague, mooli, weasel, dansmith
18:43|-|[] changed the topic of #xen: || Xen 3.0.2 is now available - bugfixes, 2.6.16, and SVM support
18:47|-|visik7 [~visi@] has quit [Remote host closed the connection]
19:08|-|um [~um@] has joined #xen
19:34|-|Basic_py [] has quit [Quit: Leaving]
20:08|-|ns [] has quit [Quit: The voices in my head are telling me to...]
20:11|-|horms [] has joined #xen
20:21|-|johnlev [] has quit [Ping timeout: 480 seconds]
20:23|-|swg_ [] has joined #xen
20:32|-|swg_ [] has quit [Quit: Trillian (]
20:37|-|swg [] has joined #xen
20:37<swg> hello everyone
20:40<swg>does anyone have any idea what is happening if I can't start a Xen guest on the root folder [~] but able to on other folders (ex. /bin)
21:00|-|hansq [~hanis@] has joined #xen
21:12|-|Basic_py [] has joined #xen
21:15<aliguori>swg, be more specific
21:15<swg> <-- here is my problem
21:16<aliguori>you have a centos.cfs in /root that isn't valid
21:17<aliguori>if there is no config file in the working directory (and an absolute path isn't specified), it checks for /etc/xen/
21:17<aliguori>in this case, you're /etc/xen/centos.cfg is valid
21:17<aliguori>if you just did xm create -c /etc/xen/centos.cfg, it would work no matter where you did it from
21:18<swg>indeed I did store my old config in ~ heh, thats why
21:18<swg>I expected it to start from /etc/xen
21:18<swg>thanks so much :P
21:29|-|swg [] has left #xen []
22:02|-|zwane_work [~zwane@] has joined #xen
22:12|-|ns [~nivedita@] has joined #xen
22:20|-|jerone [] has quit [Ping timeout: 480 seconds]
22:59|-|VS_ChanLog [] has left #xen [Rotating Logs]
22:59|-|VS_ChanLog [] has joined #xen
23:58|-|mooli [] has quit [Ping timeout: 480 seconds]
---Logclosed Wed Jun 14 00:00:41 2006