[root@xenbox ~]# vm-build.linux 1 los0-image "xxx" ... [root@xenbox ~]# vm-pause -u 1 (XEN) Domain 1 (vcpu#0) crashed on cpu#0: (XEN) CPU: 0 (XEN) EIP: e019:[] (XEN) EFLAGS: 00000202 CONTEXT: guest (XEN) eax: 00000000 ebx: 00000000 ecx: 00000000 edx: 00000000 (XEN) esi: 001e1000 edi: 00000000 ebp: 001e3ffc esp: 001e3fe8 (XEN) cr0: 8005003b cr3: 09383000 (XEN) ds: e021 es: e021 fs: e021 gs: e021 ss: e021 cs: e019 (XEN) Guest stack trace from esp=001e3fe8: (XEN) 00000000 001002dc 0001e019 00000202 001e1000 00000000
This may not look like much, but it means that Xen is
loading a movitz
image and launching into it. Score!
Muli Ben-Yehuda's journal 
How much work does porting Movitz to Xen actually involve? And more importantly, does that question even make sense?
I know next to nothing about VMMs.
Comment by yrk — June 27, 2005 @ 1:00 PM |
> How much work does porting Movitz to Xen actually involve? And more
> importantly, does that question even make sense?
Ask me when I’m done, and yes 🙂
> I know next to nothing about VMMs.
I just got a great book…
Comment by mulix — June 27, 2005 @ 1:06 PM |
That sounds kinky.
But, to me, anything involving Xen is kinky.
Comment by the_p0pe — June 27, 2005 @ 1:09 PM |
kinkiness is the future.
Comment by mulix — June 27, 2005 @ 1:17 PM |
Porting is too troublesome 🙂
I’ll try this Movitz stuff on qemu.
— bi (http://mncw.tk/)
Comment by Anonymous — June 27, 2005 @ 1:11 PM |
Re: Porting is too troublesome 🙂
it works on qemu… someone got emacs to run in it a couple of weeks ago.
Comment by mulix — June 27, 2005 @ 1:18 PM |
Re: Porting is too troublesome 🙂
Ugh, there goes my evil plans for wasting time… 😦 🙂
— bi
Comment by Anonymous — June 27, 2005 @ 6:49 PM