qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: Anshul Makkar <anshul.makkar@profitbricks.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] live migration + licensing issue.
Date: Wed, 09 Jul 2014 18:17:04 +0200 (CEST)	[thread overview]
Message-ID: <b8cdc66b-65b0-41e8-87e5-2351949ab01a@mailpro> (raw)
In-Reply-To: <CAM4NYE8+ue4+Q4hEAc3VhsH_0i59zWXc0nmPC7un1ZvT8A9oWA@mail.gmail.com>

Hi,

AFAIK this change has occured between the switch from qemu-kvm to qemu. (qemu 1.3 if I remember)

Don't have see license problem after other upgrade (qemu 1.3->1.4->1.5 ...)


But It's always better to use volume licenses, no more problem in case of virtual hardware change.


----- Mail original -----

De: "Anshul Makkar" <anshul.makkar@profitbricks.com>
À: "Markus Armbruster" <armbru@redhat.com>
Cc: "Andreas Färber" <afaerber@suse.de>, "qemu-devel" <qemu-devel@nongnu.org>
Envoyé: Mercredi 9 Juillet 2014 13:09:47
Objet: Re: [Qemu-devel] live migration + licensing issue.

Thanks. I got the point.

Anshul Makkar

On Wed, Jul 9, 2014 at 9:36 AM, Markus Armbruster <armbru@redhat.com> wrote:
> Anshul Makkar <anshul.makkar@profitbricks.com> writes:
>
>> Hi,
>>
>> Yeah, I am aware of this option. But the point where I am concerned is
>> that if Windows VM is running in QEMU 1.0 with pc-model 1.0 and then I
>> upgrade the QEMU to 2.0 and I specify machine as pc-1.2, then Windows
>> will see this as change in hardware and complain about the license.
>
> Works as designed.
>
>> Sorry, if my understanding is wrong here or i am missing something.
>
> Changing the machine type is the virtual equivalent of replacing the
> motherboard.

  reply	other threads:[~2014-07-09 16:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 15:24 [Qemu-devel] live migration + licensing issue Anshul Makkar
2014-07-08 16:25 ` Andreas Färber
2014-07-08 21:10   ` Anshul Makkar
2014-07-09  7:36     ` Markus Armbruster
2014-07-09 11:09       ` Anshul Makkar
2014-07-09 16:17         ` Alexandre DERUMIER [this message]
2014-07-09 16:25         ` Andreas Färber
2014-07-11 10:14           ` Anshul Makkar
2014-07-11 11:09             ` Paolo Bonzini
2014-07-11 11:12             ` Markus Armbruster
2014-07-11 11:50               ` Anshul Makkar
2014-07-11 12:20                 ` Markus Armbruster
2014-07-11 11:52               ` Eduardo Otubo
2014-07-11 12:19                 ` Markus Armbruster
2014-07-11 12:29                   ` Eduardo Otubo
2014-07-11 12:41                     ` Markus Armbruster
2014-07-10 23:19     ` Eric Blake
2014-07-11 10:12       ` Anshul Makkar

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=b8cdc66b-65b0-41e8-87e5-2351949ab01a@mailpro \
    --to=aderumier@odiso.com \
    --cc=afaerber@suse.de \
    --cc=anshul.makkar@profitbricks.com \
    --cc=armbru@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).