qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
To: Thomas Huth <thuth@linux.vnet.ibm.com>
Cc: qemu-ppc@nongnu.org, Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Introduce machine specific default memory size
Date: Wed, 04 Mar 2015 15:26:16 +0530	[thread overview]
Message-ID: <87mw3t6q7z.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150304103918.230ad0b6@oc7435384737.ibm.com>

Thomas Huth <thuth@linux.vnet.ibm.com> writes:

> On Wed, 04 Mar 2015 14:59:13 +0530
> Nikunj A Dadhania <nikunj@linux.vnet.ibm.com> wrote:
>
>> Thomas Huth <thuth@linux.vnet.ibm.com> writes:
>> 
>> > On Wed, 04 Mar 2015 14:34:27 +0530
>> > Nikunj A Dadhania <nikunj@linux.vnet.ibm.com> wrote:
>> >
>> >> Thomas Huth <thuth@linux.vnet.ibm.com> writes:
>> >> 
>> >> > On Wed, 04 Mar 2015 14:00:17 +0530
>> >> > Nikunj A Dadhania <nikunj@linux.vnet.ibm.com> wrote:
>> >> >
>> >> >> Markus Armbruster <armbru@redhat.com> writes:
>> >> >> 
>> >> >> > Nikunj A Dadhania <nikunj@linux.vnet.ibm.com> writes:
>> >> >> >
>> >> >> >> diff --git a/vl.c b/vl.c
>> >> >> >> index eb89d62..dd56754 100644
>> >> >> >> --- a/vl.c
>> >> >> >> +++ b/vl.c
>> >> >> >> @@ -4053,6 +4053,18 @@ int main(int argc, char **argv, char **envp)
>> >> >> >>          exit(1);
>> >> >> >>      }
>> >> >> >>  
>> >> >> >> +    if (machine_class->default_ram_size && ram_size < machine_class->default_ram_size) {
>> >> >> >> +        fprintf(stderr, "qemu: %s guest ram size defaulting to %ld MB\n",
>> >> >> >> +                machine_class->name,
>> >> >> >> +                machine_class->default_ram_size / (1024 * 1024));
>> >> >> >
>> >> >> > If the user explicitly asks for something, we either provide it
>> >> >> > silently, or we error out.  This does neither.  Why?
>> >> >> 
>> >> >> In case the user has provided memory not enough to boot the machine, I
>> >> >> could error out. My idea was to have a sane default which is provided by
>> >> >> the machine.
>> >> >> 
>> >> >> Initially, I had just "ram_size == default_ram_size", but then it was
>> >> >> allowing "-m 128M" to go through. And the VM would not boot. 
>> >> >> 
>> >> >> This can as well be converted to an error report and fail here to boot
>> >> >> the VM.
>> >> >
>> >> > What does exactly fail with 128MB? Linux? 
>> >> 
>> >> Linux kernel, and not much info as well on the console.
>> >
>> > Ok, but then I think it should still be possible to specify -m 128M on
>> > the command line - in case the user wants to run an older Linux which
>> > still works fine with that amount of memory.
>> 
>> But how do we distinguish whether its old/new kernel in the distro?
>> 
>> And the older kernel will boot with more memory, while the reverse isnt
>> true.
>
> True, and it's IMHO certainly ok to increase the default memory size -

> I just wanted to say that you should not disallow "-m 128M" in case the
> users know what they are doing.

That becomes a little bit tricky, as 128MB can come from
default_ram_size and from the user as well. 

So here I am only changing the machine class for sPAPR. I have tried few
distro installations and none of them boot with qemu default
memory(128MB). Moreover, the installer kernel does not tell what went
wrong. It silently goes till a point and is stuck.

Regards
Nikunj

  reply	other threads:[~2015-03-04  9:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 12:54 [Qemu-devel] [PATCH] Introduce machine specific default memory size Nikunj A Dadhania
2015-03-04  7:24 ` Markus Armbruster
2015-03-04  8:30   ` Nikunj A Dadhania
2015-03-04  8:59     ` Thomas Huth
2015-03-04  9:04       ` Nikunj A Dadhania
2015-03-04  9:19         ` Thomas Huth
2015-03-04  9:29           ` Nikunj A Dadhania
2015-03-04  9:39             ` Thomas Huth
2015-03-04  9:56               ` Nikunj A Dadhania [this message]
2015-03-04 11:11     ` [Qemu-devel] [Qemu-ppc] " Nikunj A Dadhania

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=87mw3t6q7z.fsf@linux.vnet.ibm.com \
    --to=nikunj@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@linux.vnet.ibm.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).