From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-1953353 ] could not load PC BIOS '/path/to/bios.bin' on "-m 4096"
Date: Mon, 26 May 2008 09:50:10 -0700 [thread overview]
Message-ID: <E1K0fti-0002mg-47@sc8-sf-web23.sourceforge.net> (raw)
Bugs item #1953353, was opened at 2008-04-28 07:50
Message generated for change (Settings changed) made by aliguori
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1953353&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Rafal Wijata (ravpl)
Assigned to: Nobody/Anonymous (nobody)
Summary: could not load PC BIOS '/path/to/bios.bin' on "-m 4096"
Initial Comment:
The maximum amount of memory I can give to kvm is ~3560M
I run custom compiled kvm-66 on F8 box with
Linux mailhub 2.6.24.4-64.fc8 #1 SMP Sat Mar 29 09:15:49 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
The modules are loaded from F8 kernel, rather than those shipped with kvm-66
----------------------------------------------------------------------
Comment By: Izik Eidus (izike)
Date: 2008-04-30 10:12
Message:
Logged In: YES
user_id=1851802
Originator: NO
above 4 giga support in kvm, work stable just for kernel modules with
userspace memory allocation (kvm 50~, or 2.6.25)
however there is no actually any limitation in making it work for older
kernel modules,
i will take a look on it, (but it will take me few weeks until i will
touch it)
----------------------------------------------------------------------
Comment By: Marcelo Tosatti (mtosatti)
Date: 2008-04-30 09:30
Message:
Logged In: YES
user_id=2022487
Originator: NO
This bug can be marked as CLOSED.
----------------------------------------------------------------------
Comment By: Rafal Wijata (ravpl)
Date: 2008-04-30 08:53
Message:
Logged In: YES
user_id=996150
Originator: YES
Indeed, I grabbed the kvm-67, recompiled, and loaded modules that comes
with kvm(kvm-intel).
After that I could give to the guest even 6G of ram.
And BTW, after I loaded those modules I was able to assign more than 4
CPUs to the guest as well(I remember there's such bug here).
Thanx for prompt reply.
----------------------------------------------------------------------
Comment By: Marcelo Tosatti (mtosatti)
Date: 2008-04-29 21:34
Message:
Logged In: YES
user_id=2022487
Originator: NO
Can you reproduce the problem with the modules shipped with kvm-66?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1953353&group_id=180599
next reply other threads:[~2008-05-26 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 16:50 SourceForge.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-27 3:34 [ kvm-Bugs-1953353 ] could not load PC BIOS '/path/to/bios.bin' on "-m 4096" SourceForge.net
2008-05-26 16:56 SourceForge.net
2008-04-30 14:12 SourceForge.net
2008-04-30 13:30 SourceForge.net
2008-04-30 12:53 SourceForge.net
2008-04-30 1:34 SourceForge.net
2008-04-28 11:50 SourceForge.net
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=E1K0fti-0002mg-47@sc8-sf-web23.sourceforge.net \
--to=noreply@sourceforge.net \
/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