All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: kvm@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH] README: add information about memory usage
Date: Mon, 24 Feb 2014 22:29:37 -0500	[thread overview]
Message-ID: <20140224222937.46a1b511@redhat.com> (raw)

I got a report of someone trying to run tests with a large amount of
RAM (4GB), which broke the guest as free_memory() function (called
by setup_vm()) will override the PCI hole.

Let's document memory constraints so that people don't do that.

Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
---
 README | 4 ++++
 1 file changed, 4 insertions(+)


diff --git a/README b/README
index db525e3..0f5d810 100644
--- a/README
+++ b/README
@@ -18,6 +18,10 @@ This invocation runs the msr test case. The test outputs to stdio.
 Using qemu (supported since qemu 1.3):
 qemu-system-x86_64 -enable-kvm -device pc-testdev -serial stdio -device isa-debug-exit,iobase=0xf4,iosize=0x4 -kernel ./x86/msr.flat
 
+Note that it's not necessary to specify the "-m" option to qemu. The default
+memory size is enough. Actually, the tests infrastructure doesn't support too
+much RAM anyway, so specifying a large amount of RAM may break it.
+
 Or use a runner script to detect the correct invocation:
 ./x86-run ./x86/msr.flat
 To select a specific qemu binary, specify the QEMU=<path> environment:
-- 
1.8.1.4


             reply	other threads:[~2014-02-25  3:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25  3:29 Luiz Capitulino [this message]
2014-02-26 11:05 ` [PATCH] README: add information about memory usage Paolo Bonzini

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=20140224222937.46a1b511@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.