On 11/25/19 1:22 PM, Thomas Lamprecht wrote:
On 11/25/19 12:33 PM, Stefan Reiter wrote:
Approach is correct IMO, probably the easiest way, and I agree that it seems
unlikely that QEMU's patch version will be important in the future.
Some stuff inline.
On 11/25/19 11:27 AM, Thomas Lamprecht wr
On 11/25/19 12:33 PM, Stefan Reiter wrote:
> Approach is correct IMO, probably the easiest way, and I agree that it seems
> unlikely that QEMU's patch version will be important in the future.
>
> Some stuff inline.
>
> On 11/25/19 11:27 AM, Thomas Lamprecht wrote:
>> With our QEMU 4.1.1 package
Approach is correct IMO, probably the easiest way, and I agree that it
seems unlikely that QEMU's patch version will be important in the future.
Some stuff inline.
On 11/25/19 11:27 AM, Thomas Lamprecht wrote:
With our QEMU 4.1.1 package we can pass a additional internal version
to QEMU's mach
With our QEMU 4.1.1 package we can pass a additional internal version
to QEMU's machine, it will be split out there and ignored, but
returned on a QMP 'query-machines' call.
This allows us to use it for reducing the granularity with which we
can roll-out HW layout changes/additions for VMs. Until
