--- Day changed

--- Log opened Thu Mar 24 23:59:03 2005
00:11 -!- ijuz_ [~ijuz@p54ABED34.dip.t-dialin.net] has joined #xen
00:19 -!- ijuz [~ijuz@p54ABD06A.dip.t-dialin.net] has quit [Ping timeout: 480 seconds]
01:24 -!- DEac- [~deac@xdsl-213-196-197-235.netcologne.de] has joined #xen
02:21 -!- Shaun [~ndci@ip68-111-70-41.oc.oc.cox.net] has joined #xen
06:08 -!- muli [muli@alhambra.mulix.org] has quit [Quit: My damn controlling terminal disappeared!]
09:16 -!- mdday [~mdday@bi01p1.nc.us.ibm.com] has joined #xen
10:11 -!- Method [~Method@stanford.columbia.tresys.com] has joined #xen
10:31 -!- rharper [~rharper@pixpat.austin.ibm.com] has joined #xen
10:50 -!- hollis [~hollis@pixpat.austin.ibm.com] has joined #xen
11:00 -!- hollis [~hollis@pixpat.austin.ibm.com] has quit [Quit: Lost terminal]
11:07 -!- hollis [~hollis@pixpat.austin.ibm.com] has joined #xen
11:45 -!- plars [~plars@pixpat.austin.ibm.com] has quit [Ping timeout: 480 seconds]
11:56 -!- plars [~plars@pixpat.austin.ibm.com] has joined #xen
13:57 -!- Sir_Ahzz [~ahzz@c-24-0-215-3.client.comcast.net] has quit [Ping timeout: 480 seconds]
13:59 -!- Sir_Ahzz [~ahzz@c-24-0-215-3.client.comcast.net] has joined #xen
13:59 -!- mode/#xen [+o Sir_Ahzz] by ChanServ
14:00 -!- DEac- [~deac@xdsl-213-196-197-235.netcologne.de] has quit [Ping timeout: 480 seconds]
14:11 -!- DEac- [~deac@xdsl-213-196-203-223.netcologne.de] has joined #xen
14:48 < Method> does anyone know why vmware won't run in a domain 0 xen guest?
15:03 -!- anticw is now known as cw
15:03 < cw> Method: it has various needs that aren't presently virtualized to work with Xen
15:03 < cw> Method: my guess is that vmware/emc really are the only people who can address that
15:04 < Method> i see, so it's similar to the OS porting issue?
15:05 < cw> similar yes
15:05 < cw> vmware (probably, i didn't check) uses various instructions it shouldn't and the kernel module does things that will need changing for xen
15:06 < Method> well, it won't be an issue once windows supports xen :)
15:07 < cw> windows wont support xen ever as-is i bet
15:07 < cw> not anything you and distributate anyhow, you need to get VT silicon for windows to work
15:09 < Method> at the point where the processor can virtualize what is the advantage of running xen?
15:11 < hollis> you need sofware (e.g. xen) to take advantage of that hardware support
15:11 < hollis> the hardware can only offer you the capability
15:11 < cw> xen is fine for *bsd, linux, etc.
15:11 < cw> for many people that is *all* they will ever want ... windows isn't useful to them
15:11 < Method> cw: sure..
15:11 < cw> if you want windows to work virtualized you need to get VT support and that will also be *slower* too
15:12 < demon> not really
15:12 < demon> once you have hardware support for full virtualization, it won't be notably slower
15:12 < cw> at some point microsoft will have their own VM/Monitor and windows i bet for their datacenter range
15:12 < demon> well, they already do
15:12 < cw> yes
15:12 < demon> or are trying to get that going
15:12 < demon> that's what VirtualPC is for
15:12 < cw> and it will be slower (a bit) that xen + modified OS
15:13 < cw> yeah, but i bet once VT silicon is out there you will be able to partition windows and fancy things
15:13 < demon> only if you have to deal a lot with emulated hardware should you see a notable slowdown
15:13 < Method> isn't the vt processor instruction set very close to xen's instruction set? why would it be slower?
15:13 < cw> for the high-end spendy version of windows, not sure if any of that will work with xen or a non-ms monitor
15:13 < cw> Method: it will be slower because you have to emulate hardware at a lower-level still so there is some overhead
15:14 < cw> xen has no instruction set, the VT stuff allows us to virtualize things that are hard/impossible now
15:34 -!- mdday [~mdday@bi01p1.nc.us.ibm.com] has left #xen [/dev/stomach]
15:41 -!- rharper [~rharper@pixpat.austin.ibm.com] has quit [Quit: Leaving]
17:03 -!- hollis [~hollis@pixpat.austin.ibm.com] has quit [Quit: leaving]
17:49 -!- MadMethod [~Method@209.60.7.66] has joined #xen
17:50 -!- Method [~Method@stanford.columbia.tresys.com] has quit [Ping timeout: 480 seconds]
17:57 -!- jonmason [~jonmason@pixpat.austin.ibm.com] has quit [Remote host closed the connection]
17:58 -!- hollis [~hollis@user-0vvde2g.cable.mindspring.com] has joined #xen
18:02 -!- jonmason [~jonmason@pixpat.austin.ibm.com] has joined #xen
18:07 -!- jonmason [~jonmason@pixpat.austin.ibm.com] has quit [Read error: Connection reset by peer]
18:12 -!- jonmason [~jonmason@pixpat.austin.ibm.com] has joined #xen
18:30 -!- MadMethod [~Method@209.60.7.66] has quit [Ping timeout: 480 seconds]
18:45 -!- Method [Method@pcp0010742058pcs.howard01.md.comcast.net] has joined #xen
18:46 -!- hollis [~hollis@user-0vvde2g.cable.mindspring.com] has quit [Quit: leaving]
19:15 -!- ijuz_ [~ijuz@p54ABED34.dip.t-dialin.net] has quit [Quit: Client exiting]
20:54 -!- Nigelenki [~bluefox@pcp484971pcs.whtmrs01.md.comcast.net] has joined #xen
20:54 -!- Bluefox [~bluefox@pcp484971pcs.whtmrs01.md.comcast.net] has quit [Read error: Connection reset by peer]
--- Log closed Fri Mar 25 23:59:00 2005