search for: rustyvisor

This is a formal announcement of Lguest64. Most are aware of the little puppies (lguest32, or simply lguest, or in some circles "rustyvisor"). But this time the puppies ate a bit too much. No more lean and mean puppies, now we got big fat lazy ones. Running on the hardware that's too lazy to do full virutalization. Yes, lguest now runs on x86_64! As you know, puppies are young, and so is lguest64. And like most new born pup...

This is a formal announcement of Lguest64. Most are aware of the little puppies (lguest32, or simply lguest, or in some circles "rustyvisor"). But this time the puppies ate a bit too much. No more lean and mean puppies, now we got big fat lazy ones. Running on the hardware that's too lazy to do full virutalization. Yes, lguest now runs on x86_64! As you know, puppies are young, and so is lguest64. And like most new born pup...

...-help--- + This is a very simple module which allows you to run + multiple instances of the same Linux kernel, using the + "lguest" command found in the Documentation/lguest directory. + Note that "lguest" is pronounced to rhyme with "fell quest", + not "rustyvisor". See Documentation/lguest/lguest.txt. + + If unsure, say N. If curious, say M. If masochistic, say Y. + +config LGUEST_GUEST + bool + help + The guest needs code built-in, even if the host has lguest + support as a module. The drivers are tiny, so we build them + in too. diff -puN...

Hi all, Ingo was eloquantly passionate about hating the name lhype, so after some debate (and importantly, the rejection of both "Wonkavisor" and "Rustyvisor"), I decided to name it after the guest (which is what users care about), not the hypervisor (which is what hackers care about). Hence: lhype_add -> lguest lguest.ko -> lg /dev/lhba -> /dev/lgba Thanks to everyone for the naming input! Rusty.

Hi all, Ingo was eloquantly passionate about hating the name lhype, so after some debate (and importantly, the rejection of both "Wonkavisor" and "Rustyvisor"), I decided to name it after the guest (which is what users care about), not the hypervisor (which is what hackers care about). Hence: lhype_add -> lguest lguest.ko -> lg /dev/lhba -> /dev/lgba Thanks to everyone for the naming input! Rusty.

...+ This is a very simple module called lg.ko which allows you to run + multiple instances of the Linux kernel, using the "lguest" command found in the Documentation/lguest directory. Note that "lguest" is pronounced to rhyme with "fell quest", not "rustyvisor". See Documentation/lguest/lguest.txt. + Usually you would also turn on "Lguest guest support", to create a + kernel which can also boot under lguest. + If unsure, say N. If curious, say M. If masochistic, say Y. - -config LGUEST_GUEST - bool - help - The guest needs c...

...+ This is a very simple module called lg.ko which allows you to run + multiple instances of the Linux kernel, using the "lguest" command found in the Documentation/lguest directory. Note that "lguest" is pronounced to rhyme with "fell quest", not "rustyvisor". See Documentation/lguest/lguest.txt. + Usually you would also turn on "Lguest guest support", to create a + kernel which can also boot under lguest. + If unsure, say N. If curious, say M. If masochistic, say Y. - -config LGUEST_GUEST - bool - help - The guest needs c...