On Tue, Nov 10, 2015 at 04:01:51PM +0100, Paolo Bonzini wrote:
>
>
> On 09/11/2015 21:46, Michael S. Tsirkin wrote:
> > On Mon, Nov 02, 2015 at 12:55:07PM +0100, Paolo Bonzini wrote:
> >> On 30/10/2015 20:36, Eduardo Habkost wrote:
> >>> In 2012, QEMU had a bug where it exposed QEMU version infor
On 09/11/2015 21:46, Michael S. Tsirkin wrote:
> On Mon, Nov 02, 2015 at 12:55:07PM +0100, Paolo Bonzini wrote:
>> On 30/10/2015 20:36, Eduardo Habkost wrote:
>>> In 2012, QEMU had a bug where it exposed QEMU version information
>>> to the guest, meaning a QEMU upgrade would expose different
>>>
On Mon, Nov 02, 2015 at 12:55:07PM +0100, Paolo Bonzini wrote:
>
>
> On 30/10/2015 20:36, Eduardo Habkost wrote:
> > In 2012, QEMU had a bug where it exposed QEMU version information
> > to the guest, meaning a QEMU upgrade would expose different
> > hardware to the guest OS even if the same mach
On 30/10/2015 20:36, Eduardo Habkost wrote:
> In 2012, QEMU had a bug where it exposed QEMU version information
> to the guest, meaning a QEMU upgrade would expose different
> hardware to the guest OS even if the same machine-type is being
> used.
>
> The bug was fixed by commit 93bfef4c6e4b23ca