Back to Home / #uml / 2007 / 12 / Prev Day | Next Day
#uml IRC Logs for 2007-12-09

---Logopened Sun Dec 09 00:00:21 2007
00:04|-|tchan [] has quit [Quit: WeeChat 0.2.7-dev]
00:14|-|tchan [] has joined #uml
00:22|-|tchan [] has quit [Quit: WeeChat 0.2.7-dev]
00:57|-|flatronf700B [] has joined #uml
01:13|-|tchan [] has joined #uml
05:19|-|tyler29 [] has joined #uml
07:35|-|tyler29 [] has quit [Quit: ++]
09:21|-|Infinito [] has joined #uml
09:21|-|krau [~cktakahas@] has joined #uml
09:26|-|IntuitiveNipple [~TJ@] has joined #uml
09:39|-|balbir [~balbir@] has quit [Ping timeout: 480 seconds]
09:53|-|Magotari_ [] has quit [Quit: Lost terminal]
10:02|-|Infinito [] has quit [Quit: Quitte]
10:04|-|krau [~cktakahas@] has quit [Quit: Varei!!!]
10:56|-|kos_tom [] has joined #uml
11:07|-|Blissex [] has joined #uml
13:07|-|namit [] has joined #uml
13:09<namit-#uml->>I am just wondering how does UML deal with memory allocation? could anyone point me in some direction to some documentation about it?
13:13|-|Blissex [] has quit [Remote host closed the connection]
13:18|-|krau [~cktakahas@] has joined #uml
13:25<namit-#uml->>like if I run a fork bomb in my uml instance what happens to the server?
13:29<IntuitiveNipple-#uml->>It panics :)
13:32<namit-#uml->>IntuitiveNipple: how badly? and is there a way of stopping it from doing that?
13:33<namit-#uml->>suppose could use some resource manager.
13:41<caker-#uml->>the UML server would lockup/panic, but the host should not
13:41<caker-#uml->>worst case is it'll spin CPU
13:53|-|jjkola [] has joined #uml
14:10|-|Urgleflogue [~plamen@] has quit [Quit: 01001110 01100101 01110010 01100100 00100001]
14:12|-|Urgleflogue [~plamen@] has joined #uml
14:13|-|namit [] has quit [Ping timeout: 480 seconds]
14:48|-|Infinito [] has joined #uml
14:54|-|IntuitiveNipple [~TJ@] has quit [Ping timeout: 480 seconds]
15:11|-|IntuitiveNipple [] has joined #uml
15:12|-|jjkola [] has quit [Quit: *pop*]
15:13|-|cl4sh [] has joined #uml
15:14|-|cl4sh [] has quit []
15:28|-|tchan [] has quit [Quit: WeeChat 0.2.7-dev]
15:34|-|tchan [] has joined #uml
15:34|-|Micksa [~mslade@] has joined #uml
15:35<Micksa-#uml->>okay, so
15:35<Micksa-#uml->>I have an amd64 machine that's running x86 linux and i want to run an amd64 uml on it
15:35<Micksa-#uml->>(1) is it possible? and (2) am I going to have to cross-compile a uml kernel to make it happen?
15:42<Micksa-#uml->>oh, I can run an amd64 host kernel
15:43<Micksa-#uml->>IIRC an amd64 kernel will run x86 binaries and everything will work the same
15:46<IntuitiveNipple-#uml->>What host kernel version?
15:46<Micksa-#uml->>erm, whatever I can get going for dapper I guess
15:47<Micksa-#uml->>I vaguely remember running an x86 OS using an amd64 kernel a while ago
15:47<IntuitiveNipple-#uml->>older then. You may have problems, there seem to be some random issues with 32-bit on 64-bit related to SKAS0 but they've not been pinpointed yet
15:47<Micksa-#uml->>32-bit guest you mean? or 64-bit guest running 32-bit apps?
15:47<IntuitiveNipple-#uml->>I'm seeing issues with Gutsy, and a guy at Oracle is seeing issues with 2.6.18
15:48<IntuitiveNipple-#uml->>Yes, 64-bit host running 32-bit guest
15:48<Micksa-#uml->>well what I want is effectively a 64-bit guest and host
15:48<IntuitiveNipple-#uml->>Something seems to have changed after 2.6.9 that causes it but we've not yet pinned it down
15:48<IntuitiveNipple-#uml->>64-bit on 64-bit is fine
15:49<IntuitiveNipple-#uml->>I *think* 64-bit on 32-bit is possible, but I'm not sure which kernel version you need for that :)
15:50<Micksa-#uml->>that sounds too adventurous now that I think of it
15:52|-|tchan [] has quit [Quit: WeeChat 0.2.7-dev]
15:59|-|tchan [] has joined #uml
16:24|-|tchan [] has quit [Quit: WeeChat 0.2.7-dev]
16:29|-|tchan [] has joined #uml
16:33|-|tchan [] has quit []
16:45|-|karol [] has joined #uml
16:45|-|karol changed nick to Magotari
16:45<Magotari-#uml->>That skas3 patch is pretty nice.
16:58|-|tchan [] has joined #uml
17:15|-|Infinito [] has quit [Quit: Quitte]
17:27|-|kos_tom [] has quit [Quit: I like core dumps]
17:55|-|tchan [] has quit [Quit: WeeChat 0.2.7-dev]
18:22|-|tchan [] has joined #uml
18:25|-|weasel [] has joined #uml
18:27|-|Micksa [~mslade@] has quit [Ping timeout: 480 seconds]
18:30|-|krau [~cktakahas@] has quit [Quit: Varei!!!]
18:37|-|Micksa [~mslade@] has joined #uml
20:14|-|Infinito [] has joined #uml
20:33|-|ferret_0567 [~travis@] has quit [Quit: leaving]
20:47|-|ferret_0567 [~travis@] has joined #uml
20:47|-|ferret_0567 [~travis@] has quit []
20:48|-|ferret_0567 [~travis@] has joined #uml
20:49|-|ferret_0567 [~travis@] has quit []
20:49|-|ferret_0567 [] has joined #uml
20:50|-|ferret_0567 [] has quit []
20:57|-|namit [] has joined #uml
20:59|-|jcpiza [~jcpiza@] has left #uml [Leaving]
21:03|-|ferret_0567 [] has joined #uml
21:03|-|ferret_0567 [] has quit []
21:04|-|ferret_0567 [] has joined #uml
21:04|-|ferret_0567 [] has quit []
21:04|-|ferret_0567 [~travis@] has joined #uml
21:05|-|ferret_0567 [~travis@] has quit []
21:10|-|namit [] has quit [Ping timeout: 480 seconds]
21:43|-|Infinito [] has quit [Quit: Quitte]
22:02|-|IntuitiveNipple [] has quit [Quit: The only intuitive interface is the nipple; everything else is learned]
22:19|-|ferret_0567 [] has joined #uml
22:34<dang-#uml->>And here I'm on 2.6.24-pre...
23:59|-|VS_ChanLog [] has left #uml [Rotating Logs]
23:59|-|VS_ChanLog [] has joined #uml
---Logclosed Mon Dec 10 00:00:57 2007