On Fri, May 04, 2007 at 10:43:09AM +1000, Rusty Russell wrote: > On Fri, 2007-05-04 at 10:13 +1000, Rusty Russell wrote: > > On Thu, 2007-05-03 at 11:02 -0500, Matt Mackall wrote: > > > On Thu, May 03, 2007 at 12:43:48AM +1000, Rusty Russell wrote: > > > > http://lguest.ozlabs.org/lguest-2.6.21-254.patch.gz > > > > > > > > See Documentation/lguest/lguest.txt for how to run, > > > > drivers/lguest/README for the draft code documentation journey. > > > > > > Your lguest readme is quite lacking in the area of how to configure a > > > guest kernel as opposed to the host kernel. More hand-holding, please. > > > > Hi Matt! > > > > Ah, that's because they are the same kernel. Turning on CONFIG_LGUEST > > builds-in the parts needed to be a guest as well. Ok, I thought that might be a possibility. > -- You will need to configure your kernel with the following options: > +- Lguest runs the same kernel as guest and host. You can configure > + them differently, but usually it's easiest not to. I take it both sides of the virtual device drivers are turned on by the lguest option? For the purposes of kernel hacking, I'd want to boot into one build and repeatedly launch another build as a guest, thereby getting faster hack/build/test cycles than either qemu or full reboot. How tightly coupled are things here? -- Mathematics is the supreme nostalgia of our time. _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
