From: David Hildenbrand <david@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Halil Pasic" <pasic@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Eric Farman" <farman@linux.ibm.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Nina Schoetterl-Glausch" <nsg@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH v3 01/14] s390x/s390-virtio-ccw: don't crash on weird RAM sizes
Date: Tue, 24 Dec 2024 13:40:19 +0100 [thread overview]
Message-ID: <5727aaac-d042-48fe-b2a6-2211081124b6@redhat.com> (raw)
In-Reply-To: <85ad5cfb-f6c0-4a37-bbe4-46861778e8c9@tls.msk.ru>
On 24.12.24 13:32, Michael Tokarev wrote:
> 19.12.2024 17:41, David Hildenbrand wrote:
>> KVM is not happy when starting a VM with weird RAM sizes:
>>
>> # qemu-system-s390x --enable-kvm --nographic -m 1234K
>> qemu-system-s390x: kvm_set_user_memory_region: KVM_SET_USER_MEMORY_REGION
>> failed, slot=0, start=0x0, size=0x244000: Invalid argument
>> kvm_set_phys_mem: error registering slot: Invalid argument
>> Aborted (core dumped)
>>
>> Let's handle that in a better way by rejecting such weird RAM sizes
>> right from the start:
>>
>> # qemu-system-s390x --enable-kvm --nographic -m 1234K
>> qemu-system-s390x: ram size must be multiples of 1 MiB
>
> Shouldn't this one be picked for qemu-stable? Seems like a good
> bugfix to me. Picked up for current stable releases for now, please
> let me know if I shouldn't.
Yes, better to have it in qemu-stable, so it would be greta if you could
pick that as well (already upstream).
Thanks!
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-12-24 12:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 14:41 [PATCH v3 00/14] s390x: virtio-mem support David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 01/14] s390x/s390-virtio-ccw: don't crash on weird RAM sizes David Hildenbrand
2024-12-24 12:32 ` Michael Tokarev
2024-12-24 12:40 ` David Hildenbrand [this message]
2024-12-19 14:41 ` [PATCH v3 02/14] s390x/s390-virtio-hcall: remove hypercall registration mechanism David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 03/14] s390x/s390-virtio-hcall: prepare for more diag500 hypercalls David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 04/14] s390x: rename s390-virtio-hcall* to s390-hypercall* David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 05/14] s390x/s390-virtio-ccw: move setting the maximum guest size from sclp to machine code David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 06/14] s390x: introduce s390_get_memory_limit() David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 07/14] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 08/14] s390x/s390-stattrib-kvm: prepare for memory devices and sparse memory layouts David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 09/14] s390x/s390-skeys: prepare for memory devices David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 10/14] s390x/s390-virtio-ccw: " David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 11/14] s390x/pv: " David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 12/14] s390x: remember the maximum page size David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 13/14] s390x/virtio-ccw: add support for virtio based memory devices David Hildenbrand
2024-12-19 14:41 ` [PATCH v3 14/14] s390x: virtio-mem support David Hildenbrand
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=5727aaac-d042-48fe-b2a6-2211081124b6@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=nsg@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=richard.henderson@linaro.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 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.