On 09/06/2023 16.06, Igor Mammedov wrote:
On Mon, 22 May 2023 15:17:17 +0200
Igor Mammedov wrote:
Paolo,
can you pick it up?
It's merged already (commit a37531f2381c4e294e48b14170894741283)
Cheers,
Thomas
On Mon, 22 May 2023 15:17:17 +0200
Igor Mammedov wrote:
Paolo,
can you pick it up?
> QEMU aborts when default RAM backend should be used (i.e. no
> explicit '-machine memory-backend=' specified) but user
> has created an object which 'id' equals to default RAM backend
> name used by board.
>
>
s/stollen/stolen/ in the subject
On 22/05/2023 15.17, Igor Mammedov wrote:
QEMU aborts when default RAM backend should be used (i.e. no
explicit '-machine memory-backend=' specified) but user
has created an object which 'id' equals to default RAM backend
name used by board.
$QEMU -machine p
With the patch, qemu exits normally instead of Aborted.
On 5/22/23 21:17, Igor Mammedov wrote:
QEMU aborts when default RAM backend should be used (i.e. no
explicit '-machine memory-backend=' specified) but user
has created an object which 'id' equals to default RAM backend
name used by board.
On 22/5/23 15:17, Igor Mammedov wrote:
QEMU aborts when default RAM backend should be used (i.e. no
explicit '-machine memory-backend=' specified) but user
has created an object which 'id' equals to default RAM backend
name used by board.
$QEMU -machine pc \
-object memory-backend-ram,
