similar to: lhype on 2.6.20-rc2: Guest didn't handle trap 6 at c071b594 (cr2=00000000, err=0)

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

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:

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;

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 ->

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 ->

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

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, I''ve just finished my first attempt at making anything in ruby. It ended up beeing a module to facter, which collects facts about the number of domU''s and the memory, id and vcpu facts on all of the domU''s. It''s meant to be run on the dom0, and uses the xm utility to get the information. The only thing I haven''t figured out, is how to

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB

When exiting from an address space, no special hypervisor notification of page table updates needs to occur; direct page table hypervisors, such as Xen, switch to another address space first (init_mm) and unprotects the page tables to avoid the cost of trapping to the hypervisor for each pte_clear. Shadow mode hypervisors, such as VMI and lhype don't need to do the extra work of calling

When exiting from an address space, no special hypervisor notification of page table updates needs to occur; direct page table hypervisors, such as Xen, switch to another address space first (init_mm) and unprotects the page tables to avoid the cost of trapping to the hypervisor for each pte_clear. Shadow mode hypervisors, such as VMI and lhype don't need to do the extra work of calling

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, I am doing working on enabling Transcendent Memory(OLS '09) support on lguest. For the same, I need ballooning support for lguest. Is there an implmentation of Virtio Balloon driver, that I can use for my purpose? Could someone give me an insight, as to how to go about, for implementing this myself, incase I dont find this patch... Thankyou. -- Gaurav Kukreja +91 997 030 1257

Hi, I am doing working on enabling Transcendent Memory(OLS '09) support on lguest. For the same, I need ballooning support for lguest. Is there an implmentation of Virtio Balloon driver, that I can use for my purpose? Could someone give me an insight, as to how to go about, for implementing this myself, incase I dont find this patch... Thankyou. -- Gaurav Kukreja +91 997 030 1257