David Hildenbrand writes:
> On 25.08.23 11:59, David Hildenbrand wrote:
[...]
>> ... hopefully I'm done with that error-handling pain in QEMU soon and
>> can continue focusing on things that make me feel more productive :P
I'm afraid you'll be done with error handling right when you're done
wi
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 writes:
On 25.08.23 11:10, Markus Armbruster wrote:
David Hildenbrand writes:
On 25.08.23 08:57, ThinerLogoer wrote:
Hello,
At 2023-08-23
This series has been successfully tested by QE. Start a vm using
pc.ram id but specifying a different memory-backend from the default
one. Check the error message has been improved.
Tested-by: Mario Casquero
On Wed, Aug 23, 2023 at 5:38 PM David Hildenbrand wrote:
>
> For migration purposes, u
On 25.08.23 11:59, David Hildenbrand wrote:
On 25.08.23 11:56, Markus Armbruster wrote:
David Hildenbrand writes:
On 25.08.23 11:10, Markus Armbruster wrote:
David Hildenbrand writes:
On 25.08.23 08:57, ThinerLogoer wrote:
Hello,
At 2023-08-23 23:34:11, "David Hildenbrand" wrote:
For
On 25.08.23 11:56, Markus Armbruster wrote:
David Hildenbrand writes:
On 25.08.23 11:10, Markus Armbruster wrote:
David Hildenbrand writes:
On 25.08.23 08:57, ThinerLogoer wrote:
Hello,
At 2023-08-23 23:34:11, "David Hildenbrand" wrote:
For migration purposes, users might want to reuse
David Hildenbrand writes:
> On 25.08.23 11:10, Markus Armbruster wrote:
>> David Hildenbrand writes:
>>
>>> On 25.08.23 08:57, ThinerLogoer wrote:
Hello,
At 2023-08-23 23:34:11, "David Hildenbrand" wrote:
> For migration purposes, users might want to reuse the default RAM
>>
On 25.08.23 11:10, Markus Armbruster wrote:
David Hildenbrand writes:
On 25.08.23 08:57, ThinerLogoer wrote:
Hello,
At 2023-08-23 23:34:11, "David Hildenbrand" wrote:
For migration purposes, users might want to reuse the default RAM
backend id, but specify a different memory backend.
For
David Hildenbrand writes:
> On 25.08.23 08:57, ThinerLogoer wrote:
>> Hello,
>>
>> At 2023-08-23 23:34:11, "David Hildenbrand" 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.r
On 25.08.23 08:57, ThinerLogoer wrote:
Hello,
At 2023-08-23 23:34:11, "David Hildenbrand" 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-
Hello,
At 2023-08-23 23:34:11, "David Hildenbrand" 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 memo
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 improv
11 matches
Mail list logo
