TheGrebs.com:IRC Logs:#xen:2007:01:22

---	Log	opened Mon Jan 22 00:00:48 2007
00:05	\|-\|	aw [~awilliam@156.153.254.69] has quit [Quit: Leaving]
00:19	\|-\|	guillaume_t [~guillaune@129.184.84.11] has joined #xen
01:31	\|-\|	jerone [~jerone@adsl-71-145-130-136.dsl.austtx.sbcglobal.net] has quit [Remote host closed the connection]
01:56	\|-\|	mastermind [~mastermin@mastermind.kaltenbrunner.cc] has quit [Quit: Client exiting]
02:18	\|-\|	mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has joined #xen
03:14	\|-\|	visik7 [~visi@87.1.21.11] has joined #xen
03:28	\|-\|	visik7 [~visi@87.1.21.11] has quit [Remote host closed the connection]
03:29	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has joined #xen
03:34	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has quit []
03:46	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has joined #xen
03:56	<AllenJB>	Trying to set up xen on Gentoo and I've got a situation where the domU crashes but I can't find any error messages to tell me why. The domU config and log file are at http://rafb.net/p/uC3AxF95.html - How can I get more information on what's causing the domU to crash?
04:22	\|-\|	athomas [~athomas@host86-134-167-36.range86-134.btcentralplus.com] has joined #xen
04:28	\|-\|	DavidS [~david@chello062178045213.16.11.tuwien.teleweb.at] has quit [Quit: Leaving.]
05:12	\|-\|	fernando [~fernando@189.0.131.108] has joined #xen
05:20	\|-\|	bernarde [~bernarde@143.106.7.137] has joined #xen
06:25	\|-\|	guillaume_t [~guillaune@129.184.84.11] has quit [Remote host closed the connection]
06:42	\|-\|	msinhore [~msinhore@mail.samurai.com.br] has joined #xen
06:51	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has quit [Ping timeout: 480 seconds]
06:51	\|-\|	mday_away changed nick to mdday
06:54	\|-\|	danp1 [~berrange@pool-72-93-175-181.bstnma.east.verizon.net] has joined #xen
06:56	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has joined #xen
07:09	\|-\|	aw [~awilliam@c-24-9-84-32.hsd1.co.comcast.net] has joined #xen
07:36	\|-\|	gce [~someone@c-24-10-80-26.hsd1.ca.comcast.net] has quit [Quit: Leaving]
07:38	\|-\|	infernix [~nix@spirit.infernix.net] has quit [Remote host closed the connection]
07:40	\|-\|	agrif_away changed nick to agriffis
07:47	\|-\|	guillaume_t [~guillaune@129.184.84.11] has joined #xen
07:58	\|-\|	cableman [~cableman@0x50a142d3.hrnxx3.adsl-dhcp.tele.dk] has joined #xen
08:01	\|-\|	guillaume_t [~guillaune@129.184.84.11] has quit [Quit: Leaving]
08:09	\|-\|	ns [~niv@bi01p1.co.us.ibm.com] has joined #xen
08:11	\|-\|	infernix [~nix@spirit.infernix.net] has joined #xen
08:11	\|-\|	infernix [~nix@spirit.infernix.net] has quit []
08:11	\|-\|	clalance [~clalance@nat-pool-bos.redhat.com] has joined #xen
08:17	\|-\|	fernando [~fernando@189.0.131.108] has quit [Ping timeout: 480 seconds]
08:18	\|-\|	bernarde [~bernarde@143.106.7.137] has quit [Remote host closed the connection]
08:18	\|-\|	infernix [~nix@spirit.infernix.net] has joined #xen
08:34	\|-\|	fernando [~fernando@189.0.131.108] has joined #xen
08:35	\|-\|	ivan [~ikelly@5ac197ad.bb.sky.com] has joined #xen
08:43	\|-\|	agriffis changed nick to agrif_away
08:43	\|-\|	agrif_away changed nick to agriffis
08:47	\|-\|	jimix [~jimix@c-67-189-187-152.hsd1.ny.comcast.net] has joined #xen
09:07	\|-\|	DavidS [~david@chello062178045213.16.11.tuwien.teleweb.at] has joined #xen
09:14	\|-\|	Piet [hiddenserv@tor.noreply.org] has joined #xen
09:14	<Piet>	hi
09:15	<Piet>	i'm setting up a firewall script running on a dom0. it references the guest servers through their vif's.
09:16	<Piet>	however, i realize the vifs change with each reboot of the vservers and was told they would also change when restarting xen
09:16	<Piet>	is there a way to statically assign vif's to xen guests?
09:16	<icblenke>	augment your vif-script with whatever unique things you do with your vifs.
09:17	<icblenke>	rather than statically assign vifs, I just made my own vif-script to do the "special" things I need to do whenever a domain's backend comes up.
09:17	<icblenke>	xm list, find the domain name of the current vif being brought up, then do whatever configuration lookup based on the domain name for the knobs you need to turn for your unique vif configuration.
09:19	<Piet>	this would mean i would need to restart the firewall every time a guest restarts
09:20	<Piet>	which means it becomes prone to a dos
09:20	<icblenke>	depends on how you do your firewall rules.
09:20	<Piet>	i use shorewall
09:20	<icblenke>	if you add a chain for each host, and then just alter that host's chain, no worries.
09:21	<icblenke>	if you use a precanned ruleset manager like shorewall, you may need to reload the entire thing every time, yes.
09:21	<Piet>	hmm, i think shorewall does have some way to tweak chains, i'll check into that
09:21	<icblenke>	this is why I wrote my own iptables rule manager.
09:22	<Piet>	is that available somewhere under some terms?
09:22	<icblenke>	nope. it's fairly specific to my current employer. it imposes some limitations on what can be done, but the structure makes it easier to manage.
09:23	\|-\|	plars [~plars@bi01p1.co.us.ibm.com] has joined #xen
09:24	<Piet>	if i decide not to do it by hacking the vif script and doing the dynamic firewall vodoo, do you think using ip addresses to reference the guests is sufficient?
09:24	\|-\|	rharper [~rharper@bi01p1.co.us.ibm.com] has joined #xen
09:25	\|-\|	rharper [~rharper@bi01p1.co.us.ibm.com] has quit []
09:25	\|-\|	rharper [~rharper@bi01p1.co.us.ibm.com] has joined #xen
09:26	<Piet>	of course it's a tradeoff in a way, but as i statically assign ip addresses and am probably stuck with shorewall on this system (client likes it), I assume it may suffice in terms of security and not make the system prone to dos in the way an externally triggered shorewall restart probably would.
09:39	\|-\|	rpg [~rpg@bi01p1.co.us.ibm.com] has joined #xen
09:42	\|-\|	DavidS [~david@chello062178045213.16.11.tuwien.teleweb.at] has quit [Quit: Leaving.]
09:42	\|-\|	msinhore [~msinhore@mail.samurai.com.br] has quit [Quit: scp -C msinhore home:msinhore]
09:50	<icblenke>	depending on your rules and how you have your iptables configured, you could just use bridged interfaces.
09:59	\|-\|	KriP [~kp@yancey.unixworld.dk] has joined #xen
10:02	\|-\|	icblenke [~icblenke@magic.skylab.org] has quit [Ping timeout: 480 seconds]
10:02	\|-\|	bored2sleep [~bored2sle@66.111.53.150] has quit [Ping timeout: 480 seconds]
10:03	\|-\|	bernarde [~bernarde@32.104.18.240] has joined #xen
10:03	\|-\|	bored2sleep [~bored2sle@66.111.53.150] has joined #xen
10:04	\|-\|	jerone [~jerone@bi01p1.co.us.ibm.com] has joined #xen
10:05	\|-\|	hbaum [~hbaum@bi01p1.co.us.ibm.com] has joined #xen
10:06	\|-\|	hollisb [~hollisb@bi01p1.co.us.ibm.com] has joined #xen
10:06	\|-\|	brianw [~ahzz@pool-71-170-81-199.dllstx.fios.verizon.net] has joined #xen
10:09	\|-\|	jerone [~jerone@bi01p1.co.us.ibm.com] has quit []
10:12	\|-\|	jerone [~jerone@bi01p1.co.us.ibm.com] has joined #xen
10:17	\|-\|	msinhore [~msinhore@mail.samurai.com.br] has joined #xen
10:19	\|-\|	icblenke [~icblenke@magic.skylab.org] has joined #xen
10:36	\|-\|	Darxus [~darxus@panic.chaosreigns.com] has joined #xen
10:43	<Piet>	i have more guests than public ip addresses, so plain bridging is not an option
10:43	<Piet>	nice idea, though
10:48	\|-\|	ahs3_away changed nick to ahs3
10:52	\|-\|	zwane_r3k [~zwane@S0106001217d33fa6.vc.shawcable.net] has quit [Ping timeout: 480 seconds]
10:54	\|-\|	Darxus [~darxus@panic.chaosreigns.com] has left #xen []
10:55	\|-\|	Darxus [~darxus@panic.chaosreigns.com] has joined #xen
10:58	\|-\|	aliguori [~anthony@cpe-70-112-17-156.austin.res.rr.com] has quit [Quit: Leaving]
11:07	\|-\|	sputhenp [~sputhenp@202.80.58.210] has quit [Quit: Leaving]
11:18	\|-\|	aliguori [~anthony@bi01p1.co.us.ibm.com] has joined #xen
11:27	\|-\|	zwane_r3k [~zwane@h70-68-160-192.sbm.shawcable.net] has joined #xen
11:33	\|-\|	mulix [~mulix@87.69.40.180.cable.012.net.il] has joined #xen
11:41	\|-\|	mastermind [~mastermin@mastermind.kaltenbrunner.cc] has joined #xen
11:43	\|-\|	bernarde [~bernarde@32.104.18.240] has quit [Remote host closed the connection]
11:54	\|-\|	Shoragan [~shoragan@datenfreihafen.org] has quit [Remote host closed the connection]
11:54	\|-\|	Shoragan [~shoragan@datenfreihafen.org] has joined #xen
12:04	\|-\|	Basic_py [~Basic@warden.real-time.com] has quit [Quit: Leaving]
12:22	\|-\|	Piet_ [hiddenserv@tor.noreply.org] has joined #xen
12:29	\|-\|	Piet [hiddenserv@tor.noreply.org] has quit [Ping timeout: 480 seconds]
12:29	\|-\|	athomas [~athomas@host86-134-167-36.range86-134.btcentralplus.com] has quit [Quit: Leaving]
12:34	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has quit [Remote host closed the connection]
12:46	\|-\|	Basic_py [~Basic@gatekeeper.real-time.com] has joined #xen
12:49	\|-\|	swingle [~swingle@248.Red-81-40-74.staticIP.rima-tde.net] has joined #xen
12:50	<swingle>	hi
12:59	<swingle>	someone told me last week that the linux framebuffer wouldnt work with xen, can anybody explain me why?
12:59	<swingle>	ive checked the hypervisor console code and it only messes with vga when you set console=vga on the command line
13:00	<swingle>	so when you set console=com1 the linux framebuffer should work ... ??
13:03	<icblenke>	as long as a linux framebuffer driver talks directly to a PCI device...
13:03	<icblenke>	VESA is right out though.
13:03	<swingle>	i want to use vesafb
13:03	<swingle>	why doesnt that one work?
13:03	<icblenke>	VESA is a BIOS thing.
13:03	<swingle>	yep i know
13:03	<swingle>	but i can use the vesa driver with an X server
13:03	<icblenke>	the xen hypervisor runs ring0. even dom0 runs ring1.
13:03	<swingle>	and it works in dom0
13:04	<icblenke>	someone else here should probably speak up then.
13:04	<swingle>	you know who i should bother? :)
13:04	<icblenke>	they're all being rather quiet.
13:04	<swingle>	then ill camp here hehe
13:08	<danp1>	swingle: what's the problem with vesa ? my X server runs just fine with the vesa driver
13:08	<swingle>	my xserver runs fine but my framebuffer doesnt
13:09	<swingle>	im setting up an embedded system and i dont want to have an xserver on it, i just need a vnc client and id like to run it on the linux framebuffer with the vesa driver
13:09	\|-\|	pvanhoof [~pvanhoof@d54C0EE14.access.telenet.be] has joined #xen
13:10	<swingle>	it doesnt even complain it just doesnt switch to framebuffer mode
13:12	<AllenJB>	Trying to set up xen on Gentoo and I've got a situation where the domU crashes but I can't find any error messages to tell me why. The domU config and log file are at http://rafb.net/p/xVpICW94.html - How can I get more information on what's causing the domU to crash?
13:33	<icblenke>	AllenJB: try setting your on_crash, on_reboot, and on_shutdown to "preserve"
13:38	<AllenJB>	icblenke: OK. I've got a preserved crashed domain. It's not given me any more output. What can I do with it to get information about why it crashed?
13:38	<icblenke>	attach to the console?
13:39	<AllenJB>	nothing there
13:39	<icblenke>	at all?
13:39	<AllenJB>	nope
13:39	<icblenke>	check your logfiles in /var/log/xen/
13:40	<icblenke>	it sounds like your domU kernel is never getting the chance to boot
13:40	<AllenJB>	That directory doesn't exist
13:40	<icblenke>	odd. what distribution doesn't have a /var/log/xen/?
13:41	<AllenJB>	Created the directory and till nothing there.
13:41	<icblenke>	reboot the dom0.
13:41	<icblenke>	if still nothing appears in /var/log/xen, your distribution has decided to put the xen logs somewhere else.
13:41	<AllenJB>	I'm using Gentoo, using the latest versions of the xen-* packages in portage and metalog as my system logger
13:42	<icblenke>	You may have to look at your gentoo packaging to see what they've done to it.
13:43	<swingle>	yep take a look at the ebuild they are easy to follow
13:43	[~]	AllenJB waits 5 minutes for his server to reboot
13:43	<icblenke>	you run gentoo. you are used to waiting.
13:44	<AllenJB>	Yeah, I'm getting quite good at bash scripting now. One of the reasons I love Gentoo is the ease of puting stuff under the control of the package manager
13:44	<AllenJB>	Waiting? What waiting?
13:45	<swingle>	ebuilds are written in python not bash
13:46	<AllenJB>	No, portage is written in python, but the ebuilds are written in bash
13:46	<AllenJB>	go ask #gentoo-dev-help =P
13:46	<icblenke>	emerge system. wait. emerge world. wait.
13:46	<swingle>	ive made many ebuilds Allen
13:47	<AllenJB>	icblenke: Well, if that's how you choose to spend your life. I'd rather do other things in the periods where you wait =P
13:47	<AllenJB>	icblenke: linux is a multi-tasking OS after all
13:47	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has joined #xen
13:48	<AllenJB>	swingle: What does the first line say: http://devmanual.gentoo.org/ebuild-writing/file-format/index.html ? =P
13:48	<icblenke>	mmhmm.
13:48	<AllenJB>	swingle: I'm amazed they worked if you wrote all your ebuilds in python
13:48	\|-\|	sdague [~sdague@user-12lc6iq.cable.mindspring.com] has quit [Quit: Disconnecting from stoned server.]
13:48	\|-\|	sdague [~sdague@user-12lc6iq.cable.mindspring.com] has joined #xen
13:48	<swingle>	i wrote my ebuilds in the pseudo language they give you
13:48	<AllenJB>	It's not a pseudo language. It's bash script.
13:48	<swingle>	they defined many functions just for the ebuild system
13:49	<swingle>	ok try to interpret a single ebuild in bash
13:49	<icblenke>	this is #xen, not gentoo bashing.
13:49	<swingle>	icblenke, your point
13:50	<AllenJB>	That won't work. Just because you define some stuff in another language, that doesn't turn it into a pseudo language. It's bash script with a framework written in python if you want to be picky.
13:50	<swingle>	ok you can say it that way if you want
13:50	<swingle>	anyway i came here looking for a way to use the linux framebuffer with xen not to argue about gentoo
13:51	<AllenJB>	Rebooting changed nothing. Still nothing in /var/log/xen/
13:52	<AllenJB>	The only xen specific log files i have are in /var/log/: xend.log; xend-debug.log (empty); xen-hotplug.log (empty)
13:53	<icblenke>	those files would normally be in /var/log/xen. gentoo has moved them.
13:53	<icblenke>	so look in your xend.log
13:55	<ns>	or rather, gentoo has not yet moved them into /var/log/xen - they used to be in the top level /var/log dir.
13:55	<AllenJB>	That's posted on my pastebin that I posted earlier. As far as I can see there's nothing that indicates what caused the domU to crash there. If you can see something, please enlighten me
14:00	<icblenke>	you'll need to turn up your debugging.
14:01	<icblenke>	add: export XEND_DEBUG=1; export XENSTORE_TRACE=1 to your xend init script before xend is started.
14:01	<icblenke>	also: udevcontrol log_priority=debug
14:02	<icblenke>	then tail your xend.log and daemon.log (or messages, or whatever gentoo uses for udev debug logging)
14:08	<AllenJB>	Nothing useful there - in fact the output appears to be exactly what's in the xend-debug.log I already posted.
14:17	\|-\|	DavidS [~david@217.19.46.18] has joined #xen
14:18	<icblenke>	and your udev debugging shows no problems either.
14:21	\|-\|	fernando [~fernando@189.0.131.108] has quit [Ping timeout: 480 seconds]
14:22	<icblenke>	also, what are you getting in your xendstore.log ?
14:22	<icblenke>	er, xenstored.log
14:23	<AllenJB>	I can't see any such file.
14:23	<AllenJB>	icblenke: udev logs: No errors or warnings. Can't see abything else that might be of interest
14:24	<icblenke>	export XENSTORED_TRACE=1
14:24	<icblenke>	missed that "D" in my above suggestion.
14:24	<icblenke>	xenstored will then write a rather verbose xenstored.log full of interesting tidbits as things use xenstore.
14:26	<icblenke>	again, xend starts xenstored and xenconsoled on boot. setting the above variables in your init script so that xend inherits them as part of its environment will turn up the debugging information.
14:27	<AllenJB>	icblenke: The file still doesn't exist. No extra information in xend.log
14:27	<icblenke>	shrug don't know what to tell you then.
14:28	<AllenJB>	woot - I have an unsolvable problem -.-
14:28	<icblenke>	nothing that a week of beating your head against your keyboard won't solve. trust me, I've been there.
14:29	<icblenke>	hell, I've only been running Xen for about 2 months now. the first month was nothing but pain trying to get my xenconsoled not to wedge while daemonizing with my version of glibc.
14:29	<icblenke>	Welcome To Xen.
14:30	<AllenJB>	I set up xen on a previous machine and it worked first time with no problems
14:30	<AllenJB>	Unfortunately that machine died so I'm having to set it up all over again
14:30	<icblenke>	repeat what you did last time?
14:31	<AllenJB>	I have done - used the guide on Gentoo Wiki last time, used it again this time.
14:31	[~]	AllenJB thinks he's cursed
14:31	<icblenke>	that's the fun with a source based distribution like gentoo.
14:32	<AllenJB>	I couldn't find out why the old machine died. I tracked it down to some problem with mobo, cpu and PSU - but couldn't solve it despite having 2 PSUs, 3 mobos and 3 CPUs to mix and match
14:36	\|-\|	agney [~agney@201.59.6.122] has joined #xen
14:36	<aliguori>	AllenJB: I strongly suspect your domU kernel config doesn't have the right drivers enabled
14:36	<aliguori>	specifically, I don't think you have the xen console driver enabled and problem don't have the xen block driver enabled
14:37	<aliguori>	noting that you'd have to have them compiled in statically
14:37	<aliguori>	since you aren't using an initrd
14:37	<aliguori>	I believe that genkernel is capable of building xen kernels right? I would use that along with the corresponding initrd that it generates
14:37	<AllenJB>	My domU kernel is all static - I disabled module support
14:38	<AllenJB>	I don't touch genkernel
14:38	<aliguori>	okay, well, I assume you don't have the right drivers compiled in
14:38	<aliguori>	if you aren't seeing any console output, you most certainly don't have the console driver enabled
14:38	<aliguori>	people give genkernel too hard a time, I always liked it :-)
14:39	<aliguori>	if you had the console driver, I'd expect you would see an "unable to mount root" error which would probably be caused by lacking of a proper block driver (or having scsi drivers enabled which will conflict with blkfront)
14:51	\|-\|	slim [~akil@cust150-45.tvcabo.co.mz] has joined #xen
14:51	\|-\|	slim [~akil@cust150-45.tvcabo.co.mz] has left #xen []
14:56	<AllenJB>	aliguori: Where should the xen console driver that you're talking about be?
14:56	<aliguori>	in the domU kernel config
14:56	<AllenJB>	where in menuconfig?
14:58	<AllenJB>	ahh - think I may have found it - "Xen TPM Support" under "Device Drivers -> Char. Devices -> TPM Support"
15:00	<hollisb>	no
15:00	<hollisb>	TPM is not the console
15:02	<AllenJB>	Oh well, some of the settings were disbaled, so I've enabled them and am recompilnig the kernels to see if it makes a difference. Also enabled all the Xen debugging items which might give me more info (didn't realise I'd left them off)
15:05	<aliguori>	make sure you have it set to be an unprivileged domain
15:19	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has quit [Read error: Connection reset by peer]
15:19	\|-\|	visik7 [~visi@87.1.21.11] has joined #xen
15:20	\|-\|	fernando [~fernando@189.0.156.100] has joined #xen
15:25	\|-\|	msinhore [~msinhore@mail.samurai.com.br] has quit [Ping timeout: 480 seconds]
15:32	\|-\|	swingle [~swingle@248.Red-81-40-74.staticIP.rima-tde.net] has quit [Quit: Leaving]
15:36	\|-\|	msinhore [~msinhore@correio.samurai.com.br] has joined #xen
15:47	\|-\|	Piet__ [hiddenserv@tor.noreply.org] has joined #xen
15:53	\|-\|	Piet_ [hiddenserv@tor.noreply.org] has quit [Ping timeout: 480 seconds]
15:58	\|-\|	mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has quit [Quit: Leaving]
15:58	\|-\|	cableman [~cableman@0x50a142d3.hrnxx3.adsl-dhcp.tele.dk] has quit [Quit: Leaving]
16:13	\|-\|	Piet__ changed nick to Piet
16:16	\|-\|	motr1n [~ash@38.96.133.11] has joined #xen
16:16	<motr1n>	hey, i'm having a problem with xen on centos4.4, with "Error: Device 0 (vif) could not be connected. Hotplug scripts not working."
16:16	<motr1n>	so far no help from googling the mailing lists
16:16	<motr1n>	bridge utils are installed, netloop.ko is loaded
16:16	<motr1n>	can anyone help?
16:19	<AllenJB>	I'm now getting the following error in xend.log when I start my domU: [2007-01-22 22:24:06 xend.XendDomainInfo] WARNING (XendDomainInfo:234) No vm path in store for existing domain 0
16:19	<AllenJB>	(Well, not error, warning)
16:19	<AllenJB>	What does thi s warning mean and what can I do about it?
16:20	<AllenJB>	My domU's config file: http://rafb.net/p/Og2QIZ83.html
16:24	\|-\|	jwb_ [~jwboyer@rchp4.rochester.ibm.com] has quit [Remote host closed the connection]
16:32	<icblenke>	that warning says that the path /vm/{guid} for the domain in question didn't already exist.
16:32	<icblenke>	(in xenstore)
16:33	<icblenke>	to learn what that means, try "xenstore-ls" or "xenstore-list" or any of the other "xenstore-*" commands.
16:35	<AllenJB>	So that's safe to ignore then?
16:37	<AllenJB>	I still can't find any mention of a "xen console driver" or anything similar in the kernel config for either dom0 or domU
16:38	<icblenke>	do you see the other Xen options when you build those kernels?
16:38	<AllenJB>	yes
16:38	<AllenJB>	frontend / backend stuff and various other bits
16:39	<AllenJB>	I tried searching for "xen" in menuconfig too but couldn't see anything there
16:42	\|-\|	visik7 [~visi@87.1.21.11] has quit [Read error: Connection reset by peer]
16:43	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has joined #xen
16:43	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has quit [Read error: Connection reset by peer]
16:43	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has joined #xen
16:45	\|-\|	DavidS [~david@217.19.46.18] has quit [Ping timeout: 480 seconds]
16:48	[~]	AllenJB gives Xen a good kick - "Work damnit!"
17:03	\|-\|	rpg [~rpg@bi01p1.co.us.ibm.com] has quit [Remote host closed the connection]
17:06	\|-\|	KriP [~kp@yancey.unixworld.dk] has quit [Quit: Leaving]
17:08	\|-\|	hollisb [~hollisb@bi01p1.co.us.ibm.com] has quit [Quit: leaving]
17:25	\|-\|	motr1n [~ash@38.96.133.11] has quit [Quit: [BX] The Invisible Man uses BitchX, you just can't see it!]
17:26	\|-\|	rpg [~rpg@bi01p1.co.us.ibm.com] has joined #xen
17:41	\|-\|	aliguori [~anthony@bi01p1.co.us.ibm.com] has quit [Remote host closed the connection]
17:50	\|-\|	msinhore [~msinhore@correio.samurai.com.br] has quit [Ping timeout: 480 seconds]
18:08	\|-\|	mdday changed nick to mday_away
18:16	\|-\|	clalance [~clalance@nat-pool-bos.redhat.com] has quit [Quit: Leaving]
18:20	<brendan>	anybody else getting an undefined PG_foreign error in mm/page_alloc.c from xen-unstable?
18:20	\|-\|	zwane_r3k [~zwane@h70-68-160-192.sbm.shawcable.net] has quit [Ping timeout: 480 seconds]
18:23	\|-\|	jerone [~jerone@bi01p1.co.us.ibm.com] has quit [Quit: jerone]
18:28	\|-\|	rharper [~rharper@bi01p1.co.us.ibm.com] has quit [Quit: Leaving]
18:34	\|-\|	ahs3 changed nick to ahs3_away
18:39	\|-\|	hbaum [~hbaum@bi01p1.co.us.ibm.com] has left #xen [Client exiting]
18:43	\|-\|	thwollex [~thwollex@c-ca6fe253.538-1-64736c21.cust.bredbandsbolaget.se] has joined #xen
18:47	\|-\|	aliguori [~anthony@cpe-70-112-17-156.austin.res.rr.com] has joined #xen
18:51	\|-\|	bernarde [~bernarde@201.72.60.80] has joined #xen
19:00	\|-\|	Basic_py [~Basic@gatekeeper.real-time.com] has quit [Quit: Leaving]
19:08	\|-\|	hollisb [~hollisb@user-0vvdf2d.cable.mindspring.com] has joined #xen
19:10	\|-\|	jimix [~jimix@c-67-189-187-152.hsd1.ny.comcast.net] has quit [Quit: jimix]
19:10	\|-\|	rpg [~rpg@bi01p1.co.us.ibm.com] has quit [Remote host closed the connection]
19:11	\|-\|	ns [~niv@bi01p1.co.us.ibm.com] has quit [Quit: .]
19:20	\|-\|	zwane_r3k [~zwane@S0106001217d33fa6.vc.shawcable.net] has joined #xen
19:52	\|-\|	agriffis changed nick to agrif_away
19:52	\|-\|	Shoragan [~shoragan@datenfreihafen.org] has quit [Quit: changing servers]
19:53	\|-\|	Shoragan [~shoragan@datenfreihafen.org] has joined #xen
20:14	\|-\|	fernando [~fernando@189.0.156.100] has quit [Quit: Leaving]
20:37	\|-\|	pvanhoof [~pvanhoof@d54C0EE14.access.telenet.be] has quit [Remote host closed the connection]
20:40	\|-\|	visik7 [~visi@host11-21-dynamic.1-87-r.retail.telecomitalia.it] has quit [Ping timeout: 480 seconds]
20:41	\|-\|	visik7 [~visi@82.54.163.182] has joined #xen
20:56	\|-\|	danp1 [~berrange@pool-72-93-175-181.bstnma.east.verizon.net] has left #xen []
21:12	\|-\|	jwb_ [~jwboyer@67-41-71-127.roch.qwest.net] has joined #xen
21:14	\|-\|	jwb_ [~jwboyer@67-41-71-127.roch.qwest.net] has quit []
21:20	\|-\|	hollisb [~hollisb@user-0vvdf2d.cable.mindspring.com] has quit [Quit: Leaving]
21:28	\|-\|	bernarde [~bernarde@201.72.60.80] has quit [Remote host closed the connection]
21:31	\|-\|	agrif_away changed nick to agriffis
21:46	\|-\|	Basic_py [~Basic@warden.real-time.com] has joined #xen
22:05	\|-\|	segher [~segher@dslb-084-056-144-093.pools.arcor-ip.net] has quit [Ping timeout: 480 seconds]
22:07	\|-\|	segher [~segher@dslb-084-056-187-190.pools.arcor-ip.net] has joined #xen
22:53	\|-\|	agriffis changed nick to agrif_away
22:58	\|-\|	VS_ChanLog [~stats@ns.theshore.net] has left #xen [Rotating Logs]
22:58	\|-\|	VS_ChanLog [~stats@ns.theshore.net] has joined #xen
23:06	\|-\|	sputhenp [~sputhenp@202.80.58.210] has joined #xen
23:10	\|-\|	Piet [hiddenserv@tor.noreply.org] has quit [Quit: Piet]
23:37	\|-\|	dhendrix [~dhendrix@c-24-7-121-175.hsd1.ca.comcast.net] has quit [Quit: Leaving]
23:45	\|-\|	dhendrix [~dhendrix@c-24-7-121-175.hsd1.ca.comcast.net] has joined #xen
---	Log	closed Tue Jan 23 00:00:29 2007