I'm getting the following crash with current -git userspace. I'm
running a stock 2.6.22-14-generic ubuntu kernels with modules from the
kvm-userspace tree. I believe my BIOS images are also from current
-git.
The crash occurs about 10 or 15 seconds after the GUI comes up.
Booting with
On Thu, 2008-03-27 at 11:36 +0200, Avi Kivity wrote:
I dug out my i386 install and tried it. Doesn't reproduce for me on
either kvm.git or -rc7.
Do you have a working setup that we can bisect?
I don't really have a working revision to bisect against. I'm not sure
that it ever worked.
On Thu, 2008-03-27 at 17:53 +0200, Avi Kivity wrote:
Dave Hansen wrote:
On Thu, 2008-03-27 at 11:36 +0200, Avi Kivity wrote:
I dug out my i386 install and tried it. Doesn't reproduce for me on
either kvm.git or -rc7.
Do you have a working setup that we can bisect?
I
On Thu, 2008-03-27 at 16:59 +0200, Avi Kivity wrote:
Dave Hansen wrote:
On Thu, 2008-03-27 at 12:10 +0200, Avi Kivity wrote:
btw, is this with = 4GB RAM on the host?
Well, are you asking whether I have PAE on or not? :)
No, I'm asking whether there is a possibility of address
On Wed, 2008-03-26 at 18:58 +0200, Avi Kivity wrote:
Dave Hansen wrote:
On Wed, 2008-03-26 at 11:50 +0200, Avi Kivity wrote:
Dave Hansen wrote:
I was getting some kvm userspace crashes trying to run a Windows guest.
So, I decided to try a recent kernel (2.6.25-rc6-00333-ga4083c9
On Wed, 2008-03-26 at 11:50 +0200, Avi Kivity wrote:
Dave Hansen wrote:
I was getting some kvm userspace crashes trying to run a Windows guest.
So, I decided to try a recent kernel (2.6.25-rc6-00333-ga4083c9) with
the kvm kernel code that shipped with that kernel.
This is fixed
I was getting some kvm userspace crashes trying to run a Windows guest.
So, I decided to try a recent kernel (2.6.25-rc6-00333-ga4083c9) with
the kvm kernel code that shipped with that kernel.
I've had some lockups doing similar things over the last month or two,
but figured it was something
On Thu, 2008-03-20 at 21:35 +0100, Carsten Otte wrote:
Dave Hansen wrote:
Well, and more fundamentally: do we really want dup_mm() able to be
called from other code?
Maybe we need a bit more detailed justification why fork() itself isn't
good enough. It looks to me like they basically
On Thu, 2008-03-20 at 10:28 -0700, Jeremy Fitzhardinge wrote:
Carsten Otte wrote:
+struct mm_struct *dup_mm(struct task_struct *tsk);
No prototypes in .c files. Put this in an appropriate header.
Well, and more fundamentally: do we really want dup_mm() able to be
called from other code?
I use '-net user' because it is simple for me to set up, and it has
always worked flawlessly. On a recent update, though, I realized that I
couldn't use vi inside my guest because it had gotten too slow. It
feels to me like lots of network latency, but is isn't _actual_ network
latency.
I can
reason that it was done this way? Was it ever tested?
-- Dave
Signed-off-by: Dave Hansen [EMAIL PROTECTED]
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 65a70b7..cbbf35d 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -115,7 +115,8 @@ config ARCH_HAS_CPU_RELAX
config
On Tue, 2008-01-08 at 12:12 +0530, Amit Shah wrote:
BIOS-provided physical RAM map:
BIOS-e820: - 0009fc00 (usable)
BIOS-e820: 0009fc00 - 000a (reserved)
BIOS-e820: 000e8000 - 0010 (reserved)
BIOS-e820: 0010
With kvm-44, I thought my kernel was freezing during boot if I gave it
1G of RAM. But, it boots fine with 512M.
So, I instrumented the kernel, and found out that it is just taking a
long time to memset a 58MB area of memory for mem_map[]. It appears to
be taking a mmio_exit for every access of
On Tue, 2008-01-08 at 00:16 +0200, Izik Eidus wrote:
Dave Hansen wrote:
With kvm-44, I thought my kernel was freezing during boot if I gave it
1G of RAM. But, it boots fine with 512M.
So, I instrumented the kernel, and found out that it is just taking a
long time to memset a 58MB area
On Tue, 2008-01-08 at 00:46 +0200, Izik Eidus wrote:
Dave Hansen wrote:
On Tue, 2008-01-08 at 00:16 +0200, Izik Eidus wrote:
Dave Hansen wrote:
With kvm-44, I thought my kernel was freezing during boot if I gave it
1G of RAM. But, it boots fine with 512M.
So, I
drivers/kvm/kvm_main.c: In function `kvm_flush_remote_tlbs':
drivers/kvm/kvm_main.c:220: error: implicit declaration of function
`smp_call_function_mask'
make[2]: *** [drivers/kvm/kvm_main.o] Error 1
make[1]: *** [drivers/kvm] Error 2
http://sr71.net/~dave/linux/config-kvm-up
Looks like that
On Sat, 2007-07-14 at 09:27 +0300, Avi Kivity wrote:
Dave, can you compare the output of hdparm -v /dev/hda? Maybe more
clues there.
slow:
qemu:~# hdparm -v /dev/hda
/dev/hda:
multcount= 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq= 0 (off)
using_dma= 1 (on)
On Sun, 2007-07-15 at 21:27 +0200, Luca wrote:
On 7/13/07, Dave Hansen [EMAIL PROTECTED] wrote:
diff -ru kvm-fast-dmesg.txt kvm-slow-dmesg.txt
Linux version 2.6.22 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Ubuntu
4.1.2-0ubuntu4)) #13 Wed Jul 11 15:27:01 PDT 2007
Is this a vanilla
On Sun, 2007-07-15 at 23:22 +0200, Luca wrote:
Can you re-test KVM 27 with it's BIOS (i.e. use something like -L
~/src/kvm-27/qemu/pc-bios)?
Doing that does appear to make it behave like kvm-28. DMA enabled, and
slow I/O:
qemu:~# hdparm -v /dev/hda
/dev/hda:
multcount= 16 (on)
On Fri, 2007-07-13 at 17:39 +0200, Luca wrote:
Dave, can you confirm that backing out my patch fixes your speed
issue?
Sure, I'll check current git with and without your patch.
I've reproduced that _applying_ it to kvm-27 creates the slowdown, but
I'll double-check that backing it out
On Thu, 2007-07-12 at 08:37 +0300, Avi Kivity wrote:
Can you confirm it by backing out that one patch?
Do you know the git commit id by chance?
-- Dave
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express
On Tue, 2007-07-10 at 08:44 +0300, Avi Kivity wrote:
What does 'top' on the host show in both cases?
On the fast one (kvm-27) I just see the dd as a flash in top. It
doesn't stay for long. The VM isn't very responsive during the dd.
On the slow (kvm-28) one, I see the dd in top creeping
On Sun, 2007-07-08 at 11:14 +0300, Avi Kivity wrote:
Dave Hansen wrote:
I've noticed that some of my tests run *MUCH* slower in kvm-28 than in
27. I'm sure that wall time is pretty wonky in the guests, but it is
much slower in real-world time as well.
Here's a little test to create
I had a host running kvm-27 oops on me last week. The system had been
up for about 2 weeks, and had probably run and stopped at least a couple
hundred kvm guests. I don't think it is very reproducible, but here it
is anyway. The host is running 2.6.20.4.
Here's the actual BUG_ON() that was
On Mon, 2007-07-02 at 20:58 +0200, Luca wrote:
MMU working memory was exhausted during a guest context switch. It has
been fixed by:
KVM: Lazy guest cr3 switching
4b82b37a35a085a07d9ed84efee06c69655fd3d1
which is included in KVM-28.
OK, I'll give kvm-28 a shot. Thanks for the help!
25 matches
Mail list logo
