From: Markus Armbruster <armbru@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: peter.maydell@linaro.org, jan.kiszka@siemens.com,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Funny -m arguments can crash
Date: Wed, 08 Aug 2012 11:04:22 +0200 [thread overview]
Message-ID: <87wr1921rd.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <CAAu8pHu4pPbgxUxd2N+iVyoUmqXEgMMtupZDxx+YwqXkUOKeRQ@mail.gmail.com> (Blue Swirl's message of "Mon, 30 Jul 2012 15:05:41 +0000")
Blue Swirl <blauwirbel@gmail.com> writes:
> On Mon, Jul 30, 2012 at 12:56 PM, Markus Armbruster <armbru@redhat.com> wrote:
>> Blue Swirl <blauwirbel@gmail.com> writes:
>>
>>> On Sat, Jul 28, 2012 at 6:41 AM, Markus Armbruster <armbru@redhat.com> wrote:
>>>> Blue Swirl <blauwirbel@gmail.com> writes:
>>>>
>>>>> On Wed, Jul 25, 2012 at 11:49 AM, Markus Armbruster
>>>>> <armbru@redhat.com> wrote:
>>>>>> Asking for "funny" memory sizes sometimes crashes for me. For instance
>>>>>> -m 0.8 or the equivalent -m 838860b. -m 0.7 appears to work.
>>>>>>
>>>>>> Should we round memory sizes? How? Where?
>>>>>
>>>>> We had a discussion about this recently:
>>>>> http://lists.nongnu.org/archive/html/qemu-devel/2012-06/msg02800.html
>>>>
>>>> I missed that, thanks!
>>>>
>>>> Unfortunately, the thread petered out without a conclusion. What now?
>>>
>>> There's no patch to do the check in vl.c for 8k. Lacking the patch, we
>>> don't know exactly what is the charge level of megaphone batteries:
>>> like Schrödinger's cat, they may be dead or fully charged.
>>
>> What would you like me to do? Round argument of -m up to next multiple
>> of 8KiB?
>
> Yes please, maybe with a notice to the user.
Next problem: minimum RAM size.
For instance, -M pc -m X, where X < 32KiB dies "qemu: fatal: Trying to
execute code outside RAM or ROM at [...] Aborted (core dumped)" with
TCG, and "KVM internal error. Suberror: 1" with KVM.
Should a minimum RAM size be enforced? Board-specific?
I'm inclined to declare this one a feature...
next prev parent reply other threads:[~2012-08-08 9:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 11:49 [Qemu-devel] Funny -m arguments can crash Markus Armbruster
2012-07-27 19:00 ` Blue Swirl
2012-07-28 6:41 ` Markus Armbruster
2012-07-28 8:29 ` Blue Swirl
2012-07-30 12:56 ` Markus Armbruster
2012-07-30 15:05 ` Blue Swirl
2012-08-08 9:04 ` Markus Armbruster [this message]
2012-08-08 9:16 ` Peter Maydell
2012-08-08 10:02 ` Markus Armbruster
2012-08-08 9:48 ` Avi Kivity
2012-08-13 13:41 ` Markus Armbruster
2012-08-13 13:56 ` Avi Kivity
2012-08-13 14:02 ` Gleb Natapov
2012-08-13 14:04 ` Avi Kivity
2012-08-13 14:10 ` Gleb Natapov
2012-08-13 20:35 ` Blue Swirl
2012-08-19 19:26 ` Kevin O'Connor
2012-08-13 14:19 ` Anthony Liguori
2012-08-13 14:46 ` Markus Armbruster
2012-08-14 8:44 ` Markus Armbruster
2012-08-14 10:20 ` Avi Kivity
2012-08-14 10:44 ` Jan Kiszka
2012-08-14 10:51 ` Avi Kivity
2012-08-14 11:01 ` Jan Kiszka
2012-08-14 13:16 ` Avi Kivity
2012-08-14 13:25 ` Jan Kiszka
2012-08-14 13:42 ` Avi Kivity
2012-08-14 11:12 ` Markus Armbruster
2012-08-14 13:25 ` Avi Kivity
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=87wr1921rd.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.com \
--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.