Re: [PATCH v3 1/1] Fix the coredump when memory backend id conflicts with default_ram_id

On Mon, Jun 13, 2022 at 5:31 PM David Hildenbrand wrote: > > On 13.06.22 16:37, Li Zhang wrote: > > On Mon, Jun 13, 2022 at 4:19 PM Igor Mammedov wrote: > >> > >> On Mon, 13 Jun 2022 12:44:02 +0200 > >> Li Zhang wrote: > >> > >>> When no memory backend is specified in machine options, > >>> a

Re: [PATCH v3 1/1] Fix the coredump when memory backend id conflicts with default_ram_id

On 13.06.22 16:37, Li Zhang wrote: > On Mon, Jun 13, 2022 at 4:19 PM Igor Mammedov wrote: >> >> On Mon, 13 Jun 2022 12:44:02 +0200 >> Li Zhang wrote: >> >>> When no memory backend is specified in machine options, >>> a default memory device will be added with default_ram_id. >>> However, if a

Re: [PATCH v3 1/1] Fix the coredump when memory backend id conflicts with default_ram_id

On Mon, Jun 13, 2022 at 4:19 PM Igor Mammedov wrote: > > On Mon, 13 Jun 2022 12:44:02 +0200 > Li Zhang wrote: > > > When no memory backend is specified in machine options, > > a default memory device will be added with default_ram_id. > > However, if a memory backend object is added in QEMU

Re: [PATCH v3 1/1] Fix the coredump when memory backend id conflicts with default_ram_id

On Mon, 13 Jun 2022 12:44:02 +0200 Li Zhang wrote: > When no memory backend is specified in machine options, > a default memory device will be added with default_ram_id. > However, if a memory backend object is added in QEMU options > and id is the same as default_ram_id, a coredump happens. >

[PATCH v3 1/1] Fix the coredump when memory backend id conflicts with default_ram_id

When no memory backend is specified in machine options, a default memory device will be added with default_ram_id. However, if a memory backend object is added in QEMU options and id is the same as default_ram_id, a coredump happens. Command line: qemu-system-x86_64 -name