From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: David Hildenbrand <david@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: ThinerLogoer <logoerthiner1@163.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Daniel P.Berrangé" <berrange@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Elena Ufimtseva" <elena.ufimtseva@oracle.com>,
"Jagannathan Raman" <jag.raman@oracle.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Ani Sinha" <anisinha@redhat.com>,
"Xiao Guangrong" <xiaoguangrong.eric@gmail.com>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Greg Kurz" <groug@kaod.org>, "Eric Blake" <eblake@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>
Subject: Re: [PATCH v3 11/11] machine: Improve error message when using default RAM backend id
Date: Tue, 29 Aug 2023 13:29:43 +0200 [thread overview]
Message-ID: <c16efe25-5559-fb0e-a89a-e9b7ffd1561b@linaro.org> (raw)
In-Reply-To: <78fd367f-740a-4b37-0faf-dd0cabae4bd6@redhat.com>
On 25/8/23 12:10, David Hildenbrand wrote:
> On 25.08.23 11:59, David Hildenbrand wrote:
>> On 25.08.23 11:56, Markus Armbruster wrote:
>>> David Hildenbrand <david@redhat.com> writes:
>>>
>>>> On 25.08.23 11:10, Markus Armbruster wrote:
>>>>> David Hildenbrand <david@redhat.com> writes:
>>>>>
>>>>>> On 25.08.23 08:57, ThinerLogoer wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> At 2023-08-23 23:34:11, "David Hildenbrand" <david@redhat.com>
>>>>>>> wrote:
>>>>>>>> For migration purposes, users might want to reuse the default RAM
>>>>>>>> backend id, but specify a different memory backend.
>>>>>>>>
>>>>>>>> For example, to reuse "pc.ram" on q35, one has to set
>>>>>>>> -machine q35,memory-backend=pc.ram
>>>>>>>> Only then, can a memory backend with the id "pc.ram" be created
>>>>>>>> manually.
>>>>>>>>
>>>>>>>> Let's improve the error message.
>>>>>>>>
>>>>>>>> Unfortuantely, we cannot use error_append_hint(), because the
>>>>>>>> caller
>>>>>>>> passes &error_fatal.
>>>>>>>>
>>>>>>>> Suggested-by: ThinerLogoer <logoerthiner1@163.com>
>>>>>>>> Signed-off-by: David Hildenbrand <david@redhat.com>
>>>>>>>> ---
>>>>>>>> hw/core/machine.c | 4 +++-
>>>>>>>> 1 file changed, 3 insertions(+), 1 deletion(-)
> diff --git a/hw/core/machine.c b/hw/core/machine.c
> index f0d35c6401..09f40c7f07 100644
> --- a/hw/core/machine.c
> +++ b/hw/core/machine.c
> @@ -1352,6 +1352,7 @@ out:
>
> void machine_run_board_init(MachineState *machine, const char
> *mem_path, Error **errp)
> {
> + ERRP_GUARD();
> MachineClass *machine_class = MACHINE_GET_CLASS(machine);
> ObjectClass *oc = object_class_by_name(machine->cpu_type);
> CPUClass *cc;
> @@ -1380,9 +1381,13 @@ void machine_run_board_init(MachineState
> *machine, const char *mem_path, Error *
> numa_uses_legacy_mem()) {
> if (object_property_find(object_get_objects_root(),
> machine_class->default_ram_id)) {
> - error_setg(errp, "object name '%s' is reserved for the
> default"
> - " RAM backend, it can't be used for any other purposes."
> - " Change the object's 'id' to something else",
> + error_setg(errp, "object's id '%s' is reserved for the
> default"
> + " RAM backend, it can't be used for any other purposes",
> + machine_class->default_ram_id);
> + error_append_hint(errp,
> + "Change the object's 'id' to something else or disable"
> + " automatic creation of the default RAM backend by
> setting"
> + " 'memory-backend=%s' with '-machine'.\n",
> machine_class->default_ram_id);
> return;
> }
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2023-08-29 11:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 15:34 [PATCH v3 00/11] memory-backend-file related improvements and VM templating support David Hildenbrand
2023-08-23 15:34 ` [PATCH v3 01/11] nvdimm: Reject writing label data to ROM instead of crashing QEMU David Hildenbrand
2023-08-23 15:34 ` [PATCH v3 02/11] softmmu/physmem: Distinguish between file access mode and mmap protection David Hildenbrand
2023-08-23 20:21 ` Peter Xu
2023-08-23 15:34 ` [PATCH v3 03/11] backends/hostmem-file: Add "rom" property to support VM templating with R/O files David Hildenbrand
2023-09-01 12:50 ` Markus Armbruster
2023-08-23 15:34 ` [PATCH v3 04/11] softmmu/physmem: Remap with proper protection in qemu_ram_remap() David Hildenbrand
2023-08-23 20:21 ` Peter Xu
2023-08-29 11:18 ` Philippe Mathieu-Daudé
2023-08-23 15:34 ` [PATCH v3 05/11] softmmu/physmem: Bail out early in ram_block_discard_range() with readonly files David Hildenbrand
2023-08-23 20:21 ` Peter Xu
2023-08-23 15:34 ` [PATCH v3 06/11] softmmu/physmem: Fail creation of new files in file_ram_open() with readonly=true David Hildenbrand
2023-08-23 20:22 ` Peter Xu
2023-08-23 15:34 ` [PATCH v3 07/11] softmmu/physmem: Never return directories from file_ram_open() David Hildenbrand
2023-08-23 20:22 ` Peter Xu
2023-08-23 15:34 ` [PATCH v3 08/11] docs: Don't mention "-mem-path" in multi-process.rst David Hildenbrand
2023-08-23 15:34 ` [PATCH v3 09/11] docs: Start documenting VM templating David Hildenbrand
2023-08-29 11:25 ` Philippe Mathieu-Daudé
2023-08-23 15:34 ` [PATCH v3 10/11] softmmu/physmem: Hint that "readonly=on, rom=off" exists when opening file R/W for private mapping fails David Hildenbrand
2023-08-23 15:34 ` [PATCH v3 11/11] machine: Improve error message when using default RAM backend id David Hildenbrand
2023-08-25 6:57 ` ThinerLogoer
2023-08-25 7:36 ` [PATCH " David Hildenbrand
2023-08-25 9:10 ` Markus Armbruster
2023-08-25 9:13 ` David Hildenbrand
2023-08-25 9:56 ` Markus Armbruster
2023-08-25 9:59 ` David Hildenbrand
2023-08-25 10:10 ` David Hildenbrand
2023-08-29 11:29 ` Philippe Mathieu-Daudé [this message]
2023-09-01 12:52 ` Markus Armbruster
2023-08-29 8:31 ` Mario Casquero
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=c16efe25-5559-fb0e-a89a-e9b7ffd1561b@linaro.org \
--to=philmd@linaro.org \
--cc=anisinha@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=danielhb413@gmail.com \
--cc=david@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=elena.ufimtseva@oracle.com \
--cc=groug@kaod.org \
--cc=imammedo@redhat.com \
--cc=jag.raman@oracle.com \
--cc=logoerthiner1@163.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xiaoguangrong.eric@gmail.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).