similar to: lhype progress...

Displaying 20 results from an estimated 10000 matches similar to: "lhype progress..."

2007 Apr 18
2
lhype on 2.6.20-rc2: Guest didn't handle trap 6 at c071b594 (cr2=00000000, err=0)
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:
2007 Apr 18
2
lhype on 2.6.20-rc2: Guest didn't handle trap 6 at c071b594 (cr2=00000000, err=0)
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:
2007 Apr 18
0
[PATCH] lhype: compilation fix for PKMAP_BASE reference
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 @@
2007 Apr 18
0
[PATCH] lhype: compilation fix for PKMAP_BASE reference
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 @@
2007 Apr 18
0
[PATCH] lhype: Add LFS support to lhype_add for disk images
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;
2007 Apr 18
0
[PATCH] lhype: Add LFS support to lhype_add for disk images
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;
2007 Apr 18
2
APIC clock setup dependent on PAE ?
Why are these APIC clock init hooks dependent on CONFIG_X86_PAE ? include/asm/paravirt.h: static inline void setup_boot_clock(void) { paravirt_ops.setup_boot_clock(); } static inline void setup_secondary_clock(void) { paravirt_ops.setup_secondary_clock(); } (via the vmi timer patch). - James -- James Morris <jmorris@namei.org>
2007 Apr 18
2
APIC clock setup dependent on PAE ?
Why are these APIC clock init hooks dependent on CONFIG_X86_PAE ? include/asm/paravirt.h: static inline void setup_boot_clock(void) { paravirt_ops.setup_boot_clock(); } static inline void setup_secondary_clock(void) { paravirt_ops.setup_secondary_clock(); } (via the vmi timer patch). - James -- James Morris <jmorris@namei.org>
2007 Apr 18
1
lhype guest oops
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:
2007 Apr 18
1
lhype guest oops
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:
2007 Apr 18
3
lhype booting debootstrapped debian image over nfsroot, partial success
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
2007 Apr 18
3
lhype booting debootstrapped debian image over nfsroot, partial success
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
2007 Apr 18
1
[PATCH] paravirt build fix
Currently, 020-paravirt-xen.patch contains inconsistent declarations for a bunch of native_read/write functions. This patch updates the declarations to use unsigned long for register values. Signed-off-by: James Morris <jmorris@redhat.com> --- include/asm-i386/paravirt.h | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff -purN -X dontdiff
2007 Apr 18
1
[PATCH] paravirt build fix
Currently, 020-paravirt-xen.patch contains inconsistent declarations for a bunch of native_read/write functions. This patch updates the declarations to use unsigned long for register values. Signed-off-by: James Morris <jmorris@redhat.com> --- include/asm-i386/paravirt.h | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-) diff -purN -X dontdiff
1999 Sep 14
2
DBase File locking issues
Hi All, I am experiencing issues with the use of DBase files on a Samba 2.0.5a share, that appear to be due to locking problems. Basically, I have test programs for both DOS and Win32 that does nothing but append records to a DBase database (DBF/MDX files). If more than one client PC is appending to this file, data loss occurs. I get random data loss, with records lost, and index file
1998 Mar 25
1
R-beta: S Mailing List
I know that the S Mailing list recently moved but am not sure where. I recently moved and would like to resubscribe to the S Mailing list. Could someone send me the latest info on subscribing? Thanks! Jeff jmorris at cldx.com -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send
1998 Mar 25
1
R-beta: S Mailing List
I know that the S Mailing list recently moved but am not sure where. I recently moved and would like to resubscribe to the S Mailing list. Could someone send me the latest info on subscribing? Thanks! Jeff jmorris at cldx.com -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send
2007 May 08
1
[PATCH] lguest: two net bugfixes
1) Bridging via host is broken: we need to set "promisc" bit in MAC address published by the host so the guest sends us everything. Thanks James Morris for the report (I don't use bridging). 2) Lguest network device uses 0 to mean "noone at this slot". It used to use 0xFF, and one spot was missed. Minor: it just means we'll have a useless extra transmit
2007 May 08
1
[PATCH] lguest: two net bugfixes
1) Bridging via host is broken: we need to set "promisc" bit in MAC address published by the host so the guest sends us everything. Thanks James Morris for the report (I don't use bridging). 2) Lguest network device uses 0 to mean "noone at this slot". It used to use 0xFF, and one spot was missed. Minor: it just means we'll have a useless extra transmit
2007 Apr 26
1
[PATCH] Fix lguest oops when guest dies while receiving I/O
lguest needs to hold a reference to its task in case it exits while another Guest is sending it I/O. Otherwise we can oops in access_process_vm->get_task_mm->task_lock(). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> --- drivers/lguest/lguest_user.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) ===================================================================