TheGrebs.com:IRC Logs:#xen:2006:02:28

---	Log	opened Tue Feb 28 00:00:43 2006
00:09	\|-\|	Netsplit jupiter.oftc.net <-> europa.oftc.net quits: surriel, Hunger
00:15	\|-\|	Netsplit over, joins: Hunger, surriel
00:26	\|-\|	ns [~nivedita@c-67-171-181-157.hsd1.or.comcast.net] has quit [Ping timeout: 480 seconds]
00:26	\|-\|	zwane [~zwane@S0106001217d33fa6.vc.shawcable.net] has quit [Remote host closed the connection]
00:32	\|-\|	horms [~horms@vagw.valinux.co.jp] has quit [Quit: Leaving]
00:35	\|-\|	jerone [~jerone@adsl-71-145-138-37.dsl.austtx.sbcglobal.net] has quit [Quit: Leaving]
00:36	\|-\|	ns [~nivedita@c-67-171-181-157.hsd1.or.comcast.net] has joined #xen
00:40	\|-\|	rusty [~rusty@bh02i525f01.au.ibm.com] has quit [Ping timeout: 480 seconds]
00:41	\|-\|	JViz [Anomaly@adsl-065-013-131-023.sip.int.bellsouth.net] has quit [Ping timeout: 480 seconds]
01:08	\|-\|	ns [~nivedita@c-67-171-181-157.hsd1.or.comcast.net] has quit [Quit: Leaving]
01:30	\|-\|	muli_ [~muli@87.69.40.180.cable.012.net.il] has quit [Remote host closed the connection]
02:02	\|-\|	rusty [~rusty@ppp61-206.lns1.cbr1.internode.on.net] has joined #xen
02:13	\|-\|	sdog [~sdog@62.58.98.210] has joined #xen
02:36	\|-\|	JViz [Anomaly@adsl-065-013-131-023.sip.int.bellsouth.net] has joined #xen
03:02	\|-\|	ygcheny [~ygcheny@gaia.lan2net.fr] has joined #xen
03:02	<ygcheny>	Hi !
03:04	\|-\|	horms [~horms@vagw.valinux.co.jp] has joined #xen
03:05	\|-\|	athomas [~athomas@host86-136-81-69.range86-136.btcentralplus.com] has joined #xen
03:13	<teferi>	out of curiosity, are there actually any other OSes besides Linux that actually work with Xen3?
03:15	<ygcheny>	windows and some unix
03:15	<teferi>	well, the netbsd xen port is still only 2.0.7
03:15	<teferi>	the freebsd one hasn't even been merged into -CURRENT yet
03:15	<teferi>	(and the last snapshot i tried didn't even boot to single-user mode)
03:20	<hensema>	are there any other oses beside linux nowadays? :-O
03:21	<ygcheny>	linux is the better OS to work with XEN now but there is some test with other OS
03:23	<ygcheny>	Net BSD ...
03:23	<teferi>	I just mentioned the netbsd port.
03:23	<teferi>	as I said, 3.0 only runs on 2.0.7, as does even the latest -CURRENT snapshot
03:24	<teferi>	(compiled mere hours ago)
03:50	\|-\|	harry_ [~harry@blueice1n1.uk.ibm.com] has joined #xen
04:13	\|-\|	cods [~cods@tuxee.net] has joined #xen
04:25	\|-\|	horms [~horms@vagw.valinux.co.jp] has quit [Quit: Leaving]
04:49	\|-\|	Shoragan [~shoragan@d072.apm.etc.tu-bs.de] has joined #xen
04:50	\|-\|	Shoragan [~shoragan@d072.apm.etc.tu-bs.de] has quit [Remote host closed the connection]
04:53	\|-\|	Shoragan [~shoragan@d072.apm.etc.tu-bs.de] has joined #xen
04:58	\|-\|	ivan [~ikelly@83-71-74-95.b-ras1.lmk.limerick.eircom.net] has joined #xen
05:08	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has joined #xen
05:18	\|-\|	horms [~horms@p2191-ipbf409marunouchi.tokyo.ocn.ne.jp] has joined #xen
05:25	\|-\|	dme [~dme@host-84-9-60-139.bulldogdsl.com] has quit [Remote host closed the connection]
05:31	\|-\|	dme [~dme@host-84-9-60-139.bulldogdsl.com] has joined #xen
05:33	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has quit [Quit: mdday]
05:55	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has joined #xen
05:57	<muli>	good morning mdday
05:57	<mdday>	muli: good afternoon
05:57	\|-\|	pvanhoof [~pvanhoof@d54C0FBBD.access.telenet.be] has joined #xen
06:08	\|-\|	Shoragan [~shoragan@d072.apm.etc.tu-bs.de] has quit [Read error: Connection reset by peer]
06:08	\|-\|	pvanhoof [~pvanhoof@d54C0FBBD.access.telenet.be] has quit [Read error: Connection reset by peer]
06:08	\|-\|	Shoragan [~shoragan@d072.apm.etc.tu-bs.de] has joined #xen
06:08	\|-\|	pvanhoof [~pvanhoof@d54C0FBBD.access.telenet.be] has joined #xen
06:15	\|-\|	rusty [~rusty@ppp61-206.lns1.cbr1.internode.on.net] has quit [Quit: Client exiting]
06:16	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has quit [Quit: mdday]
06:27	\|-\|	pvanhoof [~pvanhoof@d54C0FBBD.access.telenet.be] has quit [Read error: Connection reset by peer]
06:27	\|-\|	Shoragan [~shoragan@d072.apm.etc.tu-bs.de] has quit [Read error: Connection reset by peer]
06:27	\|-\|	Shoragan [~shoragan@d072.apm.etc.tu-bs.de] has joined #xen
06:27	\|-\|	pvanhoof [~pvanhoof@d54C0FBBD.access.telenet.be] has joined #xen
06:27	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has joined #xen
06:50	\|-\|	hikenboot [~hikenboot@c-24-218-84-234.hsd1.ma.comcast.net] has joined #xen
06:54	<hikenboot>	hello all---the build directions suggest make KERNELS=linux-2.6-xen world followed by make install ..it also suggests leaving off the KERNELS parameter if one wishes to build the domU and dom0 kernels...it then goes on to give directions for building the kernel if you want to do a custom config...my question is if I want to make world followed by making my own custom kernel (loading specific drivers into dom0 kernel as apposed
06:55	<hikenboot>	to the generic one) how would I do this?
06:57	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has quit [Quit: mdday]
06:57	<hikenboot>	make linux-2.6-xen-config CONFIGMODE=menuconfig <----if i followed make world by this I would get only the generic kernel not the dom0/domU kernels to build ...yes/no?
07:04	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has joined #xen
07:04	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has quit [Quit: ]
07:09	<ivan>	can i modify cpu_freq in shared_info/
07:29	\|-\|	jimix [~jimix@ip139.152.45.216.suscom.net] has joined #xen
07:30	\|-\|	jimix [~jimix@ip139.152.45.216.suscom.net] has quit [Quit: ]
07:46	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has joined #xen
07:53	\|-\|	mdday [~mdday@cpe-024-163-120-222.nc.res.rr.com] has quit [Quit: mdday]
08:17	\|-\|	horms [~horms@p2191-ipbf409marunouchi.tokyo.ocn.ne.jp] has quit [Quit: Leaving]
08:32	\|-\|	jimix [~jimix@yktgi01e0-s4.watson.ibm.com] has joined #xen
08:34	\|-\|	unriel changed nick to riel
08:36	<harry_>	is save restore on x86_64 supposed to work? i find that x86_32 works but x86_64 domu kernel crashes on restore.
08:52	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has joined #xen
08:55	\|-\|	muli_ [~muli@87.69.40.180.cable.012.net.il] has joined #xen
08:57	\|-\|	zwane [~zwane@S0106001217d33fa6.vc.shawcable.net] has joined #xen
08:58	<iamlost>	aliguori: whats a clustering filesystem?
09:05	\|-\|	dansmith [~dan@129.33.1.37] has joined #xen
09:07	<mancdaz>	if I start a system using "xm create -c <name>" so I can see the console messages as it boots up, how can I disconnet from that console in that session?
09:14	<ivan>	Ctrl-]
09:16	\|-\|	aliguori [~anthony@cpe-70-116-13-229.austin.res.rr.com] has quit [Quit: Ex-Chat]
09:29	\|-\|	anball [~anball@bi01p1.nc.us.ibm.com] has joined #xen
09:31	\|-\|	homebaum [~michael@pool-71-245-98-177.ptldor.fios.verizon.net] has quit [Quit: Client exiting]
09:32	\|-\|	homebaum [~michael@pool-71-245-98-177.ptldor.fios.verizon.net] has joined #xen
09:38	<mancdaz>	ivan: thanks
09:38	\|-\|	anball [~anball@bi01p1.nc.us.ibm.com] has quit [Quit: Leaving]
09:42	\|-\|	ygcheny [~ygcheny@gaia.lan2net.fr] has quit [Quit: Leaving]
09:53	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has quit [Quit: mdday]
10:05	\|-\|	Edgan [~Edgan@71.83.124.204] has quit [Quit: Client exiting]
10:05	\|-\|	aliguori [~anthony@pixpat.austin.ibm.com] has joined #xen
10:06	\|-\|	gerrit [~gerrit@129.33.1.37] has joined #xen
10:06	<iamlost>	wb gerrit
10:06	<iamlost>	aliguori: what is a cluster filesystem?
10:06	<aliguori>	iamlost, howdy
10:07	<aliguori>	iamlost, typically, it's a filesystem that shared between many nodes who's storage is distributed in some way (like afs, dfs, gpfs, etc)
10:07	<iamlost>	or nfs
10:07	<aliguori>	no
10:07	<iamlost>	?
10:07	<aliguori>	nfs is not a cluster filesystem
10:07	\|-\|	mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has joined #xen
10:07	<aliguori>	b/c the data is stored on a server
10:08	<aliguori>	as opposed to shared across nodes
10:08	<iamlost>	oh
10:08	<iamlost>	so cluster is like peer to peer, vs nfs is like client-server
10:08	<iamlost>	?
10:08	\|-\|	hikenboot [~hikenboot@c-24-218-84-234.hsd1.ma.comcast.net] has quit [Quit: Leaving]
10:08	<aliguori>	sort of, but it's not true p2p
10:08	<aliguori>	it really depends on the actual cluster filesystem
10:09	<iamlost>	so theres more thalike how?
10:09	<iamlost>	argh
10:09	[~]	iamlost kicks the wireless
10:11	<hensema>	google on redhat global filesystem
10:11	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has joined #xen
10:11	<iamlost>	ok
10:11	[~]	iamlost kicks the wireless again
10:12	<iamlost>	someone needs to write a web-over -irc browser ;)
10:32	\|-\|	Netsplit iridium.oftc.net <-> jupiter.oftc.net quits: VS_ChanLog
10:34	\|-\|	Netsplit over, joins: VS_ChanLog
10:37	\|-\|	stekloff [~stekloff@129.33.1.37] has joined #xen
10:38	\|-\|	jerone [~jerone@pixpat.austin.ibm.com] has joined #xen
10:38	\|-\|	jerone [~jerone@pixpat.austin.ibm.com] has quit [Quit: ]
10:38	\|-\|	hollisb [~hollisb@pixpat.austin.ibm.com] has joined #xen
10:38	\|-\|	jerone [~jerone@pixpat.austin.ibm.com] has joined #xen
10:48	\|-\|	ns [~niv@129.33.1.37] has joined #xen
10:50	\|-\|	rharper [~rharper@pixpat.austin.ibm.com] has joined #xen
11:04	\|-\|	sdog [~sdog@62.58.98.210] has left #xen []
11:30	\|-\|	Basic_py [~Basic@warden.real-time.com] has quit [Quit: Leaving]
11:31	\|-\|	athomas [~athomas@host86-136-81-69.range86-136.btcentralplus.com] has quit [Quit: Leaving]
11:31	<ivan>	call i modify the frequency that xen recieves a timer interrupt?
11:32	\|-\|	harry_ [~harry@blueice1n1.uk.ibm.com] has quit [Quit: Leaving]
11:34	<iamlost>	ivan: i hope so
12:55	\|-\|	Basic_py [~Basic@gatekeeper.real-time.com] has joined #xen
12:56	<iamlost>	ivan: i would find that extemely useful
12:56	<iamlost>	myself
12:59	\|-\|	johnlev [~johnlev@nwkea-socks-2.sun.com] has joined #xen
13:34	\|-\|	felix [~felix@CPE001346d29ce3-CM00e06f1ae0c4.cpe.net.cable.rogers.com] has joined #xen
13:48	<ivan>	iamlost: you porting something to xen?
13:50	\|-\|	Solist [~Solist@85-250-91-173.bb.netvision.net.il] has joined #xen
13:50	<iamlost>	ivan: not really.
13:50	<Solist>	does anybody here knows about qemu disk emulation in vt-x?
13:51	<Solist>	My question is : does it use dma ?
13:51	<Solist>	I know that when using pcnet (AMD nic emulation) you use DMA
13:51	<Solist>	pcnet is the default ; but when using ne2000
13:51	<iamlost>	qemu itself didnt support DMA until recently...
13:51	<Solist>	emulation you DON'T use DMA
13:52	<Solist>	ialmosy: but when using pcnet you DO use dma
13:52	<Solist>	ialmost: any idea what the situation is in this regard with block device?
13:52	<riel>	using DMA is especially important for emulation
13:52	[~]	iamlost isnt sure xen wise
13:53	<riel>	because then the emulator can just dump all the data at once, instead of doing one emulated IO cycle for every few bytes of data transferred ;)
13:53	<Solist>	riel, ialmost: so this is a good reason to use dma in block device
13:54	<riel>	inside VT guests
13:54	<riel>	paravirtualised guests don't have any issues like this of course
13:54	<Solist>	I am talking abouy vt-x
13:55	<Solist>	so the guest run in non-roop operation mode
13:55	<riel>	in fact, if you emulate DMA to the host and the guest is LVM or partition backed (no loop driver), then dom0 could tell the hardware to really DMA into the guest directly
13:55	<riel>	I don't know if this is done for VT guests, but it could be ;)
13:55	\|-\|	dykman [~dykman@bi-02pt1.bluebird.ibm.com] has quit [Ping timeout: 480 seconds]
13:56	<Solist>	Ok I will have to delve into the code ; hoped someome know about it...
13:56	<Solist>	because in pcnet it DOES use dma
13:56	<f>	the IDE emulation in qemu supports aio (which is like dma) afaik
13:57	<f>	not sure if it works in Xen ioemu yet though - it tends to be stuck at an old qemu release
13:58	<Solist>	what do you mean like dma ? as I understand dma enabled access to memory without provessor intervention
13:58	<Solist>	does aio means also without processor intervention ?
13:58	<Solist>	I am not sure at all
14:00	<f>	solist: processor does the copies, but it runs asynchronous
14:00	<f>	solist: ok except if it uses O_DIRECT, but i don't think ioemu does that
14:02	<Solist>	f: I thing this mode of synchronous operation is a different leve when comparing to dma
14:03	<Solist>	i meant , of course, "a different level"
14:03	<Solist>	i don't know of comparing aio to dma is right
14:04	<f>	solist: in this case it's right. it's all virtual, remember.
14:05	<Solist>	f : on a second thought there is something true in what you say
14:13	\|-\|	Solist [~Solist@85-250-91-173.bb.netvision.net.il] has quit [Quit: Leaving]
14:28	\|-\|	hikenboot [~hikenboot@c-24-218-84-234.hsd1.ma.comcast.net] has joined #xen
14:30	<hikenboot>	I have compiled my xen kernel --its for use with iscsi as an initiator..it requires loading the nic driver into the kernel directly ..not as a module....I have compiled with this option but it the nic via_velocity simply doesnt load...anyone know what i am doing wrong?
14:47	<ns>	stupid question, but if you are compiling it into the kernel, what do you need loaded too? is the functionality not in the kernel? is the kernel not booting?
14:48	<hensema>	hikenboot: this is an domain0 kernel?
14:48	<hensema>	*a
14:51	<buggs>	aynone measured the performance of various switches and setups concerning > 4 GB memory in 32 Bit
14:51	<buggs>	?
14:51	<buggs>	any hints ?
15:06	<hikenboot>	I understand it doesnt matter iscsi wont have a problem with order of loading ..besides iscsi appears to be too unstable for my usage right now
15:07	<hikenboot>	buggs i have never installed a PAE enabled xen kernel..but havent heard of any issues
15:11	\|-\|	felix [~felix@CPE001346d29ce3-CM00e06f1ae0c4.cpe.net.cable.rogers.com] has quit [Ping timeout: 480 seconds]
15:13	<f>	tom woller is the master of the cryptic short patch descriptions
15:14	<iamlost>	nah
15:14	<iamlost>	thats me
15:14	<iamlost>	;)
15:33	<buggs>	does dom0 need to be configured for > 4GB though it only gets < 4GB ?
16:00	\|-\|	bestorga [~bestorga@129.33.1.37] has joined #xen
16:02	\|-\|	felix [~felix@CPE001346d29ce3-CM00e06f1ae0c4.cpe.net.cable.rogers.com] has joined #xen
16:03	\|-\|	mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has quit [Quit: Client exiting]
16:04	\|-\|	jimix [~jimix@yktgi01e0-s4.watson.ibm.com] has quit [Quit: jimix]
16:27	\|-\|	rusty [~rusty@bh02i525f01.au.ibm.com] has joined #xen
16:41	<Shaun>	buggs: yes
16:42	<Shaun>	buggs: everything needs to be built with PAE support (hypervisor,dom0, and domU)
16:45	\|-\|	felix [~felix@CPE001346d29ce3-CM00e06f1ae0c4.cpe.net.cable.rogers.com] has quit [Quit: Client exiting]
16:47	\|-\|	riel changed nick to unriel
16:50	\|-\|	rpg [~rpg@pixpat.austin.ibm.com] has quit [Remote host closed the connection]
16:50	\|-\|	rpg [~rpg@pixpat.austin.ibm.com] has joined #xen
16:57	\|-\|	mdday [~mdday@bi01p1.nc.us.ibm.com] has quit [Quit: mdday]
16:59	\|-\|	hikenboot_ [~hikenboot@c-24-218-84-234.hsd1.ma.comcast.net] has joined #xen
17:00	<hikenboot_>	can anyone give the steps ..or put into a wiki the steps for setting up xen with a custom kernel..like adding drivers...I keep doing this and after screwing with it for a few hours get it working but never figure out exactly how!
17:01	<hikenboot_>	MAYBE somone should write a proper README file for the xen located in the mercurial database
17:01	<iamlost>	hikenboot: i use th xen-sparse tree that comes with 3.0.1 tho
17:02	<hikenboot_>	no problem i will use xen 3.0.1 for now since i am not using the iscsi which seems to lead into using it
17:03	<hikenboot_>	scarry thing is i always manage to get the damn thing working dancing around with make dist make world and all that stuff but have no understanding of what is actually happening
17:04	<hikenboot_>	i know that i have a custom config right now that works except has to be recompiled with NIC driver NOT loaded directly into the kernel
17:05	\|-\|	jerone [~jerone@pixpat.austin.ibm.com] has quit [Quit: Leaving]
17:05	<hikenboot_>	but damned if i can figure out what i did to compile it the first time with the dom0 specific kernel rather than the generic domo/domU kernel
17:06	<hikenboot_>	I thought I saved my directions as I went ..but cant find them either...ah...damn....
17:07	<hikenboot_>	these are the newest directions ive found but they leave somthing to be desired....http://www.unix-tutorials.com/go.php?id=438
17:08	<iamlost>	building using a custom config was painful
17:11	<tonfa>	iamlost: what i do is putting the ARCH=xen stuff in my oldconfig
17:11	<tonfa>	and then doing make ARCH=xen oldconfig
17:13	<hikenboot_>	so i should go into the directory lets say for instance linux-26.16-rc4-xen0
17:13	<tonfa>	yes
17:13	<hikenboot_>	then do a nano .confiig ...put in ARCH=xen in there?
17:13	<tonfa>	no
17:14	<tonfa>	you copy the lines that talks about xen from xen0 defconfig into your customized config
17:15	<tonfa>	like CONFIG_XEN=y
17:15	<tonfa>	then you copy your customized config to .config and make ARCH=xen oldconfig
17:15	<tonfa>	it should results in a xen0 domain with the same drivers as your customized config
17:17	<hikenboot_>	ok so lets make this simple for a stupid moron like me....I goto the .config that is in the root of the mercurila.hg download of xen and copy from it the xen specific lines and copy them into my existing .config?
17:17	<tonfa>	yes
17:17	<hikenboot_>	I assume make ARCH=xen oldconfig would bring up menuconfig for further editing?
17:17	<tonfa>	no, it will ask some questions
17:18	<tonfa>	it tries to use the existing config as a valid one
17:18	<tonfa>	and asks question for new entries
17:21	<hikenboot_>	ok there is no .config in the root folder of xen just the .config that I created in the subdirectory called linux-2.6.16-rc4-xen0
17:22	<hikenboot_>	which was built originally with xen which i edited some how..(dont remember how)
17:22	<hikenboot_>	what kills me is it was so damn easy for me to do I just dont remember they syntax i used
17:25	\|-\|	dansmith [~dan@129.33.1.37] has quit [Quit: Leaving]
17:28	<hikenboot_>	the directions say 1) make linux-2.6-xen-config CONFIGMODE=menuconfig 2)make linux-2.6-xen-build 3) make linux-2.6-xen-install 4) depmod 2.6.12.6-xen 5) mkinitrd -0 /boot/initrd-2.6.12.6-xen.img 2.6.12.6-xen...............however in my case I DONT want to build the root xen config that is generic and but rather wish to build the dom0/domU kernels specifically...but I dont understand how to do this!
17:29	<hikenboot_>	the problem is with line............make linux-2.6-xen-config which somehow finds a generic config probably from buildconfigs directory
17:30	\|-\|	Basic_py [~Basic@gatekeeper.real-time.com] has quit [Quit: Leaving]
17:30	<hikenboot_>	I notice there is a mk.linux-2.6-xen file in the buildconfigs directory ..I wonder if i were to replace it with my config if it would pick up myconfig instead or would it error out
17:32	<hikenboot_>	nope that aint it
17:35	<aliguori>	qemu has supported dma for disks for quite some time (emulation at least). qemu recently got async io support (which is implemented with a thread--the underlying device is not opened with O_DIRECT though)
17:35	<aliguori>	xen got a different version of that patch that was written by some intel guys
17:35	<aliguori>	same basic idea though
17:36	<iamlost>	aliguori: different patch?
17:36	<aliguori>	yes
17:36	[~]	iamlost looks lost
17:36	<aliguori>	some intel guys wrote their own async io ptach
17:36	<iamlost>	was it xen only?
17:36	<aliguori>	specifically for xen
17:36	<aliguori>	yes
17:36	<iamlost>	oh
17:36	<iamlost>	ic
17:37	<hikenboot_>	aliguori: can you tell me what changes in the steps i listed above i should make to just edit a xen kernel configuration that I created for dom0?
17:37	<aliguori>	nope
17:37	<aliguori>	just use the default kernel
17:37	<aliguori>	i've not built a -xen kernel.
17:37	<aliguori>	i just use whatever make gives me
17:38	<hikenboot_>	I have to customize it...I am unfortuantly required to do it since i am building the kernel with computer spefic changes..
17:39	<hikenboot_>	pisses me off cause i did it once about two days ago wrote my steps down and lost the damn sheet of paper
17:42	\|-\|	aliguori [~anthony@pixpat.austin.ibm.com] has quit [Quit: Ex-Chat]
17:42	<hikenboot_>	the way i swear i did it was to cd linux-2.6-16-rc4-xen0 then make ARCH=xen menuconfig
17:43	<hikenboot_>	but it gives me make*** No rule to make target
17:43	\|-\|	surriel changed nick to riel
17:43	<michal`>	and it is right :]
17:43	<michal`>	now xen is an subarch of x86
17:43	<michal`>	so just make menuconfig
17:45	<hikenboot_>	YES....thank you thank you ...I knew it was somthing simple I did
17:46	[~]	michal` is xen newbie also ;]
17:46	<michal`>	just select xen somewhere in the menu
17:46	<michal`>	in kind of architecture
17:47	<hikenboot_>	I really need a course in compilers
17:47	<michal`>	btw
17:47	<hikenboot_>	seems like everyone does it differnetly...
17:47	\|-\|	dansmith [~dan@c-24-21-32-166.hsd1.or.comcast.net] has joined #xen
17:48	<michal`>	something what made my weekend with xen terrible - make sure you are using gcc 3 series (no 4)
17:50	\|-\|	ivan [~ikelly@83-71-74-95.b-ras1.lmk.limerick.eircom.net] has quit [Quit: leaving]
17:53	<hikenboot_>	ok so it would be make menuconfig CC=gcc-3.2 ?
17:53	<hikenboot_>	or does that come later
17:55	<tonyb>	hikenboot_: on all your make lines supply CC=gcc-3.2 HOSTCC=gcc-3.2 to be safe
17:56	<tonyb>	although aside from warnings I'm not haveing any problems with gcc-4*
18:00	<michal`>	it is told that tools are officialy not working with xen 3 and gcc 4
18:00	<hikenboot_>	well i used that about six months ago on my config..problem is i have never changed from the instructions on the readme..this time it was necessary..the README leaves a little to be desired I will write somthing up and submit it to the users list or the dev list suggesting the method you guys have helped me with
18:01	<michal`>	here something tries to write into fd -1 ;p
18:06	\|-\|	rharper [~rharper@pixpat.austin.ibm.com] has quit [Quit: Leaving]
18:08	<hikenboot_>	the second line read make linux-2.6-xen-build.....I assume it should now read make CC=gcc-3.3 HOSTCC=gcc-3.3 ?????????yes and the third line make install CC=gcc-3.3 HOSTCC=gcc-3.3 ????? is that riight michal?????
18:10	\|-\|	pvanhoof [~pvanhoof@d54C0FBBD.access.telenet.be] has quit [Remote host closed the connection]
18:21	\|-\|	horms [~horms@vagw.valinux.co.jp] has joined #xen
18:25	\|-\|	michal` [~michal@www.rsbac.org] has quit [Ping timeout: 480 seconds]
18:26	\|-\|	felix [~felix@CPE001346d29ce3-CM00e06f1ae0c4.cpe.net.cable.rogers.com] has joined #xen
18:29	\|-\|	hikenboot_ [~hikenboot@c-24-218-84-234.hsd1.ma.comcast.net] has quit [Quit: Leaving]
18:29	\|-\|	hikenboot [~hikenboot@c-24-218-84-234.hsd1.ma.comcast.net] has quit [Remote host closed the connection]
18:33	\|-\|	michal` [~michal@www.rsbac.org] has joined #xen
18:34	\|-\|	aliguori [~anthony@cpe-70-116-13-229.austin.res.rr.com] has joined #xen
18:36	\|-\|	Shoragan [~shoragan@d072.apm.etc.tu-bs.de] has quit [Quit: Leaving]
18:46	\|-\|	felix [~felix@CPE001346d29ce3-CM00e06f1ae0c4.cpe.net.cable.rogers.com] has quit [Quit: Client exiting]
18:47	\|-\|	bestorga [~bestorga@129.33.1.37] has quit [Quit: Leaving]
18:48	\|-\|	ns [~niv@129.33.1.37] has quit [Quit: Leaving]
18:49	\|-\|	stekloff [~stekloff@129.33.1.37] has quit [Quit: Leaving]
18:55	\|-\|	Basic_py [~Basic@warden.real-time.com] has joined #xen
19:07	\|-\|	hollisb [~hollisb@pixpat.austin.ibm.com] has quit [Quit: leaving]
19:10	\|-\|	dansmith [~dan@c-24-21-32-166.hsd1.or.comcast.net] has quit [Quit: Leaving]
19:22	\|-\|	jimix [~jimix@ip139.152.45.216.suscom.net] has joined #xen
20:00	\|-\|	hollisb [~hollisb@user-0vvde2g.cable.mindspring.com] has joined #xen
20:21	\|-\|	michal` [~michal@www.rsbac.org] has quit [Ping timeout: 480 seconds]
20:23	\|-\|	gerrit [~gerrit@129.33.1.37] has quit [Ping timeout: 480 seconds]
20:25	\|-\|	michal` [~michal@www.rsbac.org] has joined #xen
21:15	\|-\|	f [~f@p54898F37.dip0.t-ipconnect.de] has quit [Ping timeout: 480 seconds]
21:43	\|-\|	Basic_py [~Basic@warden.real-time.com] has quit [Quit: Leaving]
22:23	\|-\|	gerrit [~gerrit@c-67-160-146-170.hsd1.or.comcast.net] has joined #xen
22:29	\|-\|	hollisb [~hollisb@user-0vvde2g.cable.mindspring.com] has quit [Quit: leaving]
22:35	\|-\|	horms [~horms@vagw.valinux.co.jp] has quit [Quit: Leaving]
22:41	\|-\|	muli_ [~muli@87.69.40.180.cable.012.net.il] has quit [Remote host closed the connection]
22:54	\|-\|	Basic_py [~Basic@warden.real-time.com] has joined #xen
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:02	\|-\|	AlexMBas [~Alexandre@200.138.135.250] has joined #xen
23:18	\|-\|	f [~f@p54898BF8.dip0.t-ipconnect.de] has joined #xen
23:24	\|-\|	jimix [~jimix@ip139.152.45.216.suscom.net] has quit [Quit: jimix]
23:48	\|-\|	zwane [~zwane@S0106001217d33fa6.vc.shawcable.net] has quit [Remote host closed the connection]
---	Log	closed Wed Mar 01 00:00:34 2006