From: Ian Jackson <iwj@xenproject.org>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: <xen-devel@lists.xenproject.org>, Wei Liu <wl@xen.org>,
Anthony PERARD <anthony.perard@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v2 for-4.15] x86/msr: introduce an option for HVM relaxed rdmsr behavior
Date: Thu, 4 Mar 2021 15:20:34 +0000 [thread overview]
Message-ID: <24640.64194.445736.52546@mariner.uk.xensource.com> (raw)
In-Reply-To: <YED5Czp+v2xFSCOG@Air-de-Roger>
Roger Pau Monné writes ("Re: [PATCH v2 for-4.15] x86/msr: introduce an option for HVM relaxed rdmsr behavior"):
> On Thu, Mar 04, 2021 at 02:59:38PM +0000, Ian Jackson wrote:
> > I think it's almost as bad to have guests which can be migrated in,
> > but which then cannot reboot.
>
> Ups, yes, right.
>
> > Historically we have taken the view that new Xen must support old
> > guests, even if that means being bug-compatible. So I am strongly in
> > favour of avoiding such a usability regression.
>
> I'm not a xl/libxl expert, but couldn't we set the option in a
> persistent way for migrated-in guests?
>
> IIRC at domain creation libxl knows whether it's a restore or a fresh
> domain, and hence we could set the option there?
>
> The part I'm not sure is about how to make it persistent.
The guest could be stopped with xl shutdown and then recrated with xl
create, from the config file. I don't think we want to break that use
case here either.
Ian.
next prev parent reply other threads:[~2021-03-04 15:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 14:47 [PATCH v2 for-4.15] x86/msr: introduce an option for HVM relaxed rdmsr behavior Roger Pau Monne
2021-03-04 14:59 ` Ian Jackson
2021-03-04 15:13 ` Roger Pau Monné
2021-03-04 15:20 ` Ian Jackson [this message]
2021-03-04 16:55 ` Roger Pau Monné
2021-03-04 17:13 ` Ian Jackson
2021-03-04 17:43 ` Roger Pau Monné
2021-03-04 18:21 ` Ian Jackson
2021-03-05 10:26 ` Jan Beulich
2021-03-04 23:09 ` Boris Ostrovsky
2021-03-04 23:28 ` Andrew Cooper
2021-03-05 8:26 ` Roger Pau Monné
2021-03-05 0:06 ` Andrew Cooper
2021-03-05 9:15 ` Roger Pau Monné
2021-03-05 10:35 ` Jan Beulich
2021-03-05 10:56 ` Jan Beulich
2021-03-05 11:06 ` Jan Beulich
2021-03-08 14:30 ` Roger Pau Monné
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=24640.64194.445736.52546@mariner.uk.xensource.com \
--to=iwj@xenproject.org \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.