Re: [Qemu-devel] [PATCH] Don't use QEMU_VERSION in ATA/ATAPI replies to IDENTIFY cmds

["Glauber Costa" <glommer@gmail.com>]

On Wed, Sep 10, 2008 at 10:19 PM, Marc Bevand <m.bevand@gmail.com> wrote:
> On Wed, Sep 10, 2008 at 5:30 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
>>
>> Wouldn't it be better to just use whatever QEMU_VERSION is right now with a
>> big fat comment? At least then, any VM made with QEMU 0.9.1 won't require
>> reactivation.
>> No point in breaking everyone by changing it to 1.0.
>
> Yeah that could work too.
>
> (However I don't expect that changing it to 1.0 would break everyone.
> Only a minority. Because multiple hardware changes are necessary to
> trigger a need for reactivacion. In my case, I was changing the MAC
> address, upgrading to a 64-bit host (it made Windows see slightly
> different CPUID results), and upgrading QEMU (it made Windows see new
> hdd/dvd drive firmware versions). All 3 events were necessary to
> trigger a need for reactivation.)

given this info you just provided, this is probably a non-issue. After
all, if you're
changing so much things in your guest, you _are_ changing your machine in every
way that matters to the O.S. So if the O.S. is sucky enough to require
those kind of
activations, we should ultimately respect it.


-- 
Glauber Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."