similar to: lhype -> lguest

Hi everybody, Attracted by the puppies, I'm trying to run lhype. The patch applies cleanly to 2.6.20-rc2, my .config is in accord with lhype.txt, but when I try to launch an instance, I get this: $ sudo drivers/lhype/lhype_add 64m 0 vmlinux --tunnet=192.168.19.1 --block=linux.img root=/dev/lhba lhype_add: Failed to get DMA buffer from 0xb7fff008: No such file or directory lhype_add: network:

Hi everybody, Attracted by the puppies, I'm trying to run lhype. The patch applies cleanly to 2.6.20-rc2, my .config is in accord with lhype.txt, but when I try to launch an instance, I get this: $ sudo drivers/lhype/lhype_add 64m 0 vmlinux --tunnet=192.168.19.1 --block=linux.img root=/dev/lhba lhype_add: Failed to get DMA buffer from 0xb7fff008: No such file or directory lhype_add: network:

I am trying to experiment with lhype on a 32bit Intel box and when I launch a guest I get the following oops message: ----------- invalid opcode: 0000 [#1] Modules linked in: CPU: 0 EIP: 0061:[<c0101223>] Not tainted VLI EFLAGS: 00010246 (2.6.20-rc2 #1) EIP is at mwait_idle_with_hints+0x1e/0x3a eax: c03c8008 ebx: 00000000 ecx: 00000000 edx: 00000000 esi: 00000000 edi:

I am trying to experiment with lhype on a 32bit Intel box and when I launch a guest I get the following oops message: ----------- invalid opcode: 0000 [#1] Modules linked in: CPU: 0 EIP: 0061:[<c0101223>] Not tainted VLI EFLAGS: 00010246 (2.6.20-rc2 #1) EIP is at mwait_idle_with_hints+0x1e/0x3a eax: c03c8008 ebx: 00000000 ecx: 00000000 edx: 00000000 esi: 00000000 edi:

Hi! Bored by previous lhype success, I tried to boot a debootstrapped debian over nfsroot, and lo, this almost works! Commandline: # drivers/lhype/lhype_add 256m 0 ./vmlinux --tunnet=192.168.1.20 root=/dev/root nfsroot=/home/ahu/lhype-root ip=192.168.1.21:192.168.1.20:192.168.1.20 This with lhype.patch current as of this message and 2.9.20-rc4. The boot process stops after: Starting periodic

Hi! Bored by previous lhype success, I tried to boot a debootstrapped debian over nfsroot, and lo, this almost works! Commandline: # drivers/lhype/lhype_add 256m 0 ./vmlinux --tunnet=192.168.1.20 root=/dev/root nfsroot=/home/ahu/lhype-root ip=192.168.1.21:192.168.1.20:192.168.1.20 This with lhype.patch current as of this message and 2.9.20-rc4. The boot process stops after: Starting periodic

This patch allows lhype_add to open disk image files larger than 2GB. Please apply. Signed-off-by: James Morris <jmorris@redhat.com> --- diff -r 82d084b15417 drivers/lhype/lhype_add.c --- a/drivers/lhype/lhype_add.c Wed Nov 15 00:58:18 2006 -0500 +++ b/drivers/lhype/lhype_add.c Wed Nov 15 01:01:35 2006 -0500 @@ -329,7 +329,7 @@ static int set_up_block_device(const cha struct stat st;

This patch allows lhype_add to open disk image files larger than 2GB. Please apply. Signed-off-by: James Morris <jmorris@redhat.com> --- diff -r 82d084b15417 drivers/lhype/lhype_add.c --- a/drivers/lhype/lhype_add.c Wed Nov 15 00:58:18 2006 -0500 +++ b/drivers/lhype/lhype_add.c Wed Nov 15 01:01:35 2006 -0500 @@ -329,7 +329,7 @@ static int set_up_block_device(const cha struct stat st;

I get a compilation error with an undefined reference to PKMAP_BASE (on a fairly standard x86 box). This patch include asm/highmem.h, where the macro is defined. Please apply. Signed-off-by: James Morris <jmorris@redhat.com> --- diff -r 2f39210c8792 drivers/lhype/init.c --- a/drivers/lhype/init.c Mon Nov 13 17:16:49 2006 -0500 +++ b/drivers/lhype/init.c Mon Nov 13 17:23:38 2006 -0500 @@

I get a compilation error with an undefined reference to PKMAP_BASE (on a fairly standard x86 box). This patch include asm/highmem.h, where the macro is defined. Please apply. Signed-off-by: James Morris <jmorris@redhat.com> --- diff -r 2f39210c8792 drivers/lhype/init.c --- a/drivers/lhype/init.c Mon Nov 13 17:16:49 2006 -0500 +++ b/drivers/lhype/init.c Mon Nov 13 17:23:38 2006 -0500 @@

Hi all, Some of you know I've been working on a trivial in-kernel hypervisor to demonstrate paravirt_ops. The good news is that it works! (And not just for me!) The bad news is that I haven't written any documentation and now I'm going to be offline (moving to a farm) for several weeks. Nonetheless, if you're the kind of person who wants to poke around with hypervisors, no

Hi all, Some of you know I've been working on a trivial in-kernel hypervisor to demonstrate paravirt_ops. The good news is that it works! (And not just for me!) The bad news is that I haven't written any documentation and now I'm going to be offline (moving to a farm) for several weeks. Nonetheless, if you're the kind of person who wants to poke around with hypervisors, no

From: Rusty Russell <rusty@rustcorp.com.au> This is the Kconfig and Makefile to allow lguest to actually be compiled. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> --- drivers/Kconfig | 2 ++ drivers/Makefile | 1 + drivers/lguest/Kconfig | 20

Hi ! Kenrel 2.6.21 (kernel.org) Patch lguest-2.6.21-254.patch Distro Slackware 11.0 GCC 3.4.6 GLIBC 2.3.6 HW model name : AMD Duron(tm) procu{s{ Module Size Used by tun 7680 0 lg 54600 0 just started playing with lguest - patching, compiling and booting the host-kernel goes ok - compiling lguest is ok as well after

Hi ! Kenrel 2.6.21 (kernel.org) Patch lguest-2.6.21-254.patch Distro Slackware 11.0 GCC 3.4.6 GLIBC 2.3.6 HW model name : AMD Duron(tm) procu{s{ Module Size Used by tun 7680 0 lg 54600 0 just started playing with lguest - patching, compiling and booting the host-kernel goes ok - compiling lguest is ok as well after

Hi all, Lguest is a simple hypervisor which runs Linux under Linux, without needing VT hardware. Two people asked if I had a version of lguest which worked on other-than-bleeding-edge-mm kernels, so I did a backport of the latest version to 2.6.21. 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

Hi all, Lguest is a simple hypervisor which runs Linux under Linux, without needing VT hardware. Two people asked if I had a version of lguest which worked on other-than-bleeding-edge-mm kernels, so I did a backport of the latest version to 2.6.21. 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

From: Rusty Russell <rusty@rustcorp.com.au> A brief document describing how to use lguest. Because lguest doesn't have an ABI we also include an example launcher in the Documentation directory. [jmorris@namei.org: Fix up nat example in documentation] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Signed-off-by: James Morris

From: Rusty Russell <rusty@rustcorp.com.au> A brief document describing how to use lguest. Because lguest doesn't have an ABI we also include an example launcher in the Documentation directory. [jmorris@namei.org: Fix up nat example in documentation] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Cc: Andi Kleen <ak@suse.de> Signed-off-by: James Morris

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,