From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, Alexander Graf <agraf@suse.de>
Cc: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
aik@ozlabs.ru, armbru@redhat.com, qemu-devel@nongnu.org,
qemu-ppc@nongnu.org, marcel.apfelbaum@gmail.com,
imammedo@redhat.com, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [REBASE PATCH v5 1/2] machine: add default_ram_size to machine class
Date: Thu, 30 Apr 2015 15:05:59 +0200 [thread overview]
Message-ID: <554228B7.3070503@redhat.com> (raw)
In-Reply-To: <20150430114041.412238a2@thh440s>
On 30/04/2015 11:40, Thomas Huth wrote:
>>>> On 29/04/2015 11:06, Nikunj A Dadhania wrote:
>>>>>> so David can push both patches.
>>>>>>
>>>>>> But isn't 1G a bit too much? At least on x86 you can easily boot with 512M.
>>>>>
>>>>> I understood this number as not the _minimum memory_ to boot the
>>>>> VM. And this will only come in picture when the user has not specified
>>>>> any memory.
>>>>
>>>> This in turn will basically only happen for QEMU developers. So keeping
>>>> the default on the low side would make sense.
>>>>
>>>> On my (4G memory) laptop I might not even be able to boot a PPC64 VM
>>>> with 1G and TCG, but I can do that nicely with 256M.
>>>
>>> That will be fine with me as well, i.e. 256M
>>>
>>> David/Alex, Do you have comments on this before we change it?
>>
>> I've seen RAM size combinations that seemed to work ok, but then failed
>> during grub2 execution for example. Please verify with all reasonably
>> realistically executed distributions that 256MB is enough.
>
> Since this default value will likely be there for the next couple of
> years, it's maybe better to use a slightly higher value than one that
> is too low - the amount of RAM that a guest requires likely rather
> increases in the next years instead of going down again. So I think
> using 512 MB instead is maybe a good compromise?
Sure, 512 is okay with me.
Paolo
next prev parent reply other threads:[~2015-04-30 13:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 6:53 [Qemu-devel] [REBASE PATCH v5 0/2] Introduce default ram size in MachineClass Nikunj A Dadhania
2015-04-28 6:53 ` [Qemu-devel] [REBASE PATCH v5 1/2] machine: add default_ram_size to machine class Nikunj A Dadhania
2015-04-28 11:30 ` Thomas Huth
2015-04-29 1:56 ` David Gibson
2015-04-29 8:14 ` Nikunj A Dadhania
2015-04-29 8:33 ` Paolo Bonzini
2015-04-29 9:06 ` Nikunj A Dadhania
2015-04-29 9:10 ` Paolo Bonzini
2015-04-30 4:41 ` Nikunj A Dadhania
2015-04-30 9:18 ` Alexander Graf
2015-04-30 9:40 ` Thomas Huth
2015-04-30 9:43 ` Alexander Graf
2015-04-30 16:58 ` Nikunj A Dadhania
2015-04-30 13:05 ` Paolo Bonzini [this message]
2015-04-28 6:53 ` [Qemu-devel] [REBASE PATCH v5 2/2] spapr: override default ram size to 1GB Nikunj A Dadhania
2015-04-28 11:32 ` Thomas Huth
2015-04-29 1:57 ` David Gibson
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=554228B7.3070503@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=imammedo@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@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 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).