TheGrebs.com:IRC Logs:#xen:2006:01:31

---	Log	opened Tue Jan 31 00:00:28 2006
00:27	\|-\|	murb [~murbix@217.147.93.2] has joined #xen
00:29	\|-\|	jimix [~jimix@bh02i525f01.au.ibm.com] has joined #xen
00:34	\|-\|	jimix [~jimix@bh02i525f01.au.ibm.com] has quit [Quit: jimix]
01:02	\|-\|	murb [~murbix@217.147.93.2] has quit [Quit: leaving]
01:03	\|-\|	murb [~murbix@soapstone.yuri.org.uk] has joined #xen
01:07	\|-\|	dme [~dme@host-84-9-60-139.bulldogdsl.com] has quit [Remote host closed the connection]
01:20	\|-\|	sdog [~sdog@213-193-182-28.adsl.easynet.be] has joined #xen
01:22	\|-\|	dme [~dme@host-84-9-60-139.bulldogdsl.com] has joined #xen
01:23	\|-\|	Netsplit arion.oftc.net <-> europa.oftc.net quits: surriel, Hunger
01:25	\|-\|	Netsplit over, joins: Hunger, surriel
01:26	\|-\|	Tv [~tv@GMMDXXVII.dsl.saunalahti.fi] has quit [Quit: foo]
01:28	\|-\|	rusty [~rusty@bh02i525f01.au.ibm.com] has quit [Ping timeout: 480 seconds]
02:06	<mOdY>	hey all,, any idea why am i getting this message while there's a lot of unallocated ram memory !!!!!!? " Error: Error creating domain: The privileged domain did not ballon! "
02:40	\|-\|	tab_ [~tab@darwin.snarc.org] has joined #xen
02:40	\|-\|	tab [~tab@darwin.snarc.org] has quit [Read error: Connection reset by peer]
02:44	\|-\|	sdog [~sdog@213-193-182-28.adsl.easynet.be] has quit [Remote host closed the connection]
02:58	\|-\|	grifferz [~andy@82.69.129.107] has joined #xen
03:10	\|-\|	sdog [~sdog@213-193-182-28.adsl.easynet.be] has joined #xen
03:14	\|-\|	DV_ [~veillard@194.98.169.93] has joined #xen
03:24	\|-\|	gerrit [~gerrit@visit.suse.de] has joined #xen
03:28	\|-\|	Laugick [~Arnaud@82.138.86.21] has joined #xen
03:31	\|-\|	muli [~muli@87.69.40.180.cable.012.net.il] has quit [Quit: My damn controlling terminal disappeared!]
03:31	\|-\|	nicolas__ [~nicolas@130.158.161.128] has joined #xen
03:36	\|-\|	nicolas [~nicolas@130.158.161.128] has quit [Read error: Connection reset by peer]
03:36	\|-\|	nicolas [~nicolas@130.158.161.128] has joined #xen
03:42	\|-\|	nicolas__ [~nicolas@130.158.161.128] has quit [Ping timeout: 480 seconds]
03:51	\|-\|	athomas [~athomas@host86-136-81-69.range86-136.btcentralplus.com] has joined #xen
04:46	\|-\|	mjt [~mjt@nat.corpit.ru] has quit [Read error: Connection reset by peer]
04:46	\|-\|	Shoragan [~shoragan@d072.apm.etc.tu-bs.de] has joined #xen
05:07	\|-\|	wenchien [~wenchien@221-169-69-23.adsl.static.seed.net.tw] has quit [Quit: Terminated with extreme prejudice - dircproxy 1.0.5]
05:48	\|-\|	Tv [~tv@GMMDXXVII.dsl.saunalahti.fi] has joined #xen
06:06	\|-\|	DV_ [~veillard@194.98.169.93] has quit [Remote host closed the connection]
06:07	\|-\|	sdog [~sdog@213-193-182-28.adsl.easynet.be] has quit [Remote host closed the connection]
06:13	\|-\|	sdog [~sdog@213-193-182-28.adsl.easynet.be] has joined #xen
06:34	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has joined #xen
06:58	\|-\|	nags [~nags@125.16.129.16] has quit [Quit: Linux Desktop Testing Project - http://ldtp.freedesktop.org]
07:06	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has quit [Quit: mdday]
07:17	\|-\|	bernarde [~bernarde@tux01.ltc.ic.unicamp.br] has joined #xen
07:31	\|-\|	tschwinge [cpts2523@l2.cip.ei.uni-stuttgart.de] has left #xen [ERC Version 5.0.4 $Revision: 1.726.2.21 $ (IRC client for Emacs)]
07:34	\|-\|	_bernarde [~bernarde@tux01.ltc.ic.unicamp.br] has joined #xen
07:37	\|-\|	bernarde [~bernarde@tux01.ltc.ic.unicamp.br] has quit [Ping timeout: 480 seconds]
08:01	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has joined #xen
08:24	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has quit [Quit: mdday]
08:38	\|-\|	unriel changed nick to riel
08:40	\|-\|	johnlev [~johnlev@nwkea-socks-2.sun.com] has joined #xen
08:47	\|-\|	anball [~anball@bi01p1.nc.us.ibm.com] has joined #xen
08:49	\|-\|	dansmith [~dan@bi01p1.co.us.ibm.com] has joined #xen
09:10	\|-\|	Basic_py [~Basic@warden.real-time.com] has quit [Quit: Leaving]
09:17	\|-\|	rharper [~rharper@pixpat.austin.ibm.com] has joined #xen
09:17	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has joined #xen
09:32	\|-\|	athomas [~athomas@host86-136-81-69.range86-136.btcentralplus.com] has quit [Quit: Leaving]
09:33	\|-\|	athomas [~athomas@host86-136-81-69.range86-136.btcentralplus.com] has joined #xen
09:35	\|-\|	athomas [~athomas@host86-136-81-69.range86-136.btcentralplus.com] has quit [Quit: ]
09:39	\|-\|	anball [~anball@bi01p1.nc.us.ibm.com] has quit [Quit: Leaving]
09:40	\|-\|	athomas [~athomas@host86-136-81-69.range86-136.btcentralplus.com] has joined #xen
09:40	\|-\|	MarkW [~MarkW@maw48.kings.cam.ac.uk] has joined #xen
09:40	\|-\|	mode/#xen [+o MarkW] by ChanServ
09:41	<@MarkW>	aliguori: Dude, you there?
09:41	<aliguori>	MarkW, yessir
09:41	<aliguori>	MarkW, how's it going?
09:41	<@MarkW>	aliguori: You got any idea where I might find IBM zseries manuals? Are they public, or does IBM just charge loadsa money for them?
09:42	<@MarkW>	aliguori: Pretty good thanks. Just grokking through more s390 assembler ;-)
09:42	<aliguori>	MarkW, are you looking for an assembly manual?
09:43	<aliguori>	or are you looking for something more specific?
09:43	<@MarkW>	aliguori: Yes, an asm manual and a decent explanation of (the various kinds of) saved segments. Reading the source code is a big help, but it'd be nice to not be reverse engineering everything ;-)
09:45	<@MarkW>	aliguori: Actually, if you don't have any specific ideas I could contact Carsten Otte - he's worked on this stuff.
09:46	<aliguori>	MarkW, yeah, I was going to just send out off an email because I don't know anything off of the top of my head :-)
09:47	<@MarkW>	aliguori: OK. I'll send mail to Carsten and see if he has any ideas. I'll let you know how I get on ;-)
09:47	<aliguori>	MarkW, ok
09:53	\|-\|	tab_ changed nick to tab
09:55	\|-\|	rpg [~rpg@pixpat.austin.ibm.com] has joined #xen
10:03	\|-\|	Basic_py [~Basic@gatekeeper.real-time.com] has joined #xen
10:08	\|-\|	rpg [~rpg@pixpat.austin.ibm.com] has quit [Remote host closed the connection]
10:11	\|-\|	rpg [~rpg@pixpat.austin.ibm.com] has joined #xen
10:25	\|-\|	aliguori [~anthony@cpe-70-116-13-229.austin.res.rr.com] has quit [Remote host closed the connection]
10:27	\|-\|	anball [~anball@bi01p1.nc.us.ibm.com] has joined #xen
10:41	\|-\|	jerone [~jerone@pixpat.austin.ibm.com] has joined #xen
10:42	\|-\|	ns [~niv@bi01p1.co.us.ibm.com] has joined #xen
10:48	\|-\|	aliguori [~anthony@pixpat.austin.ibm.com] has joined #xen
11:01	\|-\|	mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has joined #xen
11:03	\|-\|	athomas [~athomas@host86-136-81-69.range86-136.btcentralplus.com] has quit [Remote host closed the connection]
11:04	\|-\|	gerrit [~gerrit@visit.suse.de] has quit [Quit: Client exiting]
11:08	\|-\|	stekloff [~stekloff@bi01p1.co.us.ibm.com] has joined #xen
11:09	\|-\|	athomas [~athomas@host86-136-81-69.range86-136.btcentralplus.com] has joined #xen
11:17	\|-\|	_bernarde [~bernarde@tux01.ltc.ic.unicamp.br] has quit [Ping timeout: 480 seconds]
11:19	\|-\|	jesse_ [~wenchien@221-169-69-23.adsl.static.seed.net.tw] has joined #xen
11:19	\|-\|	jesse_ changed nick to wenchien
11:21	\|-\|	_bernarde [~bernarde@tux01.ltc.ic.unicamp.br] has joined #xen
11:38	\|-\|	mdday_ [~mdday@bi01p1.nc.us.ibm.com] has joined #xen
11:39	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has quit [Ping timeout: 480 seconds]
11:40	\|-\|	yorkedork [~thom@nom13839cmd.nomadic.ncsu.edu] has joined #xen
11:41	\|-\|	athomas [~athomas@host86-136-81-69.range86-136.btcentralplus.com] has quit [Quit: Leaving]
11:43	\|-\|	yorkedork [~thom@nom13839cmd.nomadic.ncsu.edu] has quit [Quit: ]
11:46	\|-\|	pdx6 [~ballew@screen.sublinear.net] has quit [Ping timeout: 480 seconds]
12:05	\|-\|	VS_ChanLog_ [~stats@ns.theshore.net] has joined #xen
12:05	\|-\|	VS_ChanLog [~stats@ns.theshore.net] has quit [Remote host closed the connection]
12:05	\|-\|	VS_ChanLog_ changed nick to VS_ChanLog
12:13	\|-\|	Netsplit arion.oftc.net <-> quasar.oftc.net quits: VS_ChanLog
12:20	\|-\|	pdx6 [~ballew@screen.sublinear.net] has joined #xen
12:21	\|-\|	Netsplit over, joins: VS_ChanLog
12:25	\|-\|	Roey [~katz@h-69-3-4-130.mclnva23.covad.net] has joined #xen
12:28	\|-\|	johnlev [~johnlev@nwkea-socks-2.sun.com] has quit [Ping timeout: 480 seconds]
12:32	<johnny43>	guys, i have another xen3 mixing question for you..
12:32	<johnny43>	would a xen3_64bit dom0 support xen3_32bit domU's?
12:32	<tab>	johnny43: no
12:32	\|-\|	Netsplit arion.oftc.net <-> quasar.oftc.net quits: VS_ChanLog
12:32	<johnny43>	ah.. ok :( will have to stick to 32 bit pae then
12:33	<johnny43>	thanks
12:34	<tab>	you can have 32 bit support in domU on 64 bit xen only with HVM only
12:34	<tab>	-only
12:36	\|-\|	anball [~anball@bi01p1.nc.us.ibm.com] has quit [Quit: Leaving]
12:36	<johnny43>	HVM is supported only by some intel CPUs, right?
12:36	<tab>	and some AMD cpus
12:37	<johnny43>	hmm.. which are they? how can i check if i have it?
12:38	<tab>	you are looking for pacifica cpu or vt cpu
12:38	<tab>	only very very recent cpu have thoses
12:43	<johnny43>	ok, then i probably don't have it
12:44	<johnny43>	but - is there a performance penalty when running Xen with HVM?
12:46	\|-\|	sdog [~sdog@213-193-182-28.adsl.easynet.be] has left #xen []
12:49	\|-\|	mdday_ [~mdday@bi01p1.nc.us.ibm.com] has quit [Ping timeout: 480 seconds]
12:50	\|-\|	jerone_ [~jerone@pixpat.austin.ibm.com] has joined #xen
12:51	\|-\|	jerone_ [~jerone@pixpat.austin.ibm.com] has quit [Quit: ]
12:51	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has joined #xen
12:52	<aliguori>	johnny43, pacifica chips aren't shipping yet
12:52	<aliguori>	i don't think
12:54	\|-\|	bestorga [~bestorga@bi01p1.co.us.ibm.com] has joined #xen
13:09	\|-\|	muli [~muli@87.69.40.180.cable.012.net.il] has joined #xen
13:52	\|-\|	_bernarde [~bernarde@tux01.ltc.ic.unicamp.br] has quit [Ping timeout: 480 seconds]
13:59	\|-\|	dansmith [~dan@bi01p1.co.us.ibm.com] has quit [Quit: Leaving]
14:03	\|-\|	VS_ChanLog [~stats@ns.theshore.net] has joined #xen
14:08	\|-\|	Netsplit arion.oftc.net <-> quasar.oftc.net quits: VS_ChanLog
14:09	<Shaun>	aliguori: you around.
14:11	\|-\|	_bernarde [~bernarde@tux01.ltc.ic.unicamp.br] has joined #xen
14:14	\|-\|	Netsplit over, joins: VS_ChanLog
14:17	<Shaun>	anybody know why i'm seeing this error... http://pastebin.com/532658
14:17	<Shaun>	here's what i did...
14:17	<Shaun>	hg clone http://tx.downloads.xensource.com/xen-3.0-testing.hg
14:17	<Shaun>	cd xen-3.0-testing.hg
14:17	<Shaun>	make -j4 dist XEN_TARGET_X86_PAE=y
14:25	\|-\|	yorkedork [~thom@cpe-071-065-223-102.nc.res.rr.com] has joined #xen
14:31	\|-\|	aliguori [~anthony@pixpat.austin.ibm.com] has quit [Quit: Leaving]
14:35	\|-\|	yorkedork [~thom@cpe-071-065-223-102.nc.res.rr.com] has quit [Quit: Leaving]
14:36	<sdague>	Shaun: I don't think parallel builds work at the moment
14:37	<sdague>	try building without the -j4
14:45	\|-\|	_bernarde [~bernarde@tux01.ltc.ic.unicamp.br] has quit [Remote host closed the connection]
14:46	<Shaun>	ok
14:46	<Shaun>	same error but i'll make clean first...
14:55	\|-\|	yorkedork [~thom@nom13839cmd.nomadic.ncsu.edu] has joined #xen
14:55	\|-\|	yorkedork [~thom@nom13839cmd.nomadic.ncsu.edu] has quit [Quit: ]
14:59	\|-\|	aliguori [~anthony@pixpat.austin.ibm.com] has joined #xen
15:01	\|-\|	soffi [~soffi@proxy.du.vdsl.is] has joined #xen
15:01	<aliguori>	rharper, yeah, so it's just xen that doesn't work with the new memory
15:01	<aliguori>	how strange
15:01	\|-\|	Roey [~katz@h-69-3-4-130.mclnva23.covad.net] has left #xen [Leaving]
15:03	<rharper>	aliguori: are all of the dimms the same?
15:03	<rharper>	shouldn't matter
15:04	<aliguori>	rharper, i don't think so
15:04	<aliguori>	rharper, x just blew up under normal linux
15:04	<rharper>	wow
15:04	<aliguori>	so i think it's a deeper issue
15:04	<rharper>	yeah
15:04	<rharper>	hardware issue
15:05	<aliguori>	yeah
15:05	<rharper>	nasty
15:05	<rharper>	send it back =)
15:05	<aliguori>	:-)
15:07	[~]	aliguori has no luck with memory
15:08	<rharper>	haha, so true
15:08	<rharper>	how much memory have you hosed up now? 4G
15:10	<aliguori>	rharper, something like that
15:10	<aliguori>	at least this machine isn't overheating
15:11	<rharper>	hehe
15:11	<rharper>	so far
15:13	\|-\|	mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has quit [Quit: Client exiting]
15:14	<Shaun>	sdague: same compile error
15:30	\|-\|	stekloff [~stekloff@bi01p1.co.us.ibm.com] has quit [Quit: Leaving]
15:30	\|-\|	dansmith [~dan@c-24-21-32-166.hsd1.or.comcast.net] has joined #xen
15:36	\|-\|	jimix [~jimix@bh02i525f01.au.ibm.com] has joined #xen
15:37	<Cyis>	so how is the 64bit support these days? Once I get the last delivery on Wed I should have a new 64bit AMD system online
15:38	<riel>	if you're lucky it compiles
15:38	<riel>	that's about how good 64 bit support seems to be ;(
15:39	<murb>	so no betting on it booting?
15:39	<riel>	not unless you really like betting
15:40	<Cyis>	well I know the 32-bit demo CD boots okay... just have a bad power supply so waiting on the new one
15:42	\|-\|	anball [~anball@bi01p1.nc.us.ibm.com] has joined #xen
15:45	<Cyis>	which source is better to work with the xen-3.0-testing.hg or xen-unstable.hg
15:47	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has quit [Ping timeout: 480 seconds]
15:48	<anball>	cyis: what do you want to do? work on new features? try out latest [well-tested] xen?
15:48	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has joined #xen
15:49	<Cyis>	distro packaging that's closer to bleeding edge but reasonably stable...
15:49	<Cyis>	realized I can't use the changeset versions between them for comparison
15:51	<anball>	so you want a fixed version to test with that's reasonably stable?
15:51	<Cyis>	reasonably stable
15:52	<anball>	try xen-3.0-testing.hg and watch for 3.0.1 release is probably your best bet
15:53	<Cyis>	yeah I've been looking for 3.0.1 to be released as I was lead to believe that it would have the 2.6.15 kernel support patches
15:55	\|-\|	riel changed nick to unriel
15:55	<anball>	i think that's an important goal of 3.0.1. watch openSuSE and/or sles 10 betas if you like/intend to use SuSE-like distros
15:57	<Cyis>	nope... Debian
15:58	\|-\|	johnlev [~johnlev@nwkea-socks-2.sun.com] has joined #xen
16:00	<anball>	cyis: cool. i'll bet lots of people have been doing debian-style packaging of xen. mailing lists and wiki prob have info on that. i myself would like to use xen on ubuntu, but need to get a spare machine.
16:01	<Cyis>	I avoid ubuntu... being a Debian Developer and all
16:01	<aliguori>	Shaun, howdy
16:01	<Cyis>	hey aliguori
16:02	<aliguori>	Cyis, howdy
16:02	<aliguori>	Cyis, 2.6.16rc1 i believe is what's in -unstable right now
16:02	<aliguori>	i may be off on the rc version
16:02	<Cyis>	I just did an hg 'pull' and 'update' and still showing 2.6.12
16:03	<rharper>	aliguori: yeah, I was mistaken this morning, the make the sparse tree a subarch, but it is still 2.6.12
16:04	<Shaun>	aliguori: hi
16:04	<aliguori>	rharper, ah, okay
16:04	<aliguori>	Cyis, well, it was supposed to happen before 3.0.1 was tagged
16:04	<rharper>	yeah, I didn't look close enough, but rpg confirmed it with a build
16:04	<aliguori>	i'm a bit confused myself.. i expected 3.0.1 before the hvm merge
16:06	<Cyis>	would be nice to have a newer kernel before hardware stuff that may or may not be as readially available as the newer kernel :)
16:06	<Cyis>	but what do I know :D
16:07	<Shaun>	oh a clean server thats never had xen installed on it how are most of you guys doing the installs, the docs on the website show one way, the readme shows another, i'm just wondering if i'm having these build problems because i'm doing somthing wrong
16:07	\|-\|	mdday_ [~mdday@bi01p1.nc.us.ibm.com] has joined #xen
16:08	<Cyis>	I just do a bare bones base-system install then add the xen packages
16:08	<Shaun>	xen packages?
16:08	<Shaun>	what the rpms from xensource?
16:08	<Cyis>	but I've not been happy with the xen-3 packages available for Debian so far
16:09	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has quit [Ping timeout: 480 seconds]
16:10	<Shaun>	when building xen0 do i have to add XEN_TARGET_X86_PAE=y or can i just change the config from 4GB to 64GB
16:12	<rharper>	if you want pae, you need to turn it on in the hypervisor and dom0, so make sure you add XEN_TARGET_X86_PAE=y in addition to changing dom0 kernel
16:13	<Shaun>	where should i specify it? when doing a make dist?
16:13	<rharper>	make pae=y dist
16:13	<rharper>	yeah
16:13	<Shaun>	ok, just to make sure i'm going in the right direction here...
16:13	<rharper>	yeah
16:14	<rharper>	been a while since I tested pae, but I believe thats whats needed
16:14	<Shaun>	on a clean install, first thing besides making sure you have gcc zlib etc... is to make dist XEN_TARGET_X86_PAE=y?
16:14	<rharper>	yeah
16:14	<Shaun>	XEN_TARGET_X86_PAE=y is what the readme says to append but it doesnt say to what...
16:15	<Shaun>	rharper: ok, once thats done, i should run the ./install.sh script?
16:15	<rharper>	yeah
16:17	<Shaun>	ok, i just did that, then i cd'd to linux-2.6.12-xen0
16:17	<Shaun>	ran a make ARCH=xen menuconfig
16:17	<Shaun>	changed a few things
16:17	<Shaun>	cd ..
16:17	<Shaun>	make
16:17	<Shaun>	and now i get this error again....
16:18	<Shaun>	http://pastebin.com/532882
16:19	<rharper>	the latest tree probably doesnt need the ARCH=xen since xen is now a subarch of i386
16:19	<rharper>	oh, but you are on testing, nm that
16:19	<Shaun>	should i be using somthing else?
16:20	<rharper>	no
16:20	<Shaun>	i dont see a 3.x released/stable anywhere
16:20	<Shaun>	only see unstable and testing.
16:20	<rharper>	yeah, I've not built the testing tree before, only use unstable. but looks like there is something going on in the testing tree.
16:21	\|-\|	mdday_ [~mdday@bi01p1.nc.us.ibm.com] has quit [Ping timeout: 480 seconds]
16:21	<Shaun>	is unstable more stable that testing? :)
16:21	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has joined #xen
16:21	<Shaun>	i though they released 3.0 as "released/stable"
16:21	<Shaun>	could have sworn i read/heard that
16:22	<rharper>	Shaun: doubtful, but the periodically pull patches from unstable that have been tested into testing, maybe they missed one
16:23	<Shaun>	if i was going to try to use xen-3.0 in a production ENV with PAE what would you recommend...
16:23	<Shaun>	testing or unstable, unless theirs another 3.0 tree i'm not seeing :)
16:23	<Cyis>	it'd be nice to see xen's sub-arch code directly in the main stream kernel source eventually not requiring patches
16:24	<rharper>	I wouldnt. I don't know that pae, whether testing or unstable has had enough pae testing to matter
16:24	<Shaun>	Cyis: UML is mainline i'm sure xen will be one day...
16:24	<Cyis>	Shaun: we can hope. prolly after things stabilize more
16:25	<Cyis>	when xen tools can be released separetly from kernel patches
16:25	\|-\|	_David_ [~david@202.148.226.15] has joined #xen
16:27	<Shaun>	rharper: i suppose they could have forgot somthing in testing but you'd think somebody would have said somthing by now, i saw this build error last week
16:27	<Shaun>	i just got around it some how
16:27	<Shaun>	i'm wondering if the problem has to do with PAE...
16:27	<rharper>	Shaun: you would think. Prolly worth an email to the list
16:27	<rharper>	Shaun: very possible
16:29	<Cyis>	Shaun: that paste was from 3.0-testing?
16:29	<Shaun>	yes
16:29	<Cyis>	running it here... just did an update/pull
16:30	<aliguori>	Shaun, try cloning the testing tree. perhaps your local copy has some badness in it
16:30	<Cyis>	that's what I'm thinking as this build is going to town without so much as a warning
16:31	<Cyis>	right now it's grabbing kernel source so done compiling the tools
16:31	<Shaun>	cd i've rm -rf'd it a few times now
16:32	<Cyis>	what system are you building it on?
16:32	<Shaun>	make dist does fine, i always run into the problem on a make install
16:32	<Shaun>	and right now i'm running into it with just a make
16:32	<Shaun>	CentOS 4
16:32	<Cyis>	could be distro issue... Debian having no problems here
16:32	<Shaun>	Cyis: thats the thing, i've had this working
16:33	<Shaun>	it just worked the other day
16:33	<Shaun>	but the day before that i had the problem
16:33	<Shaun>	i got around it somehow...
16:34	<Shaun>	let me try going through this again, step by step with out PAE and see what happens..
16:35	<Shaun>	quick question.... make dist ; ./install.sh
16:35	<Shaun>	those installed xen0 and xenU in my /boot
16:35	<Shaun>	did it build those, or are those pre-built
16:35	<Shaun>	because if it built those how the hell did it do it is my q, because i cant :)
16:35	<Cyis>	is the timestamp recent?
16:36	<rharper>	when I run make dist, it builds the hypervisor, and two kernels, tools and stuffs them all in dist/ dir in the build tree
16:36	<Shaun>	ya, timestamps show today...
16:36	\|-\|	aliguori [~anthony@pixpat.austin.ibm.com] has quit [Remote host closed the connection]
16:37	<Cyis>	Shaun2: could try taking it in steps... ie (run 'make xen && make tools && make kernels') and see where it fails
16:37	<Shaun>	just ran make xen XEN_TARGET_X86_PAE=y and it failed...
16:38	<Cyis>	my guess than the PAE code is borked
16:38	<rharper>	good guess
16:38	<Shaun>	hmm
16:38	<Shaun>	just ran make clean
16:38	<Shaun>	then make xen
16:38	<Shaun>	and it's building away...
16:38	<Shaun>	err...
16:39	<Cyis>	I could be wrong... but it would seem default is without PAE and PAE is borked and you're trying to build it...
16:39	<Shaun>	ok i have to build hypervision with PAE support to support more than 4GB of mem right?
16:39	<rharper>	yes
16:39	<Shaun>	xen0 isnt hypervision i'm assuming?
16:39	<Cyis>	nope
16:39	<rharper>	xen0 should be the dom0 kernel
16:40	<Shaun>	right.
16:40	<Cyis>	the xen-3.0.1.gz in /boot should be the hypervisor
16:40	<Cyis>	the xen0 is the dom0 kernel, the xenU is the domU kernel
16:43	<Shaun>	ok
16:43	<Shaun>	so how do i build hypervision only
16:43	<Shaun>	is make xen doing that?
16:43	<Cyis>	'make xen' should build the hypervisor... 'make tools' should build the xen tools... it's all in 'make help'
16:43	<Shaun>	oh ok
16:44	<Shaun>	ok, well unless i plan on having dom0's mem set to 4+GB of ram, there is no reason to build dom0 with PAE support right?
16:44	<rharper>	thats right
16:44	<Shaun>	ok..
16:44	<rharper>	unless any domain needs >4G you don't need pae
16:45	<Shaun>	ya, no domain is doing to use that much, probably 512 max..
16:45	<Cyis>	rharper: now would he still need the PAE then for the hypervisor? I can follow the logic regarding the dom0/domU kernels
16:45	<rharper>	Cyis: I don't think so, but I'm not 100% sure
16:46	<Cyis>	nor am I :)
16:46	<rharper>	I'm pretty sure that xen can see large amounts of memory without adding in the extra page table levels
16:46	<Cyis>	hmm.. let me see what this turns up
16:46	<Shaun>	i'm almost positive it needs it...
16:47	<Shaun>	because i know of other providers who only give guests with less than 4GB of ram and they where holding off for PAE.
16:47	<Cyis>	I can't find anything under the xen/ sub-directory of the source that uses the XEN_TARGET_X86_PAE define
16:47	<rharper>	yeah, I think you would need pae for xen to see all of the memory in the system
16:47	<rharper>	Cyis: it is CONFIG_PAE
16:47	<rharper>	XEN_TARGET_X86_PAE is turned into CONFIG_PAE, iirc
16:47	<Shaun>	right, but only hypervisor would need it right?
16:47	<Cyis>	hmm... maybe that's not the right way to search...
16:48	<rharper>	Shaun: yes as long as you don't care that dom0/domU can't have more than 4G of memory
16:48	<Cyis>	well the top level Makefile exports 'pae=y' if XEN_TARGET_X86_PAE=y
16:48	<rharper>	of course the rub is that make xen with pae is broken
16:49	<rharper>	check out xen/include/asm-x86/config.h
16:49	<rharper>	it is CONFIG_PAE_X86
16:50	\|-\|	alexandre [~Alexandre@200.138.33.182] has joined #xen
16:50	<Cyis>	also checkout the 'config-update-pae' target in buildconfigs/Rules.mk
16:51	<rharper>	auto switching for the linux kernel configs
16:52	<Shaun>	ok...
16:52	<Shaun>	well obviously make dist build hypervisor
16:52	<Shaun>	and i passed the PAE option
16:53	<Shaun>	so it must have worked, you'd think
16:53	<Shaun>	anyway to verify PAE support?
16:54	<rharper>	the xen version changes from 3.0.0, to 3.0.0p
16:54	\|-\|	AlexMBas [~Alexandre@200.138.54.233] has quit [Ping timeout: 480 seconds]
16:54	<Shaun>	anyway to see that without booting it?
16:55	<Shaun>	the file is named xen-3.0.1.gz
16:55	<rharper>	maybe zgrep -i pae /boot/xen.gz
16:55	<rharper>	or run strings on it and grep for pae, not sure
16:55	<rharper>	it isn't easy
16:55	<rharper>	which stinks
16:55	\|-\|	_David_ [~david@202.148.226.15] has quit [Quit: Kopete 0.9.2 : http://kopete.kde.org]
16:56	<Shaun>	ya, would be nice if it just named the file with the p extention :)
16:56	<rharper>	heh
16:56	\|-\|	aliguori [~anthony@pixpat.austin.ibm.com] has joined #xen
16:56	<rharper>	they take patches =)
16:57	<Shaun>	ya, i already have one to send
16:57	<rharper>	heh
16:57	<Cyis>	hmm... If I ran 'zcat xen.gz \|strings \|grep -i pae' against the build of 3.0.1 from 3.0-testing that I have here... I get three items back
16:57	<rharper>	Cyis: I have those too, but I don't build with pae support
16:57	<Cyis>	first says "PAE=yes", next is "PAE disabled." and the last is "PAE mode mismatch between Xen and DOM0 (xen=%s, dom0=%s)"
16:58	<Cyis>	yeah that was just typing "make"
16:58	<Shaun>	[root@localhost xen-3.0-testing.hg][root@localhost xen-3.0-testing.hg]# zcat /boot/xen.gz \|strings \|grep -i pae
16:58	<Shaun>	PAE mode mismatch between Xen and DOM0 (xen=%s, dom0=%s)
16:58	<Shaun>	FIXME: PAE code needed here: %s:%d (%s)
16:58	<Shaun>	PAE=yes
16:58	<Shaun>	PAE enabled, limit: %d GB
16:58	<rharper>	my xen says: (XEN) PAE disabled.
16:58	<rharper>	when I boot that image
16:58	<Cyis>	seems that the "PAE disabled." is the indicator
16:59	<rharper>	so yeah, no easy way to tell
16:59	<Cyis>	vs. "PAE enabled, limit: %d GB"
16:59	<Shaun>	what does this line output for you guys using 3.0-testing? `zcat /boot/xen.gz \|strings \|grep -i pae`
16:59	<Shaun>	same as mine or no?
17:00	<Cyis>	Shaun: what I stated was from 3.0-testing.hg
17:00	<rharper>	Shaun: mine was from unstable, I don't have that FIXME line
17:00	<Cyis>	but I was just typing 'make' without trying to include PAE support
17:00	<Shaun>	ok, so then by the looks of it my hypervisor has PAE enabled?
17:01	<rharper>	only one way to tell =)
17:01	<rharper>	boot it
17:01	<rharper>	you have serial console on the box? you can capture the hypervisor boot info
17:01	<Cyis>	well other than the one line changing from "disabled" to "enabled" and the addition of the "FIXME" line it's the same was what I got
17:01	<Cyis>	booting it up would be the only sure way to tell
17:01	<Shaun>	let me try somthin real quick
17:02	<Shaun>	rharper: no serial on this box, i have a ip kvm...
17:02	<Shaun>	ok, i just built xen without PAE and now i see this...
17:02	<Shaun>	PAE mode mismatch between Xen and DOM0 (xen=%s, dom0=%s)
17:02	<Shaun>	PAE=yes
17:02	<Shaun>	PAE disabled.
17:02	<Cyis>	which is what I get
17:03	<rharper>	seems like the strings can tell
17:03	<Cyis>	I'm trying to build with PAE after doing a 'make distclean
17:03	<Shaun>	interesting...
17:03	<Shaun>	i just did make xen pae=y
17:03	<Shaun>	and it compiled fine...
17:04	<Shaun>	strings shows PAE enabled
17:04	<Cyis>	doing a 'make XEN_TARGET_X86_PAE=y' myself
17:04	<Shaun>	wtf....
17:05	<Shaun>	oh whoops
17:05	<Cyis>	and when I do that it generates the xen.gz with "PAE enabled, limit: %d GB"
17:05	<Shaun>	no actually wtf, now make xen XEN_TARGET_X86_PAE=y compiles file....
17:05	<Shaun>	fine..
17:06	<Cyis>	did you do a 'clean' or 'distclean' between builds? could have bad object files laying around
17:06	<Shaun>	wait
17:06	<Shaun>	the problem is with make xen-install
17:07	<Shaun>	testing without pae right now..
17:08	<Shaun>	make xen;make install-xen works fine...
17:08	<Shaun>	make xen pae=y works...
17:09	<Shaun>	make install-xen pae=y works
17:09	<Cyis>	I don't know if doing 'make pae=y' is wise... README says to do 'make XEN_TARGET_X86_PAE=y'
17:09	<Shaun>	now i'm all confused..
17:10	<Shaun>	wait a sec...
17:10	<Shaun>	dont the xen0/U kernels need PAE support to be able to access/use the section of memory over 4GB?
17:10	<Shaun>	sorry my mind if flying with thoughts
17:11	<Cyis>	would the dom0 or dumU even know the system had more RAM than the config told it ?
17:12	<rharper>	Shaun: xen needs pae to map all physical memory, it provides an abstraction the xen0/U, they think their memory starts at 0 anyhow. they have to have pae support if you give them more than 4G of ram
17:12	<rharper>	you can have xen with pae, have xen see all 8G of ram, but never give any guest more than 4G and not worry about CONFIG_HIGHMEM64 in xen0/xenU kernels
17:13	<Shaun>	ok so it doesnt matter if they get thrown in the 6-8gb chunk as long as they dont has more than 4GB assigned to them
17:13	<rharper>	Shaun: I belive so
17:13	<Shaun>	ok, testing shows this....
17:13	<Shaun>	"make xen pae=y;make install-xen pae=y" builds fine, no errors....
17:14	<Shaun>	"make xen pae=y;make install-xen" fails.
17:14	<Shaun>	"make xen pae=y;make install-xen; make install-xen pae=y" fails
17:14	<Cyis>	try 'make xen pae=y;make install-xen pae=y"
17:15	<Shaun>	thats the first one i pasted above...
17:15	<rharper>	I guess they did tie the two together then, there is that message about not booting a dom0 pae on non-pae xen
17:15	<Shaun>	thats worked fine
17:15	<Cyis>	well obviously then if you do 'make xen pae=y' then you need to use 'make install-xen pae=y' rather than 'make install-xen
17:16	<Shaun>	"make xen XEN_TARGET_X86_PAE=y;make install-xen XEN_TARGET_X86_PAE=y" works fine
17:16	<rharper>	sounds like what you want
17:16	<Shaun>	ok so you just have to be consistant then...
17:16	<rharper>	xen/xen0/xenU with pae support
17:16	<rharper>	yeah
17:16	<Shaun>	rharper: wait, so i need to build everything now with pae support?
17:16	[~]	Shaun takes out 6ft of rope.
17:17	\|-\|	rusty [~rusty@bh02i525f01.au.ibm.com] has joined #xen
17:17	<rharper>	there is this line: PAE mode mismatch between Xen and DOM0 (xen=%s, dom0=%s)
17:18	<rharper>	which make me think they need to be in sync
17:18	<Shaun>	i see
17:18	<Shaun>	suppose i could post asking this question...
17:18	<Shaun>	or mayber aliguori nows...
17:19	<rharper>	maybe
17:19	<aliguori>	what question is this?
17:19	<Shaun>	boy my typing/spelling really sucks today.
17:19	<Shaun>	aliguori: in regards to PAE support...
17:19	<aliguori>	what's the question?
17:19	<rharper>	it is all or nothing, right
17:19	<Shaun>	aliguori: if the guest/dom0 are not going to be assigned more than 4GB do they need to be built with pae support, or can hypervisor only be built with it?
17:19	<rharper>	xen/dom0/domU all have to have pae support to work properly
17:19	\|-\|	soffi [~soffi@proxy.du.vdsl.is] has quit [Quit: Leaving]
17:20	<aliguori>	yes
17:20	<aliguori>	rharper is correct
17:20	<Shaun>	ok.
17:20	<Shaun>	lovely!
17:20	<aliguori>	Shaun, if the hypervisor has PAE enabled, it changes the address size to 8 bytes
17:20	<aliguori>	which means the guest has to be aware of that
17:20	<aliguori>	along with using a PAE page table because it may have higher memory
17:20	<aliguori>	even though it has less than 4gb of memory total
17:21	<aliguori>	it could be all of the top memory...
17:21	<Shaun>	right.
17:21	<rharper>	Shaun: sorry for the mixup
17:21	<Shaun>	thats what i was thinking with my question a above
17:21	<Shaun>	aliguori: thanks for the confirm...
17:21	<Shaun>	ok now lets see if i can get these xen0/U's to build with pae support :)
17:22	[~]	rharper goes home before Shaun uses 6ft of rope on him
17:22	<Cyis>	Shaun: I'm doing a PAE enabled build now
17:22	\|-\|	rharper [~rharper@pixpat.austin.ibm.com] has quit [Quit: Leaving]
17:23	<Cyis>	aliguori: I'll have my 64bit AMD system together this weekend... expecting the new power supply and cooling fan tomorrow and then to do the base install
17:23	<aliguori>	sweet
17:24	<Shaun>	Cyis: i havnt done vps's with 64bit yet.
17:24	<Shaun>	all my UML machines are just dual xeons, 8GB ram, raid10
17:25	<Shaun>	aliguori: ok when guesting the xen0/U do i need to apply XEN_TARGET_X86_PAE=y or is doing a make menuconfig ARCH=xen and setting the highmem limit to 64 good enough?
17:25	<Shaun>	s/guesting/building/g
17:26	<Cyis>	aliguori: figured I need'd to upgrade the AMD K6 450Mhz board with something...
17:27	<Cyis>	problem was the power supply wasn't an ATX12V so I had to get a new one and was cheaper to order online... also needed to get a new cooling fan as the OEM one was too high for the 2U case
17:27	\|-\|	aliguori [~anthony@pixpat.austin.ibm.com] has quit [Quit: Leaving]
17:28	\|-\|	jerone [~jerone@pixpat.austin.ibm.com] has quit [Quit: Leaving]
17:29	\|-\|	Basic_py [~Basic@gatekeeper.real-time.com] has quit [Quit: Leaving]
17:31	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has quit [Ping timeout: 480 seconds]
17:32	<Shaun>	lol, guess it's checkout time at ibm in austin :)
17:37	\|-\|	rpg [~rpg@pixpat.austin.ibm.com] has quit [Remote host closed the connection]
17:40	<Cyis>	one reason why I IRC from my home computer... remote connection is the only way to go :)
17:42	<Shaun>	Cyis: do i have to do a make dist? or can i just do everything manually, make xen;make install-xen;make .... etc?
17:49	<Shaun>	hmm doesnt look like i need too so far..
17:49	<Cyis>	if I'm not mistaken... you can do a
17:49	<Cyis>	'make install' and it should build and install all from one command
18:04	\|-\|	aliguori [~anthony@cpe-70-116-13-229.austin.res.rr.com] has joined #xen
18:06	<Shaun>	aliguori: you think in the future there might be a way to view io op/s usage per guest and possibly set a per sec limit?
18:09	<aliguori>	Shaun, that information is maintained by the dom0 kernel
18:09	<aliguori>	you should be able to get it as you normally would in linux (i don't know what you'd do there, but whatever you do, it should be the same)
18:10	<aliguori>	for vifs, correlation.. correlation for shared vbds (r/o mounted) would be difficult of course
18:10	<aliguori>	Shaun, if you figure out how to get that info from the dom0 kernel, i'd help you do the correlation as it would be a very nice feature to hvae in xen
18:12	<Shaun>	i'm running lvm backed vbd's... i'll have to dig into it more
18:12	<Shaun>	thanks
18:12	<Shaun>	caker has a patch i used on UML...
18:13	<Shaun>	worked great..
18:13	<Shaun>	was hoping for something simular for xen... http://www.theshore.net/~caker/patches/token-limiter-v4-testing.patch
18:24	\|-\|	bestorga [~bestorga@bi01p1.co.us.ibm.com] has quit [Quit: Leaving]
18:31	<Shaun>	where does xen get/build it's config from? i looked at the config from linux-2.6-xen-sparse/arch/xen/configs/xen_defconfig_x86_32 and it doesnt even come close to matching linux-2.6.12-xen0/.config
18:52	\|-\|	stephand [~syon@G199b.g.pppool.de] has joined #xen
18:52	\|-\|	stephand [~syon@G199b.g.pppool.de] has left #xen []
18:56	<Shaun>	n/m i figured out what was happening... duh!
18:57	\|-\|	anball [~anball@bi01p1.nc.us.ibm.com] has quit [Remote host closed the connection]
19:08	\|-\|	craSH [~crash@thoughtcriminal.us] has left #xen []
19:11	\|-\|	ns [~niv@bi01p1.co.us.ibm.com] has quit [Quit: Leaving]
19:14	\|-\|	aliguori [~anthony@cpe-70-116-13-229.austin.res.rr.com] has quit [Ping timeout: 480 seconds]
19:15	\|-\|	dansmith [~dan@c-24-21-32-166.hsd1.or.comcast.net] has quit [Quit: Leaving]
19:16	\|-\|	ns [~niv@bi01p1.co.us.ibm.com] has joined #xen
19:27	\|-\|	ns [~niv@bi01p1.co.us.ibm.com] has quit [Ping timeout: 480 seconds]
19:30	\|-\|	Shoragan [~shoragan@d072.apm.etc.tu-bs.de] has quit [Quit: Leaving]
20:07	\|-\|	monrad_ changed nick to monrad
20:13	\|-\|	aliguori [~anthony@cpe-70-116-13-229.austin.res.rr.com] has joined #xen
20:54	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has joined #xen
21:28	\|-\|	Basic_py [~Basic@warden.real-time.com] has joined #xen
21:35	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has quit [Quit: mdday]
21:59	\|-\|	yorkedork [~thom@cpe-071-065-223-102.nc.res.rr.com] has joined #xen
21:59	\|-\|	yorkedork [~thom@cpe-071-065-223-102.nc.res.rr.com] has quit [Quit: ]
22:00	\|-\|	hollisb [~hollisb@203-97-61-238.dsl.clear.net.nz] has joined #xen
22:03	<tonyb>	Howdy hollisb
22:05	<hollisb>	hey tonyb :)
22:06	<tonyb>	enjoying NZ now you're away from the conf?
22:07	<hollisb>	yup. still kept pretty busy actually...
22:07	<hollisb>	I went on the Speight's Brewery tour this afternoon. they have good beer. :)
22:08	<tonyb>	Yes .. Yes they do :) The question is, are you going to do the emmerson tour tomorrow? ;P
22:08	<hollisb>	is that another brewery? haven't run across that one
22:09	<tonyb>	Yup, I'll find you an URL ...
22:10	<hollisb>	well, I'm heading out early tomorrow morning, so I'll miss it I guess
22:10	<tonyb>	Oh well next time maybe
22:10	<hollisb>	yeah. I've actually been reasonably busy while here. I expected to have a little more free time
22:11	<hollisb>	but that's probably a good thing
22:13	<tonyb>	as long as it's busy seeing the place not busy working
22:13	<tonyb>	then its a good thing
22:13	<hollisb>	yeah, haven't been working :)
22:14	<tonyb>	:)
22:28	\|-\|	david_ [~david@192.55.98.42] has joined #xen
22:39	\|-\|	nags [~nags@125.16.129.16] has joined #xen
22:42	\|-\|	david_ [~david@192.55.98.42] has quit [Remote host closed the connection]
22:59	\|-\|	VS_ChanLog [~stats@ns.theshore.net] has left #xen [Rotating Logs]
22:59	\|-\|	VS_ChanLog [~stats@ns.theshore.net] has joined #xen
23:40	\|-\|	yorkedork [~thom@cpe-071-065-223-102.nc.res.rr.com] has joined #xen
23:40	\|-\|	yorkedork [~thom@cpe-071-065-223-102.nc.res.rr.com] has quit [Quit: ]
23:46	\|-\|	ricardoz [~ricardoz@ppp-70-246-92-111.dsl.austtx.swbell.net] has joined #xen
23:50	\|-\|	ricardoz [~ricardoz@ppp-70-246-92-111.dsl.austtx.swbell.net] has left #xen []
23:50	\|-\|	Shaun2222 [~Shaun@ip68-5-63-223.oc.oc.cox.net] has joined #xen
23:57	\|-\|	hollisb [~hollisb@203-97-61-238.dsl.clear.net.nz] has quit [Quit: leaving]
---	Log	closed Wed Feb 01 00:00:11 2006