From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [kvm-devel] kvm causing memory corruption? ~2.6.25-rc6
Date: Thu, 27 Mar 2008 07:55:09 -0700 [thread overview]
Message-ID: <1206629709.7883.30.camel@nimitz.home.sr71.net> (raw)
In-Reply-To: <47EB7281.6070300@qumranet.com>
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? :)
The host has 4GB of RAM exactly, but there are some serious BIOS holes,
so I needed PAE because about a gig of it is mapped >4GB.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009d800 (usable)
[ 0.000000] BIOS-e820: 000000000009d800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000d2000 - 00000000000d4000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000bf6b0000 (usable)
[ 0.000000] BIOS-e820: 00000000bf6b0000 - 00000000bf6cc000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000bf6cc000 - 00000000bf700000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000bf700000 - 00000000c0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed00000 - 00000000fed00400 (reserved)
[ 0.000000] BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed90000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 000000013c000000 (usable)
-- Dave
next prev parent reply other threads:[~2008-03-27 14:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 21:12 Dave Hansen
2008-03-26 9:50 ` [kvm-devel] " Avi Kivity
2008-03-26 16:52 ` Dave Hansen
2008-03-26 16:58 ` Avi Kivity
2008-03-26 17:16 ` Dave Hansen
2008-03-27 9:36 ` Avi Kivity
2008-03-27 10:10 ` Avi Kivity
2008-03-27 14:55 ` Dave Hansen [this message]
2008-03-27 14:59 ` Avi Kivity
2008-03-27 16:30 ` Dave Hansen
2008-06-02 22:30 ` kvm causing memory corruption? now 2.6.26-rc4 Dave Hansen
2008-06-03 0:59 ` Dave Hansen
2008-06-04 13:42 ` Avi Kivity
2008-06-06 7:41 ` Dave Hansen
2008-06-12 13:10 ` Avi Kivity
2008-06-16 18:07 ` Dave Hansen
2008-07-15 18:57 ` kvm causing memory corruption? now 2.6.26-rc8 Dave Hansen
2008-07-16 21:44 ` kvm causing memory corruption? now 2.6.26 Dave Hansen
2008-07-16 22:48 ` KVM overflows the stack Dave Hansen
2008-07-17 5:52 ` Avi Kivity
2008-07-17 6:08 ` Roland Dreier
2008-07-17 14:06 ` Dave Hansen
2008-07-17 14:15 ` Avi Kivity
2008-07-17 6:14 ` Dave Hansen
2008-07-17 6:42 ` Avi Kivity
2008-07-17 6:45 ` [PATCH] update kvm's anon_inodes.c for r/o bind mounts Dave Hansen
2008-07-19 7:33 ` Avi Kivity
2008-07-17 6:27 ` KVM overflows the stack Dave Hansen
2008-07-17 5:38 ` kvm causing memory corruption? now 2.6.26 Avi Kivity
2008-03-27 15:50 ` [kvm-devel] kvm causing memory corruption? ~2.6.25-rc6 Dave Hansen
2008-03-27 15:53 ` Avi Kivity
2008-03-27 16:30 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1206629709.7883.30.camel@nimitz.home.sr71.net \
--to=dave@linux.vnet.ibm.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®