xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
	xen-devel@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [RFC] xen/pvh: detect PVH after kexec
Date: Tue, 21 Mar 2017 12:53:07 +0100	[thread overview]
Message-ID: <87var2978c.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20170321100115.c52rcfmhopgkbczd@dhcp-3-128.uk.xensource.com> (Roger Pau Monne's message of "Tue, 21 Mar 2017 10:01:15 +0000")

Roger Pau Monne <roger.pau@citrix.com> writes:

> On Tue, Mar 21, 2017 at 10:21:52AM +0100, Vitaly Kuznetsov wrote:
>> Boris Ostrovsky <boris.ostrovsky@oracle.com> writes:
>> 
>> > On 03/20/2017 02:20 PM, Vitaly Kuznetsov wrote:
>> >> PVH guests after kexec boot like normal HVM guests and we're not entering
>> >> xen_prepare_pvh()
>> >
>> > Is it not? Aren't we going via xen_hvm_shutdown() and then
>> > SHUTDOWN_soft_reset which would restart at the same entry point as
>> > regular boot?
>> 
>> No, we're not doing regular boot: from outside of the guest we don't
>> really know where the new kernel is placed (as guest does it on its
>> own). We do soft reset to clean things up and then guest jumps to the
>> new kernel starting point by itself.
>> 
>> We could (in theory, didn't try) make it jump to the PVH starting point
>> but we'll have to at least prepare the right boot params for
>> init_pvh_bootparams and this looks like additional
>> complication. PVHVM-style startup suits us well but we still need to be
>> PVH-aware.
>
> We are going to have the same issue when booting PVH with OVMF, Linux will be
> started at the native UEFI entry point, and we will need some way to detect
> that we are running in PVH mode.
>
> What issues do you see when using the HVM boot path for kexec?

The immediate issue I ran into was ballooning driver over-allocating
with XENMEM_populate_physmap:

(XEN) Dom15 callback via changed to Direct Vector 0xf3
(XEN) d15v0 Over-allocation for domain 15: 262401 > 262400
(XEN) memory.c:225:d15v0 Could not allocate order=0 extent: id=15 memflags=0 (175 of 512)
(XEN) d15v0 Over-allocation for domain 15: 262401 > 262400
(XEN) memory.c:225:d15v0 Could not allocate order=0 extent: id=15 memflags=0 (0 of 512)
(XEN) d15v0 Over-allocation for domain 15: 262401 > 262400
...

I didn't investigate why it happens, setting xen_pvh=1 helped. Not sure
if it's related, but I see the following code in __gnttab_init():

	/* Delay grant-table initialization in the PV on HVM case */
	if (xen_hvm_domain() && !xen_pvh_domain())
		return 0;

and gnttab_init() is later called in platform_pci_probe().

-- 
  Vitaly

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-03-21 11:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 18:20 [RFC] xen/pvh: detect PVH after kexec Vitaly Kuznetsov
2017-03-20 20:21 ` Boris Ostrovsky
2017-03-21  9:21   ` Vitaly Kuznetsov
2017-03-21 10:01     ` Roger Pau Monne
2017-03-21 10:07       ` Roger Pau Monne
2017-03-21 10:07       ` Jan Beulich
2017-03-21 10:21         ` Roger Pau Monne
2017-03-21 10:42           ` Jan Beulich
2017-03-21 10:59             ` Roger Pau Monne
2017-03-21 11:00             ` Andrew Cooper
2017-03-21 11:53       ` Vitaly Kuznetsov [this message]
2017-03-21 12:13         ` Roger Pau Monne
2017-03-21 14:05           ` Boris Ostrovsky
2017-03-21 14:16             ` Roger Pau Monne
2017-03-21 15:01               ` Boris Ostrovsky
2017-03-21 14:35             ` Vitaly Kuznetsov
2017-03-21 14:44         ` Vitaly Kuznetsov
2017-03-21 15:14           ` Boris Ostrovsky
2017-03-21 17:10             ` Vitaly Kuznetsov
2017-03-21 17:28               ` Roger Pau Monne

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=87var2978c.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=roger.pau@citrix.com \
    --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 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).