From: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Dave Hansen <haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Slow Kernel Boot
Date: Tue, 08 Jan 2008 00:16:15 +0200 [thread overview]
Message-ID: <4782A4AF.6020902@qumranet.com> (raw)
In-Reply-To: <1199743548.9834.25.camel@localhost>
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 of memory for mem_map[]. It appears to
> be taking a mmio_exit for every access of every byte of memory. The end
> result is a ~100kbps memset() speed. Yes, 100 kilobytes/sec.
>
> I just tried kvm from git, and the kernel doesn't even get that far. I
> see this in debugfs
>
> insn_emulation:1393985
>
> even before I get a single kernel message. And it keeps going up, fast.
> I can get the kernel to boot just fine if I give it less than 896MB of
> RAM.
>
> kvm-44 boots long enough for me to see a really funky e820 table:
>
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 00000000fffbd000 (usable)
> BIOS-e820: 00000000fffbd000 - 00000000ffff0000 (reserved)
>
> Note that this is with '-m 1G'!! It looks to me like one of those
> sections is basically from 0x100000 up to ~4G and *usable*. That
> doesn't look right.
>
yea it really dont look right, it look like it for some reason map the
whole memory up untill the bios to the kernel as memory
it even map it on the pci hole so...
hrmmm, very weird,
what is your host info (32/64 amd/intel kernel...)? and what is the
guest info (kernel 32/64...) ?
and what happen if you run it with -no-kvm ?
and are you using new kvm-userspace as well? or just new kvm kernel
modules (or is is the oppiste?)
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next prev parent reply other threads:[~2008-01-07 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 22:05 Slow Kernel Boot Dave Hansen
2008-01-07 22:16 ` Izik Eidus [this message]
[not found] ` <4782A4AF.6020902-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-07 22:46 ` Dave Hansen
2008-01-07 22:46 ` Izik Eidus
[not found] ` <4782ABCA.2090303-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-07 23:03 ` Dave Hansen
2008-01-08 6:42 ` Amit Shah
[not found] ` <200801081212.53737.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-08 13:01 ` Amit Shah
[not found] ` <200801081831.54465.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-08 12:54 ` Izik Eidus
2008-01-08 13:18 ` Amit Shah
2008-01-08 19:13 ` Dave Hansen
2008-01-08 19:26 ` Daniel P. Berrange
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=4782A4AF.6020902@qumranet.com \
--to=izike-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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