[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 0/4] x86/PVH: Dom0 building adjustments

  • To: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Tue, 31 Aug 2021 10:53:59 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=cgeuQQ7IIPihzG5U9FIyFNYN33pFkrsOJM5NqFbgJ/g=; b=DG7ShmEsJjfd8Aav9apFNjFV+RdtfDyUIcDk2Rmg3ZlnQ2+DobUDN76qCZnG8y4WTVToCL9B2Fi6/hBN65Gp9ioPZ1e+fWpS9X/6UQyihWmguYrRwGpzjwFpNX7RxDKGJUXAcMj2jAVA19DKcLuhPUA/udDzTd8eG1aADJ1bDo1qzZvpRhRXyfrO/iOje6oy9KAu+8Dahp6WrGLeRvuxpir5BioEZyN3JJ8IH7EZ8rDJ20ReaG88pztP1OjeN1ZJaY7jBCbC4rDK8ywtDBqxEmUDfnA1rV0ynsbR1Ue2m+QKLyL+9YrWczySz0nNJJ+7OkD5QPSXJH01yxl3ErPNOQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RPi8jQOmty7KQ+1Pf86nF4Q+b1+9VsIUvnCtlt+W0BZwYq28wmiyarvqV5RlomqbcsDAR1+nEN5tZkvgI0WPMoOd0nIc1bfnFS4QWfHPrnlbd8Rrt0CO1ioKqT22QGtMo4mLB1CBv01YOyiIriGtyrf2D5IAL4VXcgdy18yBf79y0z8ECGWmfp1PY4dGttHu1uanmgemvhZIDXtlaGO1ULolGgHCJpOh6rPeHRhCD4o5noYoTkQeU6vyVzbHdMhHVTNn1TGnm4M0cSLLrzgwrGTnP59thVzrpWbn83FNO6BjqAoDv6aMFAAFvq0fNUAsV6PXmRmVEBP/rlW2xZHjRQ==
  • Authentication-results: citrix.com; dkim=none (message not signed) header.d=none;citrix.com; dmarc=none action=none header.from=suse.com;
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • Delivery-date: Tue, 31 Aug 2021 08:54:14 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 30.08.2021 15:01, Jan Beulich wrote:
> The code building PVH Dom0 made use of sequences of P2M changes
> which are disallowed as of XSA-378. First of all population of the
> first Mb of memory needs to be redone. Then, largely as a
> workaround, checking introduced by XSA-378 needs to be slightly
> relaxed.
> Note that with these adjustments I get Dom0 to start booting on my
> development system, but the Dom0 kernel then gets stuck. Since it
> was the first time for me to try PVH Dom0 in this context (see
> below for why I was hesitant), I cannot tell yet whether this is
> due further fallout from the XSA, or some further unrelated
> problem. Dom0's BSP is in VPF_blocked state while all APs are
> still in VPF_down. The 'd' debug key, unhelpfully, doesn't produce
> any output, so it's non-trivial to check whether (like PV likes to
> do) Dom0 has panic()ed without leaving any (visible) output.

Correction: I did mean '0' here, producing merely

(XEN) '0' pressed -> dumping Dom0's registers
(XEN) *** Dumping Dom0 vcpu#0 state: ***
(XEN) *** Dumping Dom0 vcpu#1 state: ***
(XEN) *** Dumping Dom0 vcpu#2 state: ***
(XEN) *** Dumping Dom0 vcpu#3 state: ***

'd' output supports the "system is idle" that was also visible from
'q' output.




Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.