From: Bernhard Held <bheld@mgpi.de>
To: dbareiro@gmx.net, kvm@vger.kernel.org
Subject: Re: Very high memory usage with KVM
Date: Mon, 10 Aug 2009 18:15:17 +0200 [thread overview]
Message-ID: <4A804795.8080302@mgpi.de> (raw)
In-Reply-To: <20090810152241.GC16293@defiant.freesoftware.org>
Hi Daniel!
> I've set in the kernel config:
>
> CONFIG_FIRMWARE_IN_KERNEL=y
And what happened? Are you sure you recompiled and booted the new kernel with
CONFIG_FIRMWARE_IN_KERNEL=y?
> Although I don't see the asked file in initramfs. The file with full
> path is /lib/firmware/bnx2/bnx2-mips-06-4.6.16.fw:
>
> # zcat /boot/initrd.img-2.6.30.4-dgb | cpio -t | grep bnx2
> lib/modules/2.6.30.4-dgb/kernel/drivers/net/bnx2.ko
> 300859 blocks
>
> Whereupon this variable is set to 'y' would not have to be sufficient?
>
> <just_guessing>
> 1) Perhaps firmware must be in some other directory.
> 2) Perhaps there is no access to the FS in /lib at the moment that loads
> drivers.
> </just_guessing>
Obviously bnx2.ko is loaded from initramfs. At that time the root filesystem is
not accessible. I expected CONFIG_FIRMWARE_IN_KERNEL=y is sufficient to solve
the problem.
Here is what I would try:
- make sure the firmware is included in your kernel, or
- keep bnx2.ko from including in initramfs (unless you boot via network), or
- include /lib/firmware/bnx2/bnx2-mips-06-4.6.16.fw in initramfs
HTH
Bernhard
next prev parent reply other threads:[~2009-08-10 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 17:43 Very high memory usage with KVM Daniel Bareiro
2009-07-26 11:31 ` Avi Kivity
2009-07-26 14:56 ` Daniel Bareiro
2009-07-26 15:11 ` Avi Kivity
2009-07-26 15:50 ` Daniel Bareiro
2009-07-26 16:19 ` Avi Kivity
2009-08-08 0:54 ` Daniel Bareiro
2009-08-09 9:12 ` Avi Kivity
2009-08-10 6:40 ` Bernhard Held
2009-08-10 15:22 ` Daniel Bareiro
2009-08-10 16:15 ` Bernhard Held [this message]
2009-08-22 2:28 ` Daniel Bareiro
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=4A804795.8080302@mgpi.de \
--to=bheld@mgpi.de \
--cc=dbareiro@gmx.net \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).