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

---	Log	opened Wed Jan 17 00:00:31 2007
00:15	\|-\|	guillaume_t [~guillaune@129.184.84.11] has joined #xen
00:54	\|-\|	sdague [~sdague@user-12lc6iq.cable.mindspring.com] has quit [Ping timeout: 480 seconds]
01:20	\|-\|	mulix [~mulix@87.69.40.180.cable.012.net.il] has quit [Remote host closed the connection]
01:21	\|-\|	Extro [~aaron@r74-193-69-30.pfvlcmta01.grtntx.tl.dh.suddenlink.net] has joined #xen
01:23	<Extro>	is windows 64-bit guest OS supportedd with AMD hardware virt?
01:37	<icblenke>	yes? with a 64bit hypervisor. I think. probably should try that here at some point.
01:43	<Extro>	okee.. I tried installing xp 64-bit a few weeks ago and it woudlld hang up..i'll have to try again
01:44	<icblenke>	installing might be a problem. try converting a vmware built image.
01:44	<icblenke>	that's what I'd do myself.
01:56	\|-\|	hollisb [~hollisb@user-0vvdf2d.cable.mindspring.com] has quit [Quit: Leaving]
01:57	\|-\|	mastermind [~mastermin@mastermind.kaltenbrunner.cc] has quit [Quit: Client exiting]
02:03	\|-\|	visik7 [~visi@82.58.136.174] has quit [Remote host closed the connection]
02:06	\|-\|	zwane_r3k [~zwane@S0106001217d33fa6.vc.shawcable.net] has quit [Ping timeout: 480 seconds]
03:24	\|-\|	cableman [~cableman@3e6b2807.rev.stofanet.dk] has joined #xen
03:34	\|-\|	Extro [~aaron@r74-193-69-30.pfvlcmta01.grtntx.tl.dh.suddenlink.net] has quit [Quit: Hey! Where'd my controlling terminal go?]
03:36	\|-\|	mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has joined #xen
03:37	\|-\|	athomas [~athomas@host86-134-167-36.range86-134.btcentralplus.com] has joined #xen
04:38	\|-\|	visik7 [~visi@82.58.136.174] has joined #xen
05:09	\|-\|	fernando [~fernando@189.0.154.44] has joined #xen
05:09	\|-\|	bernarde [~bernarde@32.104.18.240] has joined #xen
06:05	\|-\|	cableman [~cableman@3e6b2807.rev.stofanet.dk] has quit [Remote host closed the connection]
06:20	\|-\|	guillaume_t [~guillaune@129.184.84.11] has quit [Quit: Leaving]
06:26	\|-\|	guillaume_t [~guillaune@129.184.84.11] has joined #xen
06:29	\|-\|	agrif_away changed nick to agriffis
06:33	\|-\|	fernando_ [~fernando@189.0.132.137] has joined #xen
06:38	\|-\|	fernando [~fernando@189.0.154.44] has quit [Ping timeout: 480 seconds]
06:44	\|-\|	visik7 [~visi@82.58.136.174] has quit []
06:53	\|-\|	infernix [nix@spirit.infernix.net] has quit [Read error: Connection reset by peer]
06:55	\|-\|	sdague [~sdague@user-12lc6iq.cable.mindspring.com] has joined #xen
06:58	\|-\|	infernix [nix@spirit.infernix.net] has joined #xen
07:06	\|-\|	pvanhoof [~pvanhoof@d54C0EE14.access.telenet.be] has joined #xen
07:12	\|-\|	infernix [nix@spirit.infernix.net] has quit [Quit: Leaving]
07:13	\|-\|	guillaume_t [~guillaune@129.184.84.11] has quit [Quit: Leaving]
07:15	\|-\|	infernix [nix@spirit.infernix.net] has joined #xen
07:30	\|-\|	guillaume_t [~guillaune@129.184.84.11] has joined #xen
07:52	<matti>	http://www.phoronix.com/vr.php?view=8410
07:56	\|-\|	clalance [~clalance@nat-pool-bos.redhat.com] has joined #xen
08:01	\|-\|	bernarde [~bernarde@32.104.18.240] has quit [Ping timeout: 480 seconds]
08:14	\|-\|	visik7 [~visi@host174-136-dynamic.58-82-r.retail.telecomitalia.it] has joined #xen
08:20	\|-\|	infernix [nix@spirit.infernix.net] has quit [Remote host closed the connection]
08:25	\|-\|	aw [~awilliam@c-24-9-84-32.hsd1.co.comcast.net] has quit [Quit: Leaving]
08:39	\|-\|	KriP [kp@yancey.unixworld.dk] has joined #xen
08:48	\|-\|	guillaume_t [~guillaune@129.184.84.11] has quit [Quit: Leaving]
08:49	\|-\|	danp1 [~berrange@pool-72-93-175-181.bstnma.east.verizon.net] has joined #xen
08:50	\|-\|	zwane_r3k [~zwane@S0106001217d33fa6.vc.shawcable.net] has joined #xen
08:57	\|-\|	riel [~riel@offshore-host.offshoreexecutive.com] has quit [Remote host closed the connection]
08:59	\|-\|	infernix [nix@spirit.infernix.net] has joined #xen
09:00	\|-\|	kalden [~kalden@fac34-3-82-231-26-11.fbx.proxad.net] has quit [Ping timeout: 480 seconds]
09:07	\|-\|	riel [~riel@bree.surriel.com] has joined #xen
09:14	\|-\|	bernarde [~bernarde@32.104.18.240] has joined #xen
09:20	\|-\|	jerone [~jerone@adsl-71-145-130-136.dsl.austtx.sbcglobal.net] has joined #xen
09:20	\|-\|	rharper [~rharper@r74-193-70-77.pfvlcmta01.grtntx.tl.dh.suddenlink.net] has joined #xen
09:27	\|-\|	mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has quit [Quit: Leaving]
09:29	\|-\|	jnalley [~jnalley@r74-192-163-42.gtwncmta01.grtntx.tl.dh.suddenlink.net] has quit [Quit: [BX] Time wasted: 22 days 19 hours 17 minutes 37 seconds 66 milliseconds ]
09:39	\|-\|	riel [~riel@bree.surriel.com] has quit [Read error: Connection timed out]
09:41	\|-\|	riel [~riel@bree.surriel.com] has joined #xen
09:42	\|-\|	infernix [nix@spirit.infernix.net] has quit [Remote host closed the connection]
09:44	\|-\|	visik7 [~visi@host174-136-dynamic.58-82-r.retail.telecomitalia.it] has quit [Remote host closed the connection]
09:47	\|-\|	mulix [~mulix@87.69.40.180.cable.012.net.il] has joined #xen
09:50	\|-\|	visik7 [~visi@host174-136-dynamic.58-82-r.retail.telecomitalia.it] has joined #xen
10:05	\|-\|	aw [~awilliam@ftcrel3.hp.com] has joined #xen
10:22	\|-\|	brianw [~ahzz@pool-71-170-81-199.dllstx.fios.verizon.net] has joined #xen
10:33	\|-\|	aw [~awilliam@ftcrel3.hp.com] has quit [Remote host closed the connection]
10:35	\|-\|	agriffis changed nick to agrif_away
10:35	\|-\|	aw [~awilliam@ftcrel3.hp.com] has joined #xen
10:59	\|-\|	xai [~pasta@cpe-70-113-32-246.austin.res.rr.com] has quit [Quit: Client exiting]
11:05	\|-\|	agrif_away changed nick to agriffis
11:07	\|-\|	mastermind [~mastermin@mastermind.kaltenbrunner.cc] has joined #xen
11:10	\|-\|	ivan [~ikelly@5ac197ad.bb.sky.com] has joined #xen
11:25	\|-\|	sputhenp [~sputhenp@202.80.58.210] has quit [Remote host closed the connection]
11:31	\|-\|	athomas [~athomas@host86-134-167-36.range86-134.btcentralplus.com] has quit [Quit: Leaving]
11:33	\|-\|	_bernarde [~bernarde@32.104.18.240] has joined #xen
11:37	\|-\|	bernarde [~bernarde@32.104.18.240] has quit [Ping timeout: 480 seconds]
11:47	\|-\|	hollisb [~hollisb@user-0vvdf2d.cable.mindspring.com] has joined #xen
11:50	<hollisb>	rharper: looks like a target has presented itself for prose builder patches :)
11:51	<rharper>	hollisb: I saw Dilma's patch, if that is what you mean
11:51	<hollisb>	Maria's
11:51	<hollisb>	yes, that's what I mean
11:51	<rharper>	oh, sorry, right
12:09	\|-\|	aw [~awilliam@ftcrel3.hp.com] has quit [Quit: Leaving]
12:13	\|-\|	aw [~awilliam@156.153.254.66] has joined #xen
12:27	\|-\|	cableman [~cableman@3e6b6dca.rev.stofanet.dk] has joined #xen
12:28	\|-\|	mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has joined #xen
12:28	\|-\|	_bernarde changed nick to bernarde
12:29	\|-\|	danp2 [~berrange@pool-72-93-175-181.bstnma.east.verizon.net] has joined #xen
12:31	\|-\|	danp2 [~berrange@pool-72-93-175-181.bstnma.east.verizon.net] has quit []
12:32	\|-\|	danp1 [~berrange@pool-72-93-175-181.bstnma.east.verizon.net] has quit [Quit: Leaving.]
12:32	\|-\|	danp1 [~berrange@pool-72-93-175-181.bstnma.east.verizon.net] has joined #xen
12:36	\|-\|	mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has quit [Quit: Leaving]
12:40	\|-\|	danp1 [~berrange@pool-72-93-175-181.bstnma.east.verizon.net] has quit [Ping timeout: 480 seconds]
12:46	\|-\|	danp1 [~berrange@pool-72-93-175-181.bstnma.east.verizon.net] has joined #xen
12:48	\|-\|	mcr [~mcr@desk.marajade.sandelman.ca] has joined #xen
12:49	<mcr>	I'm having difficulty with vif=[]. I want to set the bridge name as well. is it: "vif = [ 'mac=STUFF', 'bridge=xenoelan'] {this gives me two interfaces on the guest!}, or is it
12:49	<mcr>	vif = [ 'mac=00:16:3e:00:a0:30 bridge=xenoelan' ]
12:50	<mcr>	which seems to give me one network device, but I don't think it worked. the guest is a NetBSD XENU.
12:54	\|-\|	visik7 [~visi@host174-136-dynamic.58-82-r.retail.telecomitalia.it] has quit [Remote host closed the connection]
12:54	\|-\|	ahs3_away changed nick to ahs3
12:55	<mcr>	vif = [ 'mac=00:16:3e:00:a0:30, bridge=xenoelan' ]
12:55	<mcr>	that's how it is.
12:56	<mcr>	the links to the man pages on the wiki don't work.
13:33	\|-\|	infernix [nix@spirit.infernix.net] has joined #xen
13:34	\|-\|	mcr [~mcr@desk.marajade.sandelman.ca] has left #xen []
13:37	\|-\|	ivan [~ikelly@5ac197ad.bb.sky.com] has quit [Remote host closed the connection]
13:46	\|-\|	visik7 [~visi@87.3.42.164] has joined #xen
13:53	\|-\|	infernix [nix@spirit.infernix.net] has quit [Remote host closed the connection]
13:55	\|-\|	bernarde [~bernarde@32.104.18.240] has quit [Remote host closed the connection]
14:20	\|-\|	infernix [nix@spirit.infernix.net] has joined #xen
14:29	\|-\|	aw [~awilliam@156.153.254.66] has quit [Quit: Leaving]
14:31	\|-\|	aw [~awilliam@ftcrel3.hp.com] has joined #xen
14:40	\|-\|	swingle [~swingle@204.Red-81-40-150.staticIP.rima-tde.net] has joined #xen
14:40	<swingle>	hi
14:40	<swingle>	is there anybody out there?
14:42	<swingle>	i have a couple of questions
14:43	<swingle>	first, i tried today the latest version of xen and the linux framebuffer wouldnt work with it
14:43	<swingle>	i just chose the same compile options and used the same kernel line as with my previous kernel but it stopped working
14:44	<swingle>	and second, ive read a bit about xenfb, could i use that to view the "screen" of an hvm guest running windows?
14:45	<swingle>	about the first thing id like to know if anybody managed to make it work
14:59	\|-\|	Piet [hiddenserv@tor.noreply.org] has joined #xen
15:10	<icblenke>	yes.
15:11	<icblenke>	with HVM, it works just as documented.
15:11	<icblenke>	with PV, I haven't build a xenfb linux domU kernel to play with it yet.
15:11	<swingle>	so i wouldnt have to do anything special? just create the domain and execute sdlfb?
15:12	<icblenke>	you don't need "sdlfb" with HVM, just sdl=1 in your config file.
15:12	<icblenke>	when you "xm create" the HVM image, your DISPLAY variable denotes where the SDL console will be displayed.
15:12	<swingle>	the problem is that id like to be able to disconnect one vm and connect another one to the window
15:12	<icblenke>	likewise, if you use vnc=1, after "xm create", there will be a VNC server listening on a port at 5900+
15:12	<swingle>	so i could use the same window to manage both
15:13	<icblenke>	I don't get what you mean. You mean you're doing fullscreen now, and you don't want to?
15:13	<swingle>	no, i do xm create and an SDL window pops up
15:13	<icblenke>	correct.
15:14	<icblenke>	if you want to "float" that console, you must use VNC.
15:14	<swingle>	i dont want it to pop up i want to create several domains and then create an SDL window and show one of them
15:14	<swingle>	then show a different domain on the window, etc
15:15	<icblenke>	use VNC, and a VNC client that lets you connect to multiple VNC ports and switch between them.
15:16	<swingle>	so it is not possible to do what i want with sdl?
15:16	<icblenke>	each HVM domain with sdl=1 gets its own SDL X11 window. that's just how it works. if you want to change that behavior, you're going to have to dive into the xen source and build your own solution.
15:16	<swingle>	i c
15:16	<swingle>	btw whats sdlfb for then?
15:17	<icblenke>	no clue. my guess, it has something to do with PV framebuffers.
15:17	<swingle>	ok
15:17	<icblenke>	haven't really dug into how the framebuffer stuff actually works. just how it behaves.
15:19	<icblenke>	my guess is that the xend harness probably spawns off an sdlfb daemon for HVM just as it does with 3.0.4 and a PV framebuffer.
15:20	\|-\|	bernarde [~bernarde@201.72.60.80] has joined #xen
15:21	\|-\|	msinhore [~msinhore@mail.samurai.com.br] has quit [Quit: scp -C msinhore home:msinhore]
15:24	<swingle>	theres a file named sdl.c inside tools/ioemu that creates an SDL window and shows the console
15:24	<swingle>	thats what is used when you set sdl=1 in the config file
15:25	<swingle>	and it has nothing to do with the new framebuffer right?
15:25	\|-\|	bernarde [~bernarde@201.72.60.80] has left #xen []
15:26	<swingle>	and theres a file named sdlfb.c in tools/xenfb that creates an SDL and shows the console too and uses the new framebuffer
15:26	\|-\|	mdday [~mdday@cpe-024-163-122-235.nc.res.rr.com] has quit [Remote host closed the connection]
15:27	<swingle>	when i run sdlfb it just hangs waiting for the framebuffer to be ready
15:28	<Piet>	hi, i'm having difficulties getting kernel output passed to console with xen. it works fine with comparable grub parameters on the default (debian) kernel image for the same kernel version.
15:28	<icblenke>	you shouldn't need to run sdlfb directly. the xend harness should start it as appropriate.
15:28	<Piet>	i read this http://lists.xensource.com/archives/html/xen-users/2005-08/msg00472.html
15:28	<aliguori>	swingle: are you sure you're activating the framebuffer in the guest?
15:28	<Piet>	but i dion't understand how to actually make it work
15:28	<aliguori>	i think it requires kernel parameters and it has to have the right kernel config options
15:28	\|-\|	agriffis changed nick to agrif_away
15:28	<swingle>	aliguori, its a windows guest, what do you mean with "activating"?
15:28	<aliguori>	swingle: sdlfb has nothing to do with HVM guests
15:29	<aliguori>	if you set sdl=1 with an HVM guest, it should Just Work
15:29	<icblenke>	Piet: xendcons=ttyS is the default dom0 option, try xendcons=tty
15:29	<swingle>	Piet, you have to say no to a kernel option under the XEN menu which disables the serial port
15:29	<icblenke>	er, xencons=tty, that is. no "d".
15:29	<aliguori>	assuming that the SDL development libraries were available when you compiled xen
15:29	<aliguori>	swingle: that is almost certainly your problem
15:29	<aliguori>	xen will not complain, it will just silently compile out SDL support
15:29	<swingle>	aliguori, my problem is that i dont really understand how the new framebuffer works
15:30	\|-\|	aw [~awilliam@ftcrel3.hp.com] has quit [Quit: Leaving]
15:30	<aliguori>	swingle: it has nothing to do with HVM domains
15:30	<aliguori>	it's a paravirtual framebuffer
15:30	<aliguori>	it's for PV guests only
15:30	<swingle>	i see
15:30	<icblenke>	aliguori: how do you specify a PV framebuffer then? (haven't researched the mailing list for instructions yet)
15:30	<Piet>	icblenke: this thread i just referred to states it's not xencons but ttyS0 on linux
15:31	<aliguori>	icblenke: same options as HVM (provided that you compile proper support in)
15:31	<Piet>	icblenke: ignore that last statement
15:31	<icblenke>	Piet: your kernel is logging its console messages somewhere else. console=tty or console=ttys, along with xencons=tty or ttys, it's going to boil down to that.
15:32	<swingle>	so if i want to run 4 guests simultaneously my only choice with SDL is to create 4 windows and keep them all open?
15:32	<aliguori>	swingle: yes
15:32	<aliguori>	that's why there's vnc
15:32	<icblenke>	aliguori: ok. if I specify serial=`pty`, will ttyS in the domU get assigned to xenconsole like with HVM?
15:32	<aliguori>	icblenke: it should
15:32	<swingle>	aliguori, but the mouse sucks when i use vnc
15:32	<swingle>	and its awfully slow
15:33	<aliguori>	icblenke: i didn't do the xend plumbing so I don't know for sure
15:33	<aliguori>	swingle: use the usb tablet
15:33	\|-\|	mdday [~mdday@cpe-024-163-122-235.nc.res.rr.com] has joined #xen
15:33	<aliguori>	that will keep the mouse from sucking so much
15:33	<aliguori>	swingle: SDL is really not that much better FWIW
15:34	<swingle>	at least with SDL theres only one mouse pointer
15:34	<aliguori>	swingle: the usb tablet will make you much happier
15:34	<swingle>	ok ill try it
15:34	<aliguori>	i dunno what the config options are, but i think it's documented pretty well in the hvm example config
15:34	<icblenke>	so usb='tablet' applies to HVM and PV domains, specifically to how the SDL/VNC consoles do cursor positioning?
15:35	<aliguori>	icblenke: no, only HVM domains
15:35	<swingle>	is it planned to add framebuffer support for hvm domains?
15:35	<aliguori>	icblenke: PV is problematic b/c Linux sucks a whole lot :-)
15:35	<aliguori>	swingle: no, that doesn't really make all that much sense
15:35	<aliguori>	there's no real benefit for that
15:35	<swingle>	it would make it wasy for people like me to code a viewer
15:35	<swingle>	*easy
15:36	<aliguori>	icblenke: in future versions of Xen, the VNC situation will improve. I've authored a VNC extension to improve mouse support and once we get it in xen and viewers start supporting it, these problems will go away
15:36	<swingle>	tying domains to windows on creation doesnt sound like a good idea
15:36	<Piet>	icblenke: you think this will work? http://channels.debian.net/paste/paste
15:36	<aliguori>	swingle: i guess. i prefer vnc myself
15:37	<swingle>	btw is it possible to make vnc to listen on a unix socket to speed things up?
15:37	<danp1>	SDL stuff just sucks as is - if you loose your SDL window, say good bye to the whole guest
15:37	[~]	swingle agrees with danp1
15:37	<aliguori>	swingle: not in the current version of xen, but it will in future versions of xen
15:38	<danp1>	swingle: not in Xen there isn't
15:38	<aliguori>	swingle: and it doesn't really speed anything up
15:38	<danp1>	but really it doesn't do anything for performance
15:38	<danp1>	the bottleneck is not the socket stuff when on a local machine
15:38	<swingle>	ok
15:38	<danp1>	in fact i've not noticed any real speed problem with the display at all, when used locally
15:38	<aliguori>	danp1: the unix socket stuff is in qemu upstream and christians already ported ioemu to cvs so it should be an easy switch over once fabrice releases something
15:39	<swingle>	so what is my best choice if i want to make VMs look like real PCs?
15:39	\|-\|	aw [~awilliam@156.153.254.69] has joined #xen
15:39	<swingle>	SDL or VNC?
15:39	<aliguori>	swingle: honestly, virt-manager
15:39	<danp1>	i ithink VNC is the only long term useful display
15:39	<aliguori>	if you're having this much trouble, that's what i'd recommend
15:40	<danp1>	we only really have SDL at all, because QEMU happened to already support it
15:40	<icblenke>	it's interesting that the vbox guys made an RDP server, but didn't opensource it.
15:40	<swingle>	what makes virt-manager better?
15:40	<danp1>	better than what ?
15:40	<aliguori>	icblenke: i'm not sure i see the benefit of RDP over VNC (other than windows client support)
15:40	<swingle>	better than SDL and VNC
15:40	<murb>	icblenke: maybe they licensed it?
15:40	<danp1>	virt-manager uses VNC to talk to the guest already
15:40	<icblenke>	perhaps.
15:40	<aliguori>	swingle: it just makes it a lot saner b/c you've got a nice gui with the display integrated
15:41	<aliguori>	you don't have to screw around with external viewers
15:41	<danp1>	swingle: eg http://virt-manager.et.redhat.com/screenshots/guest-console.png
15:42	<swingle>	ok
15:42	<swingle>	i think ill chose vnc
15:43	<swingle>	what do i need to make vnc work? xen + vncserver + vncviewer ?
15:43	<swingle>	or is the server integrated inside xen?
15:43	<icblenke>	integrated.
15:43	<icblenke>	you just need a vncviewer.
15:43	<icblenke>	(assuming you build your xen with vnc support, isn't that optional like sdl?)
15:44	<swingle>	it is but ive already built it with vnc support
15:44	<aliguori>	icblenke: no
15:44	<swingle>	no?
15:44	<swingle>	the docs say it is
15:44	<icblenke>	the docs often lie.
15:44	<swingle>	:)
15:44	<aliguori>	the vncfb stuff may be optional
15:44	<icblenke>	take vnet for example.
15:44	<aliguori>	oh dear
15:45	<aliguori>	icblenke: vnet is a sore subject :-)
15:45	<Piet>	could someone have a look at http://channels.debian.net/paste/5116 and make a guess on whether the xen boot stanza will work as expected?
15:45	<icblenke>	does anyone know if Virtual Iron's "virtual switches" are little more than vnet?
15:45	<aliguori>	Piet: RTM. that's nto the right syntax for Xen
15:45	<aliguori>	Piet: I don't recall the proper syntax off the top of my head, but it's something like console=com1
15:48	\|-\|	Piet_ [hiddenserv@tor.noreply.org] has joined #xen
15:48	<swingle>	does anybody know why the linux framebuffer doesnt work with xen?
15:48	<aliguori>	for dom0?
15:48	<swingle>	linux framebuffer = the thing you enable appending video=vesafb to your kernel line
15:48	<swingle>	yep
15:48	<aliguori>	b/c xen takes over CGA
15:49	<icblenke>	grub also eats "vga=extended"
15:49	<icblenke>	lilo doesn't. you don't now how much grub irritates me with that behavior.
15:49	<swingle>	aliguori, so theres no way to make it work?
15:49	<aliguori>	i don't think so
15:49	<rharper>	com1=115200,8n1 console=com1 is what I have for serial output from xen
15:49	<aliguori>	but i'm not 100% sure
15:50	<swingle>	CGA = color graphics adapter right?
15:50	<Piet_>	rharper: thank you
15:50	<rharper>	Piet_: on the kernel /boot/xen.gz line
15:50	<icblenke>	com1=115200,8n1 console=com1,vga
15:50	\|-\|	Piet [hiddenserv@tor.noreply.org] has quit [Killed (NickServ (GHOST command used by Piet_))]
15:50	<icblenke>	that's what I have.
15:51	<swingle>	aliguori, whats CGA?
15:52	<aliguori>	swingle: the text terminal mode
15:52	<icblenke>	grub eats "vga=80x50" if you try and pass it to xen.
15:52	<swingle>	icblenke, when i boot xen with vga=791 and check out /proc/cmdline it shows it right
15:53	<Piet_>	http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/user/user.html#s:xboot
15:53	<Piet_>	found it
15:53	\|-\|	Piet_ changed nick to Piet
15:53	<icblenke>	swingle, not the dom0 kernel. the xen hypervisor. it has a special vga= option for extended 80x50 VGA mode and whatnot.
15:56	<icblenke>	apparently grub takes any kernel option with vga= to mean that you really meant for it to be a linux vga mode number (like 791) and hacks it to be that.
15:57	<icblenke>	when I boot mbootpack with vga=80x50, I get my nice extended VGA mode.
15:57	<icblenke>	(under lilo)
15:57	<swingle>	i get the extended VGA mode with grub too
15:57	<icblenke>	with Xen?
15:57	<swingle>	yep
15:57	<swingle>	what i cant get is the 1024x768 vesafb mode
15:58	\|-\|	Jaff [~jk@bart.cs.aau.dk] has joined #xen
15:58	<icblenke>	on your dom0?
15:58	<swingle>	yes on my dom0
15:59	<swingle>	and to be fair i dont know why cause im giving it vga=791 but thats what i get
16:00	<icblenke>	if your kernel has vesafb linked in monolitically, it should.
16:00	<swingle>	icblenke, aliguori says it shouldnt
16:00	<icblenke>	oh?
16:00	<swingle>	and i think hes right cause i tried it and it didnt work :(
16:02	<icblenke>	dom0 is just another PV domain, though it has PCI device access, so you can still use a PCI video driver with your video card, I can see why vesafb might not work.
16:02	\|-\|	Jaff [~jk@bart.cs.aau.dk] has quit []
16:03	\|-\|	Jaff [~jk@bart.cs.aau.dk] has joined #xen
16:03	<icblenke>	the big pain seems to be with the AGP gart and patches for things like nvidia's nvgart.
16:06	<swingle>	it shouldnt need agp for vesafb
16:07	<swingle>	it looks like it just ignores framebuffer drivers
16:09	<icblenke>	I don't know how vesa works, but I had thought it was a BIOS thing.
16:09	<icblenke>	as Xen hides the hardware from guests, it makes perfect sense.
16:10	<icblenke>	http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
16:10	<swingle>	yep i do know how vesa works, what i didnt know is that xen hides the real BIOS from dom'
16:10	<swingle>	*dom0
16:11	<icblenke>	dom0 is just another paravirtualized domain with all PCI devices assigned to it by default.
16:11	<swingle>	dom0 cant be hvm?
16:11	<icblenke>	nope.
16:11	<swingle>	hehe then thats why it was so damn slow
16:11	<icblenke>	what are you talking about?
16:12	<swingle>	i was running linux with a normal kernel
16:12	<swingle>	then i tried a xen kernel and everything was much slower
16:12	\|-\|	Basic_py [~Basic@warden.real-time.com] has quit [Quit: Leaving]
16:12	<swingle>	i didnt know why
16:13	<icblenke>	were you booting with acpi=off or was there another interrupt issue? that's the only time I've really found a xen dom0 any slower than raw iron.
16:13	<swingle>	i didnt boot with acpi=off
16:13	<swingle>	should i?
16:13	<icblenke>	booting with acpi=off and/or noapic can fix things.
16:13	<swingle>	ok ill try it
16:13	<icblenke>	(xen hypervisor options)
16:14	<icblenke>	(xen passes those options along to the dom0 kernel)
16:14	<swingle>	you mean adding acpi=off to the kernel commadn line right?
16:14	<icblenke>	to the xen hypervisor line.
16:14	<swingle>	where is that?
16:15	<icblenke>	in /boot/grub/menu.lst ?
16:16	<swingle>	title=Gentoo (linux-2.6.19-gentoo-r2)
16:16	<swingle>	root (hd0,2)
16:16	<swingle>	kernel /kernel-2.6.19-gentoo-r2 root=/dev/hda5 video=radeonfb:1280x1024 quiet pci=assign-busses
16:16	<swingle>	you mean adding it there next to pci=assign-busses ?
16:16	<icblenke>	no. that's a raw iron linux kernel boot.
16:16	<swingle>	yeh i know
16:16	<icblenke>	where is your kernel /xen.gz line?
16:16	<swingle>	heh in another computer
16:16	<icblenke>	this is #xen, right? ;)
16:16	<swingle>	but i recall something like:
16:17	<swingle>	kernel /xen.gz
16:17	<swingle>	module /vmlinuz...
16:17	<icblenke>	that's correct.
16:17	<icblenke>	add it to the kernel line.
16:17	<swingle>	ok
16:17	<swingle>	thx :)
16:17	<icblenke>	not the module line.
16:20	<Piet>	http://channels.debian.net/paste/5117
16:21	<Piet>	got the serial console working. the url explains how
16:21	<Piet>	thanks for everyones' help
16:23	<swingle>	where can i configure xen's vnc to allow connections only from localhost?
16:24	<rharper>	maybe /etc/xen/xend-config.sxp ?
16:24	<swingle>	dunno is it there?
16:26	<icblenke>	vnclisten.
16:27	<icblenke>	that's a 3.0.4 option, anyway.
16:27	<icblenke>	and, hey, it's right there in xend-config.sxp too. how about that.
16:43	\|-\|	KriP [kp@yancey.unixworld.dk] has quit [Quit: Leaving]
16:44	<jimix>	hollisb: there?
16:51	<swingle>	im leaving, good night
16:51	\|-\|	swingle [~swingle@204.Red-81-40-150.staticIP.rima-tde.net] has quit [Quit: Leaving]
16:53	\|-\|	Basic_py [~Basic@gatekeeper.real-time.com] has joined #xen
16:57	\|-\|	jimix [~jimix@c-67-189-187-152.hsd1.ny.comcast.net] has quit [Quit: jimix]
17:15	\|-\|	cableman [~cableman@3e6b6dca.rev.stofanet.dk] has left #xen [Leaving]
17:26	\|-\|	clalance [~clalance@nat-pool-bos.redhat.com] has quit [Quit: Leaving]
17:27	\|-\|	aw [~awilliam@156.153.254.69] has quit [Quit: Leaving]
17:27	\|-\|	aw [~awilliam@156.153.254.69] has joined #xen
17:31	\|-\|	rharper [~rharper@r74-193-70-77.pfvlcmta01.grtntx.tl.dh.suddenlink.net] has quit [Quit: Leaving]
17:39	\|-\|	mdday changed nick to mday_away
18:06	\|-\|	ivan [~ikelly@5ac197ad.bb.sky.com] has joined #xen
18:14	\|-\|	cilkay [~cilkay@CPE00d0b743a22f-CM0011ae01fcbe.cpe.net.cable.rogers.com] has joined #xen
18:14	\|-\|	kozy [~kozy@82-170-128-66.dsl.ip.tiscali.nl] has joined #xen
18:19	<kozy>	hello people, I'd like to use Xen on a new Xeon (em64t) using Debian Etch. Is it necessary to use a special em64t kernel and what are the advantages? Or can I just go with the available amd64 packages?
18:25	\|-\|	danp1 [~berrange@pool-72-93-175-181.bstnma.east.verizon.net] has left #xen []
18:25	\|-\|	aw [~awilliam@156.153.254.69] has quit [Quit: Leaving]
18:26	<kozy>	I am aiming for stability on a production server
18:29	\|-\|	visik7 [~visi@87.3.42.164] has quit [Remote host closed the connection]
18:30	<kozy>	found the information here http://www.ducea.com/2006/10/10/debian-etch-kernels/
18:31	<kozy>	tnx anyway ;)
18:35	\|-\|	kozy [~kozy@82-170-128-66.dsl.ip.tiscali.nl] has quit [Quit: BitchX: made with real honey.]
19:03	\|-\|	fernando_ [~fernando@189.0.132.137] has quit [Remote host closed the connection]
19:10	\|-\|	ahs3 changed nick to ahs3_away
19:46	\|-\|	infernix [nix@spirit.infernix.net] has quit [Remote host closed the connection]
19:50	\|-\|	w3pog [~pgrace@aeneas.fierymoon.com] has joined #xen
19:51	<w3pog>	hey guys.. I'm trying to boot xen 3.0.2 on a quad-p3 xeon box with 4gb of ram. The machine gets so far into the xen boot and then reboots before I can see what the error is
19:51	<w3pog>	is there a way I can make it pause so I can see what it's complaining about?
19:54	<hollisb>	I think there's a "noreboot" boot parameter
19:54	<hollisb>	something like that
19:57	<w3pog>	do you know where such an option might go? I tried it on the xen dom0 boot line but it didn't do it
19:58	<hollisb>	it would be the Xen line, not the dom0 line
19:58	<w3pog>	module=xen.gz one?
19:58	<w3pog>	cool I'll try that
19:58	<hollisb>	mmm
19:59	<hollisb>	xen isn't a module
19:59	<hollisb>	you load it with a "kernel" command
19:59	<hollisb>	right?
19:59	<w3pog>	let me check the grub line
19:59	<w3pog>	I have to wait for the machine to spin back up every time, takes about 3 mins for all the drives to get reinitialized
20:00	<w3pog>	kernel /boot/vmlinuz-2.6.18-3-686 root=/dev/sda1 ro
20:00	<w3pog>	hmm
20:00	<w3pog>	there's no mention of xen..
20:00	<w3pog>	hmm.
20:00	<w3pog>	not 100% sure but I think I've found my problem
20:00	<hollisb>	:)
20:02	\|-\|	CleeK_ [~CleeK@124.10.202.62.fix.bluewin.ch] has quit [Read error: Connection reset by peer]
20:03	<w3pog>	There's something quite amiss
20:04	<w3pog>	The first being that I didn't load xen on it yet. hah.
20:05	<w3pog>	It was just a normal smp kernel (haven't fired up this box in a few days)
20:13	\|-\|	gerrit [~gerrit@c-67-160-146-170.hsd1.or.comcast.net] has quit [Quit: Client exiting]
20:17	\|-\|	dhendrix_work [~dhendrix@216-239-45-4.google.com] has joined #xen
20:17	\|-\|	CleeK_ [~CleeK@124.10.202.62.fix.bluewin.ch] has joined #xen
20:41	\|-\|	Basic_py [~Basic@gatekeeper.real-time.com] has quit [Quit: Leaving]
20:44	\|-\|	Piet [hiddenserv@tor.noreply.org] has quit [Quit: Piet]
21:13	\|-\|	Basic_py [~Basic@warden.real-time.com] has joined #xen
21:26	\|-\|	infernix [nix@spirit.infernix.net] has joined #xen
21:27	<w3pog>	ok, now that I have xen loaded on it.. Meh, the scsi board is being misbehaved it appears
21:51	\|-\|	pvanhoof [~pvanhoof@d54C0EE14.access.telenet.be] has quit [Remote host closed the connection]
21:58	\|-\|	hollisb [~hollisb@user-0vvdf2d.cable.mindspring.com] has quit [Quit: Leaving]
22:06	\|-\|	segher [~segher@dslb-084-056-132-007.pools.arcor-ip.net] has quit [Ping timeout: 480 seconds]
22:08	\|-\|	segher [~segher@dslb-084-056-180-166.pools.arcor-ip.net] has joined #xen
22:10	<w3pog>	That figures. Tracked down the ultimate problem to a bad raid controller. So I put an old buslogic I had lying around into the box, and of course xen doesn't have a buslogic module in 3.0.2! batting a thousand
22:37	\|-\|	aw [~awilliam@ftcrel4.hp.com] has joined #xen
22:46	\|-\|	The_Eye [~noone@c-67-176-167-93.hsd1.il.comcast.net] has joined #xen
22:48	<The_Eye>	Anyone running suse and 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:17	\|-\|	sputhenp [~sputhenp@202.80.58.210] has joined #xen
---	Log	closed Thu Jan 18 00:00:31 2007