kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] README: add information about memory usage
@ 2014-02-25  3:29 Luiz Capitulino
  2014-02-26 11:05 ` Paolo Bonzini
  0 siblings, 1 reply; 2+ messages in thread
From: Luiz Capitulino @ 2014-02-25  3:29 UTC (permalink / raw)
  To: kvm; +Cc: Paolo Bonzini

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


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] README: add information about memory usage
  2014-02-25  3:29 [PATCH] README: add information about memory usage Luiz Capitulino
@ 2014-02-26 11:05 ` Paolo Bonzini
  0 siblings, 0 replies; 2+ messages in thread
From: Paolo Bonzini @ 2014-02-26 11:05 UTC (permalink / raw)
  To: Luiz Capitulino, kvm

Il 25/02/2014 04:29, Luiz Capitulino ha scritto:
> 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:
>

Applying to kvm-unit-tests.

Paolo

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-02-26 11:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-25  3:29 [PATCH] README: add information about memory usage Luiz Capitulino
2014-02-26 11:05 ` Paolo Bonzini

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).