--- Day changed

--- Log opened Fri May 06 23:59:02 2005
00:07 -!- tierra [~tierra@dsl093-225-126.slc1.dsl.speakeasy.net] has quit [Quit: bug, n: A son of a glitch.]
00:33 -!- drbyte [~byte@203-206-83-83.dyn.iinet.net.au] has quit [Quit: Leaving]
00:33 -!- JViz [Anomaly@cpe-065-190-040-040.triad.res.rr.com] has joined #xen
00:52 -!- drbyte [~byte@203-206-83-83.dyn.iinet.net.au] has joined #xen
01:36 -!- sleon [test@e180021175.adsl.alicedsl.de] has joined #xen
01:36 < sleon> will xen run on xen processors?
01:36 < sleon> xeon
01:37 < mikegrb> yes
01:41 < sleon> thx
01:42 < sleon> does it run stable?
01:42 < sleon> :)
01:42 < sleon> we going to use it on a dual production server
01:42 < mikegrb> as stable as xen anywhere else
01:42 < sleon> does it support multiprocessor arch
01:43 < sleon> and does it scale well?
01:43 < mikegrb> sure
01:43 < sleon> thx
02:33 -!- rusty [~rusty@ppp61-198.lns1.cbr1.internode.on.net] has quit [Quit: Client exiting]
03:42 -!- cfreak [cfreak@dsl-084-056-110-178.arcor-ip.net] has joined #xen
03:46 -!- cfreak| [cfreak@dsl-084-056-110-178.arcor-ip.net] has joined #xen
03:46 -!- cfreak [cfreak@dsl-084-056-110-178.arcor-ip.net] has quit [Read error: Connection reset by peer]
03:48 -!- cfreak [cfreak@dsl-084-056-110-178.arcor-ip.net] has joined #xen
03:48 -!- cfreak| [cfreak@dsl-084-056-110-178.arcor-ip.net] has quit [Read error: Connection reset by peer]
03:52 -!- cfreak [cfreak@dsl-084-056-110-178.arcor-ip.net] has quit [Read error: Connection reset by peer]
04:16 -!- drbyte [~byte@203-206-83-83.dyn.iinet.net.au] has quit [Read error: Operation timed out]
04:31 -!- drbyte [~byte@203-206-83-83.dyn.iinet.net.au] has joined #xen
05:15 -!- DEac- [~deac@xdsl-195-14-216-21.netcologne.de] has quit [Ping timeout: 480 seconds]
05:27 -!- DEac- [~deac@xdsl-213-196-202-187.netcologne.de] has joined #xen
06:18 -!- DEac- [~deac@xdsl-213-196-202-187.netcologne.de] has quit [Quit: Verlassend]
06:22 -!- DEac- [~deac@xdsl-213-196-202-187.netcologne.de] has joined #xen
06:24 -!- drbyte [~byte@203-206-83-83.dyn.iinet.net.au] has quit [Quit: Leaving]
06:59 -!- cfreak [cfreak@dsl-084-056-110-178.arcor-ip.net] has joined #xen
07:46 -!- drbyte [~byte@c210-49-121-44.eburwd3.vic.optusnet.com.au] has joined #xen
07:47 -!- cfreak [cfreak@dsl-084-056-110-178.arcor-ip.net] has quit [Quit: .]
09:46 -!- cfreak [cfreak@dsl-084-056-110-178.arcor-ip.net] has joined #xen
09:46 -!- monrad [~monrad@213083190130.sonofon.dk] has joined #xen
10:43 -!- monrad [~monrad@213083190130.sonofon.dk] has quit [Ping timeout: 480 seconds]
11:19 -!- MarkWilliamson [~MarkW@maw48.kings.cam.ac.uk] has joined #xen
11:43 -!- MarkWilliamson [~MarkW@maw48.kings.cam.ac.uk] has quit [Remote host closed the connection]
12:02 -!- imka [~imka@227.5-182-adsl-pool.axelero.hu] has joined #xen
12:02 < imka> hi channel
12:02 < imka> what is error 22? it's what i get when i try to save a domain
12:18 -!- MarkWilliamson [~MarkW@maw48.kings.cam.ac.uk] has joined #xen
12:28 < imka> hi MarkWilliamson 
12:28 < imka> what is error 22? it's what i get when i try to save a domain
12:29 < MarkWilliamson> imka: good question
12:29 < MarkWilliamson> hang on...
12:29 < MarkWilliamson> what error message do you get along with that number?
12:30 < imka> one sec, i'm gonna try to save and see
12:30 < MarkWilliamson> ok
12:32 < imka> it works now. i got error 22 when i was first playing with ttylinux. now debian is fine :)
12:33 < imka> xen is amazing btw. kudos!
12:34 < MarkWilliamson> imka: weird that you got that error.
12:34 < MarkWilliamson> but glad it works now!  have fun ;-)
12:35 < movement> any of the xen people looked closely at the intel VT stuff yet?
12:38 < tab> movement: yes, why that ?
12:38 < imka> MarkWilliamson, i get error 22 when i try to restore the domain :(
12:38 < movement> just wondering how good a fit it is
12:39 < MarkWilliamson> imka: oh dear
12:39 < MarkWilliamson> what error text gets spat out?
12:39 < imka> "Error: 22" that's all
12:41 < imka> ok, now that i'm in the same folder as the .xen file (stupid me) i get "Error: 1"
12:43 < MarkWilliamson> ah
12:43 < MarkWilliamson> that's not very a helpful error
12:43 < MarkWilliamson> it's probably "operation not permitted" - you are running this as root, right?
12:43 < imka> just to make sure: "xm restore debian.xen" right? yes, as root
12:44 < MarkWilliamson> sounds right
12:44 < MarkWilliamson> could you please look it /var/xen/{xfrd,xend,xend-debug}.log
12:45 < imka> on sec
12:45 < MarkWilliamson> there should me some more useful information at the end of those files regarding the failure
12:48 < MarkWilliamson> movement: VT seems sane
12:49 < MarkWilliamson> the intel people have contributed code to make Xen work on it - they're planning to get it booting windows eventually
12:49 < imka> MarkWilliamson, which file should i look up? there's xfrd xend and xend-debug
12:49 < MarkWilliamson> look at all of them
12:50 < MarkWilliamson> the barf will be somewhere near the end
12:53 < imka> [2005-05-07 18:52:23 xend] INFO (__init__:1032) restore BEGIN: ['restore', ['id', '7'], ['file', '/home/imka/debian.xen']]
12:53 < imka> [2005-05-07 18:52:23 xend] INFO (__init__:1032) EVENT> xend.domain.create ['Domain-8', '8']
12:53 < imka> [2005-05-07 18:52:23 xend] ERROR (__init__:1032) op=restore: 1
12:53 < imka> None
12:53 < knewt> MarkWilliamson: did i ever post the list with a patch to increase the size of PARSER_BUF_SIZE in sxpr_parser.h from it's annoyingly small 1024 characters?
12:53 < imka> xend.log
12:54 < MarkWilliamson> knewt: i don't think so, although that's bitten me too so it would be welcome
12:55 < yosh> MarkWilliamson: what would be the best way to get CONFIG_DEBUG_BUGVERBOSE defined for guest kernels?
12:58 < MarkWilliamson> imka: still not sure
12:58 < MarkWilliamson> is there anything interesting in "xm dmesg" (towards the end)?
12:58 < MarkWilliamson> what version of Xen?
12:58 < MarkWilliamson> what does "xm list" show?
12:58 < MarkWilliamson> yosh: is that a generic linux option?
13:00 < yosh> sort of. it's only configurable if CONFIG_EMBEDDED is set. otherwise it's on all the time
13:01 < yosh> it's missing from xen/i386/Kconfig tho
13:01 < imka> MarkWilliamson, it's xen 2.0 that coming with suse 9.3. xm list shows domain-0 running. i've stopped and started xend but no success
13:01 < MarkWilliamson> yosh: I guess you'll need to tweak with the Kconfig scripts to persuade the build system it's allowed
13:01 < yosh> but the xen traps.c expects it to be there
13:01 < MarkWilliamson> imka: ok, how about "xm dmesg"?
13:01 < yosh> MarkWilliamson: well, is simply adding it to xen/i386/Kconfig the best way?
13:02 < MarkWilliamson> yosh: xen's traps.c actually uses it?  i guess you may need to fix that if you want it configurable
13:02 < imka> MarkWilliamson, i don't see any error messages (xm dmesg)
13:02 < imka> must be some trivial mistake i'm making
13:02 < MarkWilliamson> yosh: adding it to Kconfig will do for testing.  any idea which Kconfig it's in usually
13:03 < MarkWilliamson> imka: what does "xm info" give you?  in particular i'm interested in the free memory
13:03 < yosh> MarkWilliamson: lib/Kconfig.debug
13:03 < MarkWilliamson> imka: any interesting info at the end of dom0's "dmesg"
13:03 < MarkWilliamson> yosh: i guess it could be tweaked there...
13:03 < MarkWilliamson> whichever looks cleanest, i guess
13:04 < imka> MarkWilliamson, i got 50 free memory
13:04 < MarkWilliamson> imka: how big's the domain?
13:04 < imka> domain-0 is 187
13:04 < yosh> MarkWilliamson: well, xen doesn't use that though. the debug options live in xen/i386/Kconfig
13:05 < MarkWilliamson> imka: but how big was the domain before you suspended it?
13:05 < MarkWilliamson> yosh: OK, I guess that's the best place for it then.
13:07 < knewt> MarkWilliamson: sent
13:07 < MarkWilliamson> knewt: bonza
13:07 < imka> MarkWilliamson, how do i find out?
13:08 < knewt> wow, lists.xensource is fast :)
13:09 < imka> brb
13:09 -!- imka [~imka@227.5-182-adsl-pool.axelero.hu] has quit [Quit: Leaving]
13:10 < yosh> MarkWilliamson: ok, I'll test and send patch to the mailing list
13:10 < movement> MarkWilliamson: neat
13:12 < MarkWilliamson> movement: the VT enhancements are used to trap stuff that was previously untrappable.  Xen contains code to virtualise the memory space.  IO requests are passed to a userspace daemon in dom0, which runs Bochs-derived virtual device models for video, disk, network...
13:13 < MarkWilliamson> movement: we'll hopefully see some similar code from AMD later on.
13:13 < movement> yeah, I've been following up the stuff
13:14 < movement> hmm, why did you end up implementing shadow page tables?
13:14 < movement> ease of porting?
13:14 < MarkWilliamson> movement: there's various modes of shadow page tables
13:14 -!- imka [~imka@227.5-182-adsl-pool.axelero.hu] has joined #xen
13:15 < MarkWilliamson> logdirty mode is needed for migration and was done first (by Ian)
13:15 < MarkWilliamson> then full shadow mode was added by Intel
13:15 < MarkWilliamson> now Michael Fetterman is reimplementing full shadow mode to work with or without VT
13:16 < movement> ah ok
13:17 < MarkWilliamson> there'll be an evaluating of the performance tradeoffs at some stage
13:17 < movement> one more, how far along towards SMP guests are you?
13:18 < MarkWilliamson> i guess it should ease porting but (depending on the performance vs ease of port tradeoff) you may still want fully paravirt
13:18 < MarkWilliamson> in the unstable tree SMP guests work, are generally stable but are not fully optimised
13:18 < movement> super.
13:19 < MarkWilliamson> SMP guests don't work under Xen/VT yet but it's on Intel's roadmap.
13:19 < MarkWilliamson> Intel have been seriously cool with all the work they're putting in (also on the IA64 port, the ACPI enhancements...)
13:21 < imka> MarkWilliamson, i started a domain with xm create ... -c and i get the saved domain
13:22 < MarkWilliamson> imka: ?
13:22 < MarkWilliamson> imka: but how much memory did you configure the domain with in the first place?
13:23 < imka> MarkWilliamson, 50
13:23 < MarkWilliamson> hrrrm.  this is a pretty weird error.
13:24 < MarkWilliamson> just as a sanity check, can you try configuring it with less memory (say 32meg) and doing the create / save / restore again?
13:26 < imka> tried with 30, and i get the same error
13:32 -!- soffi [~soffi@proxy.du.vdsl.is] has joined #xen
13:33 < MarkWilliamson> imka: hmmmm.  bizzarre.
13:38 < MarkWilliamson> imka: it'd be useful to know what release of Xen you're running - it should say somewhere towards the start of xm dmesg
13:38 -!- user1 [~user1@209.183.18.147] has joined #xen
13:39 < imka> MarkWilliamson, 2.0 suse build
13:40 < MarkWilliamson> imka: doesn't really help - i'd like the actual release that SuSE based their build on
13:41 < imka> it says "xen version 2.0"
13:42 < MarkWilliamson> somewhere it should say 2.0.5 or something similar
13:42 < MarkWilliamson> it's the third number i need
13:43 -!- user1 [~user1@209.183.18.147] has left #xen []
13:47 < imka> MarkWilliamson, 2.0.5c-4
13:47 < MarkWilliamson> imka: that's it :-)
13:48 < imka> a broken version ? :)
13:48 < MarkWilliamson> imka: could would be the reason
13:49 < MarkWilliamson> imka: might be worth posting to xen-users and asking if there are any migration / susp / resume fixes in the -testing tree.
13:49 < MarkWilliamson> I know they were hunting down some known bugs in 2.0.5 but I don't know the exact details.
13:50 < tab> is there some stuff in xfrd.log ?
13:50 < imka> ok i will. now another question. can i start a domain from an iso image?
13:50 < imka> tab do you mean me?
13:50 < tab> yes imka 
13:51 < imka> tab no error messages there
13:52 < tab> usually xfrd is verbose
13:53 < tab> what give you the error btw ?
13:54 < imka> tab i get "Error: 1" when i try to restore a domain. however, if i just start the domain with xm create ... -c again, i actually get a restored domain 
13:55 < tab> imka: how do you try to restore your domain ?
13:56 < imka> xm restore debian.xen
13:56 < tab> could you try directly with xfrd ?
13:57 < imka> how?
13:57 < tab> telnet localhost 8002
13:57 < tab> then you write:
13:57 < tab> (xfr.hello 1 0)
14:03 < imka> xfr.err 0
14:04 < tab> then: (xfr.migrate /path/to/debian.xen)
14:17 < imka> tab thanks for the help,but gotta go now. fortunately or not, i have a life :)
14:17 -!- imka [~imka@227.5-182-adsl-pool.axelero.hu] has quit [Quit: Leaving]
14:18 -!- sleon [test@e180021175.adsl.alicedsl.de] has quit [Read error: Operation timed out]
14:19 -!- monrad [~monrad@213083190130.sonofon.dk] has joined #xen
14:33 -!- sleon [test@e180002167.adsl.alicedsl.de] has joined #xen
14:34 < liberie> q
15:15 -!- MarkWilliamson [~MarkW@maw48.kings.cam.ac.uk] has left #xen [Kopete 0.10 : http://kopete.kde.org]
16:30 -!- sleon [test@e180002167.adsl.alicedsl.de] has quit [Quit: Leaving]
17:21 -!- DEac- [~deac@xdsl-213-196-202-187.netcologne.de] has quit [Ping timeout: 480 seconds]
17:28 -!- soffi [~soffi@proxy.du.vdsl.is] has quit [Quit: This computer has gone to sleep]
17:34 -!- DEac- [~deac@xdsl-84-44-147-240.netcologne.de] has joined #xen
18:19 -!- soffi [~soffi@proxy.du.vdsl.is] has joined #xen
18:31 -!- judge [~taras@S0106000795bd85bd.gv.shawcable.net] has left #xen []
18:47 -!- soffi [~soffi@proxy.du.vdsl.is] has quit [Quit: Leaving]
19:53 -!- Bluefox [~bluefox@pcp0012067827pcs.whtmrs01.md.comcast.net] has quit [Read error: Operation timed out]
20:24 -!- Bluefox [~bluefox@pcp0012067827pcs.whtmrs01.md.comcast.net] has joined #xen
22:03 -!- plars_ [~plars@bi01p1.co.us.ibm.com] has joined #xen
22:04 -!- plars [~plars@pixpat.austin.ibm.com] has quit [Read error: Operation timed out]
22:06 -!- plars__ [~plars@pixpat.austin.ibm.com] has joined #xen
22:09 -!- jonmason [~jonmason@pixpat.austin.ibm.com] has quit [Ping timeout: 480 seconds]
22:10 -!- plars_ [~plars@bi01p1.co.us.ibm.com] has quit [Read error: Connection reset by peer]
22:11 -!- jonmason [~jonmason@bi01p1.co.us.ibm.com] has joined #xen
22:11 -!- plars_ [~plars@bi01p1.co.us.ibm.com] has joined #xen
22:13 -!- plars__ [~plars@pixpat.austin.ibm.com] has quit [Read error: Operation timed out]
22:38 -!- plars__ [~plars@pixpat.austin.ibm.com] has joined #xen
22:40 -!- jonmason [~jonmason@bi01p1.co.us.ibm.com] has quit [Read error: Operation timed out]
22:40 -!- jonmason [~jonmason@pixpat.austin.ibm.com] has joined #xen
22:44 -!- plars_ [~plars@bi01p1.co.us.ibm.com] has quit [Read error: Operation timed out]
23:25 -!- plars__ [~plars@pixpat.austin.ibm.com] has quit [Read error: Connection reset by peer]
23:25 -!- jonmason [~jonmason@pixpat.austin.ibm.com] has quit [Read error: Connection reset by peer]
23:25 -!- jonmason [~jonmason@pixpat.austin.ibm.com] has joined #xen
23:25 -!- plars__ [~plars@pixpat.austin.ibm.com] has joined #xen
23:29 -!- vikasa [~vikasa@cpe-24-92-61-26.nycap.res.rr.com] has joined #xen
23:31 < vikasa> hi
23:32 < vikasa> hi anyone good in XEND code
23:33 -!- vikasa [~vikasa@cpe-24-92-61-26.nycap.res.rr.com] has quit [Quit: Leaving]
23:40 -!- vikasa [~vikasa@cpe-24-92-61-26.nycap.res.rr.com] has joined #xen
23:52 -!- vikasa [~vikasa@cpe-24-92-61-26.nycap.res.rr.com] has quit [Quit: Leaving]
23:57 -!- plars_ [~plars@bi01p1.co.us.ibm.com] has joined #xen
--- Log closed Sat May 07 23:59:00 2005