--- Day changed

--- Log opened Tue May 31 23:59:02 2005
00:11 -!- nextime [~nextime@213-140-6-96.fastres.net] has quit [Ping timeout: 480 seconds]
01:25 -!- Shaun [ndci@ip68-111-70-41.oc.oc.cox.net] has joined #xen
02:20 -!- rusty [~rusty@bh02i525f01.au.ibm.com] has joined #xen
03:18 -!- franR [~franr@inextensia.net] has joined #xen
03:26 -!- homebaum_ [~michael@wbar1.sea1-4-5-031-104.sea1.dsl-verizon.net] has quit [Ping timeout: 480 seconds]
03:33 -!- murble [~murble@debian.home.boughton.org.uk] has quit [Quit: leaving]
03:35 -!- mufa [~erer@hide.eea.eu.int] has joined #xen
03:54 < mufa> I have a problem when booting a virtual domain: "Could not load /lib/modules/2.6.11-1.1353_FC4xenU/modules.dep: No such file or directory". What should I do in order to have that? Thanks
04:08 < bunoc> mufa, ignore that warning.
04:09 < bunoc> it is all fine
04:09 < mufa> bunoc: well, if not having modules is fine
04:12 -!- rusty [~rusty@bh02i525f01.au.ibm.com] has quit [Quit: Client exiting]
04:19 -!- cilkay [~cilkay@CPE00d0b743a22f-CM0011ae01fcbe.cpe.net.cable.rogers.com] has quit [Ping timeout: 480 seconds]
04:34 < mufa> is it possible to nfs mount home directories from a xen domain?
04:42 -!- demon [demon@66.35.250.240] has quit [Ping timeout: 480 seconds]
05:08 -!- Beaky [~chatzilla@ncg-adsl.demon.co.uk] has joined #xen
05:21 -!- athomas [~athomas@ppp-0-112.lond-a-1.access.uk.tiscali.com] has joined #xen
06:06 -!- DEac- [~deac@xdsl-195-14-218-178.netcologne.de] has quit [Ping timeout: 480 seconds]
06:19 -!- DEac- [~deac@xdsl-213-196-206-153.netcologne.de] has joined #xen
06:34 -!- tim [~tim@cpe-66-67-139-238.rochester.res.rr.com] has joined #xen
07:01 -!- Quozl [~james@144.135.190.104] has joined #xen
07:03 < Quozl> Erm, help?  Debian Sid, domain 0 boot, "Kernel panic: VFS: Unable to mount root fs on 03:04", using kernel-image-2.4.25-xeno-p2 ... as if initrd not seen, but my grub has extra module ref.
07:04 -!- jimix [~jimix@ip13.194.susc.suscom.net] has joined #xen
07:10 < Quozl> Help.  http://pastebin.com/293213  domain 0 kernel fails to boot, as if initrd missing.
07:10 -!- jimix [~jimix@ip13.194.susc.suscom.net] has quit [Quit: jimix]
07:54 -!- Quozl [~james@144.135.190.104] has quit [Quit: think of it as evolution in action]
09:12 < mufa> is xen supported on rhel?
09:16 < athomas> Supported by Red Hat? No.
09:17 < athomas> It can be made to work though.
09:19 < mufa> after many hours of hard working
09:22 < mael> and you should expect a lot of strange things
09:23 < mael> such as bush being re-elected, or spaceship landing in your garden
09:23 < mufa> well, then I'll say boss it is not possible
09:23 < mael> and so on
09:23 < mufa> thanks
09:52 -!- hollis [~hollis@user-0vvde2g.cable.mindspring.com] has joined #xen
09:55 -!- homebaum [~michael@pool-71-111-177-107.ptldor.dsl-w.verizon.net] has joined #xen
10:10 -!- yarihm [~yarihm@80-218-1-211.dclient.hispeed.ch] has joined #xen
10:27 -!- cilkay [~cilkay@CPE00d0b743a22f-CM0011ae01fcbe.cpe.net.cable.rogers.com] has joined #xen
10:31 < mufa> how could I install FC2 inside a xen domain?
10:48 < athomas> http://www.fedoraproject.org/wiki/FedoraXenQuickstart
10:49 < mufa> thank you... I am following that site instructions
10:49 -!- rharper [~rharper@pixpat.austin.ibm.com] has joined #xen
10:52 -!- yarihm [~yarihm@80-218-1-211.dclient.hispeed.ch] has quit [Quit: Leaving]
11:15 -!- mufa [~erer@hide.eea.eu.int] has quit [Quit: Leaving]
11:18 -!- MarkW [~MarkW@maw48.kings.cam.ac.uk] has joined #xen
11:21 < mael> hi MarkW !
11:21 < MarkW> MarkW: Hi there
11:21 < MarkW> mael: oops, not muchpoint me talking to myself!  (tab completion ;-)
11:21 < MarkW> How's it going?
11:21 < mael> 'been a long time
11:21 < MarkW> indeed
11:21 < mael> away for holidays?
11:22 < MarkW> I've been doing mostly teaching work, so I've not done much development recently.
11:22 < mael> okay
11:22 < mael> so no work on xenfs :)
11:22 < MarkW> I've only got one more hour of teaching, then I can get back to hacking on Xen!
11:22 -!- ruuth [VooDoo@topas.informatik.uni-ulm.de] has joined #xen
11:23 < MarkW> Nope, not at the moment.  I've almost got kexec working though.
11:23 < mael> oh yeah that was rescheduled as a high priority task for 3.0 release
11:24 < MarkW> Was it?
11:24 < MarkW> I was just playing with it because it looked cool!
11:24 < mael> mmh from what I remember, yeah
11:25 < MarkW> Ah, it seems to be on "optional" on the wiki page
11:25 < MarkW> Guess I should put my name in there!
11:25 < mael> mmh yeah
11:25 < mael> strange
11:26 < MarkW> It's caused me to start having evil ideas about kexec in Xen itself though.
11:26 < mael> you're not alone on this task, are you?
11:26 < MarkW> Yup
11:26 < MarkW> I'm treating kexec in a guest and kexec for the whole host as separate issues.
11:27 < MarkW> But I've recently been thinking about a separate project to hot-upgrade Xen underneath running domains...  A fair bit of hacking required but it would be way cool.
11:29 < hollis> hmm, yeah :)
11:31 -!- Aaby [~aaby@port79.ds1-abc.adsl.cybercity.dk] has joined #xen
11:32 < mael> MarkW:  you told soffi about a "xen-get" stuff for domains, is it still an idea?
11:32 -!- Aaby [~aaby@port79.ds1-abc.adsl.cybercity.dk] has left #xen []
11:32 -!- mejlholm [~mejlholm@port79.ds1-abc.adsl.cybercity.dk] has joined #xen
11:34 < mael> I think this might be a cool feature for ISPs offering Virtual Private Servers
11:34 < mael> and for ppl who'd like to test xen also :)
11:34 < MarkW> hollis: I think the Linux kexec patch will be reasonably straightforward to import into Xen.  The largest amount of effort required will be to serialise the subset of Xen's internal state that can't be refreshed from dom0
11:35 < MarkW> mael: Yes, I think it's a really worthwhile thing to have, so I'll probably take a look at it again some time.
11:35 < mael> MarkW:  I try quite hard to find time to write a small article on usages you can think for xen
11:35 < hollis> given the constant stream of xend bug reports, it sounds like dom0 is one of the least reliable places to get state from ;)
11:35 < MarkW> mael: Soffi set up an XML feed from his Xen images pages which you can track with an RSS reader. We'd use the contents of this feed in the xen-get tool.
11:36 < mael> MarkW:  he did it by hand, right?
11:36 < MarkW> hollis: yeah, Xend is a really big bit of code and difficult to debug.  Hopefully the recent (and planned changes) will make it a bit easier to deal with!
11:37 < MarkW> mael: I think so, yes.
11:37 < mael> ok
11:38 < MarkW> mael: what usages have you got so far (for your article)?
11:38 < mael> mmh let me check
11:38 < mael> I have to download the tex sources
11:40 < mael> 7
11:40 < mael> 1- consolidation of multiple applications on a single server
11:40 < mael> 2- virtual dedicated servers at a ISP housing facility
11:40 < mael> 3- backup, development or test server
11:40 < mael> 4- high availability applications
11:41 < mael> 5- workstation management and deployment using VM
11:41 < mael> 6- using unused workstation CPU cycles to run distributed programs on a backend VM
11:41 < mael> 7- computer running two or more operating system at a time on x86 hardware virtualization
11:42 < MarkW> OK, sounds good.
11:43 < MarkW> You might also run an IDS / Firewall on a user's machine, separate from the VM they were using.
11:43 < mael> yes this is an aspect I talk about in the first point
11:43 < mael> as this is common to all usages
11:43 < MarkW> That way, you can firewall your machines with all the hosts in your company firewalling themself, rather than a one big (expensive) firewall box.
11:44 < MarkW> Yeah, OK.
11:44 < mael> ah this is good you talked about this : what would be the best practise : firewall on dom0 or on domU?
11:44 < mael> I'm not so sure at the moment
11:44 < mael> dom0 is a bad choice for security, but domU takes ressources
11:45 < mael> and DomU is still complicated for the network stuff right now
11:45 < MarkW> At the moment, X can only run in dom0 -> if the user is to use screen / keyboard they must log into dom0
11:45 < mael> (as you have to give privileges on pci devices if you need perfs)
11:45 < mael> X?
11:45 < MarkW> X server
11:45 < mael> hum? what to do with firewalling? :)
11:46 < mael> okay you mean for workstations
11:46 < mael> with linux running as the "frontend VM"
11:46 < MarkW> The ideal case would be to have domU running the Xserver and dom0 being the "management partition", which your site sysadmin logs into and does firewalling
11:46 < mael> yes this is the design I talk about
11:46 < MarkW> mael: exactly, for workstations so that ordinary users can have a "personal" firewall that's centrally controlled
11:47 < mael> actually the article will try to outline all the stuff missing in Xen for those usages :)
11:47 < MarkW> Support for driver domains is only going to get better over time.  I expect one day we'll be able to give multiple domains their own graphics card / keyboard.
11:47 < mael> it's not about trying to build a system using hacks/kludge with the existing stuff
11:48 < MarkW> Also, with Intel / AMD's Trusted Computing stuff, giving access to a PCI device will no longer require trust.
11:48 < mael> yeah this is a point I don't know much about
11:48 < mael> I talked a bit about this with Keir and James
11:49 < MarkW> mael: Good point.  Xen works well for standard virtual hosting some of the cooler applications are not easy to do at the moment.
11:49 < mael> and read Intel's VT documentation
11:49 < mael> but it's still very foggy for me
11:49 < MarkW> mael: VT + LT combined will support a "page table" for DMA accesses
11:49 < mael> LT?
11:49 < MarkW> LaGrande (intel's trusted computing).  It has VT as a prereq, I believe.
11:50 < mael> eurk
11:50 < MarkW> With the page table for IO, you'll be able to do per-page / per device protections like you can do per page / per process protection for normal memory access.
11:50 < mael> okay
11:50 < MarkW> So in particular, a domain will only be granted mappings to DMA to memory it can access normally.
11:51 < MarkW> Right guys, I need to head off and mark a big pile of my students' work now.
11:52 < MarkW> I'll probably be around later (more so once I've finished with the teaching)
11:52 < mael> yeah I have to go back home and take care of the kid
11:52 < mael> see ya
11:53 < mael> it's nice to see you around, you're a good source of fresh information :)
11:54 < MarkW> mael: :-)
11:54 < MarkW> see ya
11:54 -!- MarkW [~MarkW@maw48.kings.cam.ac.uk] has left #xen [Kopete 0.10.2 : http://kopete.kde.org]
11:55 -!- Beaky [~chatzilla@ncg-adsl.demon.co.uk] has quit [Remote host closed the connection]
12:02 -!- hollis [~hollis@user-0vvde2g.cable.mindspring.com] has quit [Quit: leaving]
12:12 -!- niv [~nivedita@bi01p1.co.us.ibm.com] has joined #xen
12:33 -!- hollis [~hollis@pixpat.austin.ibm.com] has joined #xen
12:33 < Sir_Ahzz> mooo
12:39 -!- knewt_ [~jmb@zeus.pimb.org] has joined #xen
12:44 -!- knewt_ [~jmb@zeus.pimb.org] has quit [Remote host closed the connection]
12:44 -!- knewt_ [~jmb@p213.54.65.86.tisdip.tiscali.de] has joined #xen
12:46 -!- knewt [~jmb@p213.54.101.238.tisdip.tiscali.de] has quit [Ping timeout: 480 seconds]
12:53 -!- athomas [~athomas@ppp-0-112.lond-a-1.access.uk.tiscali.com] has quit [Quit: Leaving]
13:03 -!- doremifa [~Administr@YahooBB219206220072.bbtec.net] has joined #xen
13:06 -!- Tv [~Tv@hq.inoi.fi] has joined #xen
13:19 -!- liberie [~root@dsl027-160-029.atl1.dsl.speakeasy.net] has joined #xen
13:33 -!- ruuth [VooDoo@topas.informatik.uni-ulm.de] has quit [Quit: Nettalk6 der Freeware IRC-Client]
13:59 -!- v-gge [vigge@fulhack.nu] has joined #xen
14:35 -!- doremifa [~Administr@YahooBB219206220072.bbtec.net] has quit [Ping timeout: 480 seconds]
14:56 -!- f9 [~andi@one.firstfloor.org] has joined #xen
15:06 -!- tim [~tim@cpe-66-67-139-238.rochester.res.rr.com] has quit [Ping timeout: 480 seconds]
15:40 -!- jonmason [~jonmason@pixpat.austin.ibm.com] has quit [Quit: using sirc version 2.211+KSIRC/1.3.11]
15:40 -!- jonmason [~jonmason@pixpat.austin.ibm.com] has joined #xen
15:44 -!- jdmason [~jonmason@pixpat.austin.ibm.com] has joined #xen
15:44 -!- jdmason [~jonmason@pixpat.austin.ibm.com] has quit [Quit: ]
15:54 -!- franR [~franr@inextensia.net] has quit [Quit: Error inopinée -10s, -9, -8...    Unexpected error -10s, -9, -8,... Really ?]
17:15 -!- demon [demon@newcastle.devrandom.net] has joined #xen
17:23 < niv> has anyone used the xen trace tools?
17:27 < jonmason> no
17:28 < dhendrix> fraid not
17:42 -!- chrish01 [~chrish01@69.90.131.10] has joined #xen
17:56 -!- Tv [~Tv@hq.inoi.fi] has quit [Quit: Client exiting]
18:42 -!- rharper [~rharper@pixpat.austin.ibm.com] has quit [Quit: Leaving]
18:54 -!- DEac- [~deac@xdsl-213-196-206-153.netcologne.de] has quit [Quit: Verlassend]
18:54 -!- DEac- [~deac@xdsl-213-196-206-153.netcologne.de] has joined #xen
19:02 -!- DEac- [~deac@xdsl-213-196-206-153.netcologne.de] has quit [Ping timeout: 480 seconds]
19:15 -!- DEac- [~deac@xdsl-213-196-204-6.netcologne.de] has joined #xen
19:26 -!- hollis [~hollis@pixpat.austin.ibm.com] has quit [Quit: leaving]
19:26 -!- chrish01 [~chrish01@69.90.131.10] has quit [Ping timeout: 480 seconds]
19:27 -!- chrish01 [~chrish01@lri01.sea.mosaix.net] has joined #xen
19:52 -!- drbyte [~cc2@c210-49-121-44.eburwd3.vic.optusnet.com.au] has quit [Ping timeout: 480 seconds]
19:58 -!- aeddan [~aeddan@203.39.89.243] has joined #xen
20:01 -!- tim [~tim@cpe-66-67-139-238.rochester.res.rr.com] has joined #xen
20:40 -!- nextime [~nextime@213-140-6-96.fastres.net] has joined #xen
20:49 -!- Quozl [~james@144.135.190.104] has joined #xen
20:50 < Quozl> Help.  Xen on Debian Sid problem ... unable to mount rootfs, but I have initrd ... http://pastebin.com/293213 has the details.
20:53 < nextime> Quozl : uhmm i think that your menu.lst is broken
20:54 < Quozl> nextime: thanks, what should i do to fix it?  in what way is it broken?
20:54 < nextime> Quozl : you must use xen.gz as kernel, and vmlinuz as module
20:54 < nextime> like this:
20:54 < nextime> title           Debian GNU/Linux, kernel 2.6.10-xen0 Default
20:54 < nextime> root            (hd0,0)
20:54 < nextime> kernel          /boot/xen.gz dom0_mem=131072
20:54 < nextime> module          /boot/vmlinuz-2.6.10-xen0 root=/dev/md0 ro
20:54 < nextime> savedefault
20:54 < nextime> boot
20:55 < nextime> ( this is on a debian sid too )
20:55 < Quozl> nextime: but i do; the locations there are where the debian packages place the files; /boot/xen.gz is not present, but that /usr/lib/kernels/xen-i386/1.2/images/vmlinuz was; by package xen.
20:56 < Quozl> nextime: so what created /boot/xen.gz on your system?
20:56 < nextime> Quozl : debian package...
20:56 < nextime> xen01:~# dpkg -S xen.gz
20:56 < nextime> xen: /boot/xen.gz
20:57 < Quozl> nextime: package xen version?
20:57 < nextime> on this server is Version: 2.0.4-4
20:57 < nextime> but i have more few xen servers with different versions
20:57 < Quozl> ah, okay, i'm using 1.2-4.1 from sid, not experimental.
20:58 < nextime> ok, i have no used 1.2 in my xen history, only 2.x
20:58 < Quozl> ok, i'll try 2.0.4 from experimental, thanks.
20:59 < nextime> Quozl : anyway, 2.x is very stable, i'm using it on production server 
21:20 -!- niv [~nivedita@bi01p1.co.us.ibm.com] has quit [Quit: Quitting]
21:31 -!- minemaz [~mine@YahooBB220055148023.bbtec.net] has joined #xen
22:19 -!- tim [~tim@cpe-66-67-139-238.rochester.res.rr.com] has quit [Ping timeout: 480 seconds]
22:22 -!- hollis [~hollis@user-0vvde2g.cable.mindspring.com] has joined #xen
23:33 -!- doremifa [~Administr@YahooBB219206220072.bbtec.net] has joined #xen
23:50 -!- doremifa [~Administr@YahooBB219206220072.bbtec.net] has quit [Ping timeout: 480 seconds]
--- Log closed Wed Jun 01 23:59:00 2005