From: "Marc Bevand" <m.bevand@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Don't use QEMU_VERSION in ATA/ATAPI replies to IDENTIFY cmds
Date: Wed, 10 Sep 2008 18:19:20 -0700 [thread overview]
Message-ID: <aaccfcb60809101819r5abe4ce0tb383fa1c3666406c@mail.gmail.com> (raw)
In-Reply-To: <48C8669D.2000103@codemonkey.ws>
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.)
Ultimately however I think it should be user-configurable.
--
Marc Bevand
next prev parent reply other threads:[~2008-09-11 1:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 0:19 [Qemu-devel] [PATCH] Don't use QEMU_VERSION in ATA/ATAPI replies to IDENTIFY cmds Marc Bevand
2008-09-11 0:30 ` Anthony Liguori
2008-09-11 1:19 ` Marc Bevand [this message]
2008-09-11 1:40 ` Glauber Costa
2008-09-11 3:34 ` Marc Bevand
2008-09-11 8:18 ` Jamie Lokier
2008-09-11 11:44 ` Glauber Costa
2008-09-11 11:56 ` Jamie Lokier
2008-09-11 13:58 ` Paul Brook
2008-09-11 14:11 ` Avi Kivity
2008-09-11 15:16 ` Ian Kirk
2008-09-11 15:55 ` Paul Brook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aaccfcb60809101819r5abe4ce0tb383fa1c3666406c@mail.gmail.com \
--to=m.bevand@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).