From: "Andreas Färber" <afaerber@suse.de>
To: Anshul Makkar <anshul.makkar@profitbricks.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] live migration + licensing issue.
Date: Tue, 08 Jul 2014 18:25:23 +0200 [thread overview]
Message-ID: <53BC1B73.4070304@suse.de> (raw)
In-Reply-To: <CAM4NYE_=d_niRDNepo8TPRL_sU7k_r=OLzKTwuFzvi_LXbWtEg@mail.gmail.com>
Hi,
Am 08.07.2014 17:24, schrieb Anshul Makkar:
> In our data center we are using qemu 1.0/ 1.2 and we need to do a live
> migration to qemu 2.0.
>
> One of the main hindrance that we are facing is that QEMU 1.0 uses old
> PC model so if a user using Windows on the VM running on QEMU 1.0 does
> a live migrate to QEMU 2.0 , he will see a licensing issue as after
> migration Windows will see a new hardware beneath it.
>
> Any suggestion as to how to overcome this problem.
Please check the documentation. There's the -machine option with
parameters such as pc-1.0 and pc-1.2 for that exact purpose. libvirt
should supply the corresponding option automatically.
More difficult is if you're trying to migrate from qemu-kvm to qemu -
code changes to your copy of 2.0 will be necessary then.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-07-08 16:25 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 [this message]
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
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=53BC1B73.4070304@suse.de \
--to=afaerber@suse.de \
--cc=anshul.makkar@profitbricks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.