Rusty Russell wrote:
On Mon, 29 Jun 2009 03:36:30 am Brian Jackson wrote:Nevermind the above. I figured out I didn't have LGUEST_GUEST turned on for some reason. I'm sure I turned it on when I turned on LGUEST, but I'm just a meat bag. Might be a nice thing to add to the FAQ...The problem is that trap 13 tends to be what happens when a guest does something bad early on. We could offer a hint if there was no LHCALL_INIT call but it would only be a guess...I also tried inside a non-paravirt 32bit kvm instance and got: lguest: unhandled trap 13 at 0xc100af77 (0xd8) Anybody got any ideas to test out?If this is a correctly-configured kernel, please send your .config...
I think it is. At least I went back and checked the docs and checked what it said this time.
The interesting bits: egrep '(LGUEST|PARAVIRT|HIGHMEM|ALIGN|PAE)' /usr/src/linux/.config CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_PARAVIRT_GUEST=y CONFIG_LGUEST_GUEST=y CONFIG_PARAVIRT=y CONFIG_PARAVIRT_SPINLOCKS=y # CONFIG_PARAVIRT_CLOCK is not set # CONFIG_PARAVIRT_DEBUG is not set # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_HIGHMEM=y CONFIG_PHYSICAL_ALIGN=0x100000 # CONFIG_DEBUG_HIGHMEM is not setfull config is gzip'ed and attached since I wasn't sure it would get to the list otherwise.
--Brian Jackson
Thanks! Rusty.
lguest-config.gz
Description: application/gzip
_______________________________________________ Lguest mailing list [email protected] https://ozlabs.org/mailman/listinfo/lguest
