From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu version updates break Windows activation
Date: Thu, 27 Nov 2008 14:58:17 +0000 [thread overview]
Message-ID: <20081127145817.GK14154@redhat.com> (raw)
In-Reply-To: <492EB0EA.50103@redhat.com>
On Thu, Nov 27, 2008 at 04:38:34PM +0200, Avi Kivity wrote:
> Frederik Himpe wrote:
> >Every time qemu/kvm is updated, the version strings in the virtual
> >hardware change, which breaks an activated windows installation in qemu.
> >Windows thinks it's running on other hardware, and requires manual re-
> >activation by phone.
> >
> >Could the version strings please be made optional in the hardware?
> >
> >
>
> Perhaps we should switch the version strings not to include the qemu
> version, but instead carry their own version numbers, which would bump
> on on incompatible change (presumably, never).
This sounds like a good idea. If a guest really badly wants to know the
QEMU version number, it is already exposed via the SMBIOS data tables,
so its redundant to include in the per-device info too.
NB, this doesn't just impact Windows - when configuring evdev in Linux
it is desirable to configure it to match based on device name, rather
than the unstable path /dev/input/event3. This is only possible if the
device name is stable though, so removing the QEMU version number would
help make more reliable Linux Xorg configs too.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
prev parent reply other threads:[~2008-11-27 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 19:23 [Qemu-devel] qemu version updates break Windows activation Frederik Himpe
2008-11-26 14:59 ` Jamie Lokier
2008-11-26 15:08 ` Paul Brook
2008-11-26 15:09 ` Stefano Stabellini
2008-11-27 14:38 ` Avi Kivity
2008-11-27 14:47 ` Jamie Lokier
2008-11-27 14:58 ` Ben Taylor
2008-11-27 14:58 ` Daniel P. Berrange [this message]
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=20081127145817.GK14154@redhat.com \
--to=berrange@redhat.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).