From: Cheyenne Wills <cheyenne.wills@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: XSA-351 causing Solaris-11 systems to panic during boot.
Date: Tue, 17 Nov 2020 07:43:29 -0700 [thread overview]
Message-ID: <CAHpsFVcy2n2Sr845mPw4txH5UTbtKrbezRtgdmDaDX0T2r5wog@mail.gmail.com> (raw)
In-Reply-To: <7bca24cb-a3af-b54d-b224-3c2a316859dd@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
The Solaris version reported in the copyright banner on the ISO is SunOS
Release 5.11 Version 11.4.0.15.0 64-bit
My existing guest solaris systems are also at the same release/version level
At the time of the panic, the panic log reports that the rcx register
contains '0606' (this was from my notes yesterday). If additional
information is needed, I will need a bit more time to set up my system
again.
On Tue, Nov 17, 2020 at 1:12 AM Jan Beulich <jbeulich@suse.com> wrote:
> On 16.11.2020 22:57, Cheyenne Wills wrote:
> > Running Xen with XSA-351 is causing Solaris 11 systems to panic during
> > boot. The panic screen is showing the failure to be coming from
> > "unix:rdmsr". The panic occurs with existing guests (booting off a disk)
> > and the booting from an install ISO image.
> >
> > I discussed the problem with "andyhhp__" in the "#xen" IRC channel and he
> > requested that I report it here.
>
> Thanks. What we need though is information on the specific MSR(s) that
> will need to have workarounds added: We surely would want to avoid
> blindly doing this for all that the XSA change disallowed access to.
> Reproducing the panic screen here might already help; proper full logs
> would be even better.
>
> Jan
>
[-- Attachment #2: Type: text/html, Size: 1674 bytes --]
next prev parent reply other threads:[~2020-11-17 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 21:57 XSA-351 causing Solaris-11 systems to panic during boot Cheyenne Wills
2020-11-17 8:12 ` Jan Beulich
2020-11-17 14:43 ` Cheyenne Wills [this message]
2020-11-17 14:46 ` Andrew Cooper
2020-12-17 1:51 ` boris.ostrovsky
2020-12-17 7:40 ` Jan Beulich
2020-12-17 16:25 ` boris.ostrovsky
2020-12-17 16:46 ` Andrew Cooper
2020-12-17 17:49 ` boris.ostrovsky
2020-12-18 20:43 ` boris.ostrovsky
2020-12-21 8:21 ` Jan Beulich
2020-12-21 16:21 ` boris.ostrovsky
2020-12-21 16:55 ` Jan Beulich
2020-11-17 10:50 ` Roger Pau Monné
2020-11-17 12:54 ` Roger Pau Monné
2020-11-17 13:59 ` Cheyenne Wills
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=CAHpsFVcy2n2Sr845mPw4txH5UTbtKrbezRtgdmDaDX0T2r5wog@mail.gmail.com \
--to=cheyenne.wills@gmail.com \
--cc=jbeulich@suse.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 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.