On Thu, 2007-04-05 at 12:59 +1000, Rusty Russell wrote: > On Wed, 2007-04-04 at 15:07 -0400, Steven Rostedt wrote: > Yeah, I haven't tried loading random modules but I can imagine this does > happen (what module was it, BTW?) I have no idea of which module it crashed on. I didn't investigate that too much. I could simply send a trap to guest when __pa(addr) != lguest_find_guest_paddr(addr) and see which module it crashed on. My block device I used was basically a copy of a RHEL5 system. I only modified the inittab and fstab to get it working. So on startup and doing the udev init was when it crashed. > > I used to have a function just like this, but managed to get rid of > it. > > Hmm, perhaps we should have an "int lgread_virt_byte(u8 *)" which does > the pgtable walk and read all in one? It won't be efficient, but it'll > be more correct and maybe even fewer lines 8) I forgot that you have a goal to keep lguest small :) Perhaps we can fork, and have lguest and lguest-lite. -- Steve _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
