| --- | Log | opened Sat May 03 00:00:09 2008 |
| 00:24 | <Shaun:#xen> | what happened to `make mkpatches`? |
| 00:26 | -!- | _avi_ [~avi@77.126.14.159] has quit [Read error: Connection timed out] |
| 00:28 | -!- | _avi_ [~avi@77.126.14.159] has joined #xen |
| 00:30 | -!- | Caleb [~caleb@12-214-1-103.client.mchsi.com] has joined #xen |
| 01:45 | -!- | jm [~fake@c-76-113-194-7.hsd1.mn.comcast.net] has quit [] |
| 02:04 | -!- | Caleb [~caleb@12-214-1-103.client.mchsi.com] has quit [Quit: Leaving] |
| 04:31 | -!- | osmosis [~steven@cpe-76-90-81-133.socal.res.rr.com] has quit [Quit: Ex-Chat] |
| 05:17 | <tessier_:#xen> | Anyone know how much memory xen itself uses? My calculations show it to need 62M on my system. Could that be right? Sounds rather large. |
| 05:18 | <tessier_:#xen> | Wow. http://docs.xensource.com/XenServer/4.0.1/installation/apd.html says it uses 128M. |
| 05:36 | <tessier_:#xen> | http://en.wikipedia.org/w/index.php?title=Comparison_of_file_systems&oldid=209063556#Features |
| 05:36 | <tessier_:#xen> | WOW. That's just wrong. |
| 05:36 | <tessier_:#xen> | Check out the last "feature" of reisersf. |
| 05:49 | -!- | geoff_k [~geoff_k__@209.116.gr5.adsl.brightview.com] has joined #xen |
| 06:12 | -!- | visik7 [~dksakd@host155-47-dynamic.13-79-r.retail.telecomitalia.it] has joined #xen |
| 08:52 | -!- | babbage [~james@89.100.186.117] has joined #xen |
| 09:20 | <babbage:#xen> | What are the Xen kernels on Debian lenny called? I read a bit about the *-xen kernels and what I read seemed to indicate that you can now use the same kernel for dom0 and domU. Is this the case? |
| 09:25 | <geoff_k:#xen> | babbage, i;ve not looked at lenny with xen but you can use same kernels for dom0 and domU and always have for as long as ive used it |
| 09:32 | <murb:#xen> | geoff_k: you can't. |
| 09:33 | <murb:#xen> | as the xen kernels in lenny are using the upstream paravirt stuff |
| 09:33 | <murb:#xen> | which doesn't have dom0 support. |
| 09:33 | <murb:#xen> | (yet) |
| 09:33 | <geoff_k:#xen> | oh i see specificaly in lenny i thought he meant generaly |
| 09:34 | <geoff_k:#xen> | like can lenny do it because older version didn't |
| 09:39 | <babbage:#xen> | murb, OK, thanks. I understand what you said, but what should I do about it? |
| 09:40 | <babbage:#xen> | (FWIW, I am using AMD64) |
| 09:44 | <murb:#xen> | babbage: oh then you don't even have domU support quite yet. |
| 09:44 | <murb:#xen> | in 64b |
| 09:47 | <babbage:#xen> | I'm happy to run 32-bit domUs. |
| 09:49 | <babbage:#xen> | I only upgraded to a 64-bit machine to get >1GB RAM (my old motherboard only supported ECC for >1GB, which made upgrading its RAM expensive) |
| 09:50 | -!- | jm [~fake@c-76-113-194-7.hsd1.mn.comcast.net] has joined #xen |
| 09:50 | -!- | jm [~fake@c-76-113-194-7.hsd1.mn.comcast.net] has quit [] |
| 09:50 | -!- | geoff_k [~geoff_k__@209.116.gr5.adsl.brightview.com] has quit [Quit: Quit] |
| 09:50 | -!- | jm [~fake@c-76-113-194-7.hsd1.mn.comcast.net] has joined #xen |
| 09:59 | <babbage:#xen> | murb, I suspect there is domU support: /boot/vmlinuz-2.6.22-3-vserver-amd64 exists (it belongs to the Debian package linux-image-2.6.22-3-vserver-amd64) |
| 09:59 | <babbage:#xen> | bbl |
| 10:00 | -!- | babbage [~james@89.100.186.117] has quit [Quit: Leaving] |
| 10:43 | -!- | babbage [~james@89.100.186.117] has joined #xen |
| 10:43 | <babbage:#xen> | OK, so I got the hypervisor to boot. But the hypervisor says "not an ELF binary" when it tries to invoke the kernel. |
| 10:54 | -!- | Infinito [~argos@201-10-139-186.gnace701.dsl.brasiltelecom.net.br] has joined #xen |
| 11:03 | -!- | babbage [~james@89.100.186.117] has quit [Quit: Leaving] |
| 11:45 | -!- | Infinito [~argos@201-10-139-186.gnace701.dsl.brasiltelecom.net.br] has quit [Remote host closed the connection] |
| 12:10 | -!- | movement [~moz@82-69-60-206.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 480 seconds] |
| 12:19 | -!- | movement [~moz@82-69-60-206.dsl.in-addr.zen.co.uk] has joined #xen |
| 12:20 | -!- | babbage [~james@89.100.186.117] has joined #xen |
| 12:38 | <babbage:#xen> | Does anybody know if there are any issues with getting the Xen 2.6.18 kernel working on Lenny? |
| 12:57 | -!- | movement [~moz@82-69-60-206.dsl.in-addr.zen.co.uk] has quit [Read error: Connection reset by peer] |
| 13:10 | -!- | movement [~moz@82-69-60-206.dsl.in-addr.zen.co.uk] has joined #xen |
| 14:13 | -!- | babbage [~james@89.100.186.117] has quit [Quit: Leaving] |
| 14:14 | -!- | Infinito [~argos@201-10-139-186.gnace701.dsl.brasiltelecom.net.br] has joined #xen |
| 14:47 | <icarus901:#xen> | tessier_, that estimate is just about right |
| 14:47 | <icarus901:#xen> | for 32bit its less |
| 14:48 | -!- | visik7 [~dksakd@host155-47-dynamic.13-79-r.retail.telecomitalia.it] has quit [Remote host closed the connection] |
| 15:12 | -!- | _avi_ [~avi@77.126.14.159] has quit [Remote host closed the connection] |
| 15:13 | -!- | avi_ [~avi@77.126.14.159] has joined #xen |
| 15:40 | -!- | avi_ [~avi@77.126.14.159] has quit [Remote host closed the connection] |
| 15:42 | -!- | avi_ [~avi@77.127.108.81] has joined #xen |
| 15:45 | -!- | babbage [~james@89.100.186.117] has joined #xen |
| 15:46 | <babbage:#xen> | When I boot my system, the hyperviser starts fine, and then gets as far as handing over the VGA console to the dom0 kernel, but nothing happens for a few seconds and then the machine reboots? What's happening? How can I get better diagnostics about what is going on? |
| 15:59 | -!- | ultratotor [~uranus@lns-bzn-50f-81-56-199-214.adsl.proxad.net] has joined #xen |
| 16:00 | <ultratotor:#xen> | hello |
| 16:12 | <icblenke:#xen> | ultratotor: try adding "noreboot" to your hypervisor commandline on boot. |
| 16:18 | <babbage:#xen> | icblenke, I assume you were talking to me. No difference. The last message is still that the hypervisor is handing over the VGA console. |
| 16:22 | <ultratotor:#xen> | icblenke i have a xp virtualisation probleme, p2v |
| 16:23 | <ultratotor:#xen> | and i search a perfect dd cmd for hard drive to img |
| 16:23 | <ultratotor:#xen> | adding noreboot for my hypervisor can help me ? |
| 16:24 | <icblenke:#xen> | that was menat for babbage. |
| 16:25 | <ultratotor:#xen> | ok |
| 16:33 | -!- | fuzzy [~fuzzy@c-67-171-182-99.hsd1.or.comcast.net] has joined #xen |
| 16:50 | -!- | fuzzy [~fuzzy@c-67-171-182-99.hsd1.or.comcast.net] has quit [Quit: fuzzy] |
| 16:52 | -!- | fuzzy [~fuzzy@c-67-171-182-99.hsd1.or.comcast.net] has joined #xen |
| 18:11 | -!- | mebe [~mebe@helheim.shinsen-subs.org] has joined #xen |
| 18:14 | <mebe:#xen> | hi |
| 18:14 | <babbage:#xen> | hi |
| 18:14 | <mebe:#xen> | one of my domUs suddenly stopped responding to console |
| 18:14 | <mebe:#xen> | i tried hitting ctrl-q in case i had accidentally hit ctrl-s, but that didn't help |
| 18:15 | <mebe:#xen> | everything that's still running on it responds fine and other domU consoles open fine |
| 18:15 | <mebe:#xen> | any tips? |
| 18:15 | <babbage:#xen> | I'm a noob. Unlikely to be able to help, sorry. |
| 18:15 | <mebe:#xen> | ok, no problem :) |
| 18:15 | <babbage:#xen> | ScrollLock? |
| 18:18 | <mebe:#xen> | nope, doesn't seem to be it |
| 18:18 | <mebe:#xen> | thanks for the offer, though |
| 18:40 | -!- | ultratotor [~uranus@lns-bzn-50f-81-56-199-214.adsl.proxad.net] has quit [Quit: leaving] |
| 18:50 | -!- | Infinito [~argos@201-10-139-186.gnace701.dsl.brasiltelecom.net.br] has quit [Quit: Leaving] |
| 20:53 | -!- | Infinito [~argos@201-10-139-186.gnace701.dsl.brasiltelecom.net.br] has joined #xen |
| 21:08 | -!- | Infinito [~argos@201-10-139-186.gnace701.dsl.brasiltelecom.net.br] has quit [Quit: Leaving] |
| 21:31 | -!- | Wordy [~moi@c-75-71-123-67.hsd1.co.comcast.net] has left #xen [bye] |
| 21:34 | -!- | fuzzy_ [~fuzzy@c-67-171-182-99.hsd1.or.comcast.net] has joined #xen |
| 21:34 | -!- | fuzzy [~fuzzy@c-67-171-182-99.hsd1.or.comcast.net] has quit [Read error: Connection reset by peer] |
| 21:36 | -!- | fuzzy [~fuzzy@c-67-171-182-99.hsd1.or.comcast.net] has joined #xen |
| 21:36 | -!- | fuzzy_ [~fuzzy@c-67-171-182-99.hsd1.or.comcast.net] has quit [Read error: Connection reset by peer] |
| 21:44 | -!- | fuzzy [~fuzzy@c-67-171-182-99.hsd1.or.comcast.net] has quit [Ping timeout: 480 seconds] |
| 22:55 | <tessier_:#xen> | icarus901: Thanks for the confirmation. What on earth does xen do with 62M of RAM? I am told that Vmware ESX server needs only 32M. And even that sounds like a lot. I thought a hypervisor was a very thin layer of software. |
| 23:59 | -!- | VS_ChanLog [~stats@ns.theshore.net] has left #xen [Rotating Logs] |
| 23:59 | -!- | VS_ChanLog [~stats@ns.theshore.net] has joined #xen |
| --- | Log | closed Sun May 04 00:00:47 2008 |
