All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "陳韋任 (Wei-Ren Chen)" <chenwj@iis.sinica.edu.tw>,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] default guest RAM size?
Date: Wed, 6 Mar 2013 18:47:54 +0000	[thread overview]
Message-ID: <20130306184753.GZ18317@redhat.com> (raw)
In-Reply-To: <CAFEAcA9MW5gMw65mFPOsEfXChjvQf-_kJEK1FKRWH3h+2tvRxg@mail.gmail.com>

On Thu, Mar 07, 2013 at 02:34:53AM +0800, Peter Maydell wrote:
> On 6 March 2013 11:59, Rob Landley <rob@landley.net> wrote:
> > On 03/05/2013 12:09:27 AM, Peter Maydell wrote:
> >> On 5 March 2013 14:07, 陳韋任 (Wei-Ren Chen) <chenwj@iis.sinica.edu.tw>
> >> wrote:
> >> > On Tue, Mar 05, 2013 at 01:40:38PM +0800, Peter Maydell wrote:
> >> >> On 5 March 2013 13:26, Michael Tokarev <mjt@tls.msk.ru> wrote:
> >> >> > For many years, qemu defaults to 128Mb of guest RAM size.
> >> >> > Today, this is just too small, and many OSes fails to boot
> >> >> > with this size, more, they fail to produce any reasonable
> >> >> > messages either (eg, windows7 just crashes at startup).
> >> >>
> >> >> If you make the default bigger then some boards will crash
> >> >> or behave weirdly because they try to map more RAM in than
> >> >> will fit into the space for RAM in their address maps.
> >> >
> >> >   So, 128Mb is still a good default? I am just wondering if those
> >> > boards with little memory still are major user of QEMU? :)
> >>
> >> They may not be major but they're still in the codebase. You
> >> can't just arbitrarily break them -- you need to propose
> >> a path forward that doesn't do that.
> >
> > 256 can be handled by most things.
> 
> I'm going to take a wild guess that Windows 7 doesn't do any
> better in 256MB than it does with 128 :-)

Indeed documented min requirements for Win7 are 2 GB on x86_64. In fact
very few modern OS accept anything as low as 256 MB. If you want adefault
that is suitable for anything mainstream then we're talking GB's not MB's.

Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2013-03-06 18:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05  5:26 [Qemu-devel] default guest RAM size? Michael Tokarev
2013-03-05  5:40 ` Peter Maydell
2013-03-05  6:07   ` 陳韋任 (Wei-Ren Chen)
2013-03-05  6:09     ` Peter Maydell
2013-03-06  3:59       ` Rob Landley
2013-03-06 18:34         ` Peter Maydell
2013-03-06 18:47           ` Daniel P. Berrange [this message]
2013-03-06 18:42             ` Michael Tokarev
2013-03-07  1:21           ` Rob Landley
2013-03-07  1:29             ` Peter Maydell
2013-03-06  9:28   ` Markus Armbruster
2013-03-07  2:38   ` Anthony Liguori
2013-03-07  3:40     ` [Qemu-devel] propose to implement ower device li guang
2013-03-07 13:41       ` Wenchao Xia
2013-03-11  0:34         ` li guang
2013-03-05  9:53 ` [Qemu-devel] default guest RAM size? Daniel P. Berrange

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=20130306184753.GZ18317@redhat.com \
    --to=berrange@redhat.com \
    --cc=chenwj@iis.sinica.edu.tw \
    --cc=mjt@tls.msk.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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.