qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu version updates break Windows activation
Date: Thu, 27 Nov 2008 14:47:42 +0000	[thread overview]
Message-ID: <20081127144742.GI18400@shareable.org> (raw)
In-Reply-To: <492EB0EA.50103@redhat.com>

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).

Microsoft Virtual PC lets you override the version strings and UUIDs
yourself for some things, I think.  They are in the XML VM description
file, which is what you click on start a VM.

This is helpful for moving existing VM images from one hypervisor to
another without needing Windows re-activation.  VMware probably does
the same, to be able to run Virtual PC images unchanged.

-- Jamie

  reply	other threads:[~2008-11-27 14:47 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 [this message]
2008-11-27 14:58     ` Ben Taylor
2008-11-27 14:58   ` Daniel P. Berrange

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=20081127144742.GI18400@shareable.org \
    --to=jamie@shareable.org \
    --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).