From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Error booting Xen
Date: Wed, 3 Feb 2016 11:57:02 -0500
Message-ID: <20160203165702.GD22750@char.us.oracle.com>
References: <56A8D03E02000078000CB8B8@prv-mh.provo.novell.com>
	<CAPtdW16eY_3QEbBM+9xDd9XBKCjhKSqUO5_RiCBpD6X1V5ZxJQ@mail.gmail.com>
	<56A8E20C02000078000CB944@prv-mh.provo.novell.com>
	<CAPtdW17ZmY_ctuU4Uqcsbke8ohN9BF3M-0RrVjSnvkCsSPLzoQ@mail.gmail.com>
	<56AB495C02000078000CC4F5@prv-mh.provo.novell.com>
	<1454487813.9227.187.camel@citrix.com>
	<CAPtdW168nOxjM-DWOb4g1zNR32q_3ThPWDHhhHNRcJM_vPWt3g@mail.gmail.com>
	<1454504139.9227.285.camel@citrix.com>
	<56B1FC2B.3060005@citrix.com>
	<1454505446.9227.298.camel@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <1454505446.9227.298.camel@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Shuai Ruan <shuai.ruan@linux.intel.com>, Harmandeep Kaur <write.harmandeep@gmail.com>, Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

On Wed, Feb 03, 2016 at 02:17:26PM +0100, Dario Faggioli wrote:
> On Wed, 2016-02-03 at 13:10 +0000, Andrew Cooper wrote:
> > On 03/02/16 12:55, Dario Faggioli wrote:
> > >=A0
> > > tbox login: (d1) mapping kernel into physical memory
> > > (d1) about to get started...
> > > (XEN) traps.c:2684:d1v0 Domain attempted WRMSR 00000000c0000081
> > > from 0xe023e00800000000 to 0x0023001000000000.
> > > (XEN) traps.c:2684:d1v0 Domain attempted WRMSR 00000000c0000082
> > > from 0xffff82d0bfffe080 to 0xffffffff817ef990.
> > > (XEN) traps.c:2684:d1v0 Domain attempted WRMSR 00000000c0000083
> > > from 0xffff82d0bfffe0a0 to 0xffffffff817f1f60.
> > > (XEN) traps.c:2684:d1v0 Domain attempted WRMSR 0000000000000174
> > > from 0x000000000000e008 to 0x0000000000000010.
> > > (XEN) traps.c:2684:d1v0 Domain attempted WRMSR 0000000000000175
> > > from 0xffff83026d40ffc0 to 0x0000000000000000.
> > > (XEN) traps.c:2684:d1v0 Domain attempted WRMSR 0000000000000176
> > > from 0xffff82d08023eaf0 to 0xffffffff817f1d60.
> > > (XEN) traps.c:2684:d1v0 Domain attempted WRMSR 00000000c0000084
> > > from 0x0000000000074700 to 0x0000000000047700.
> > > (XEN) traps.c:2684:d1v1 Domain attempted WRMSR 00000000c0000081
> > > from 0xe023e00800000000 to 0x0023001000000000.
> > > (XEN) traps.c:2684:d1v1 Domain attempted WRMSR 00000000c0000082
> > > from 0xffff82d0bffff000 to 0xffffffff817ef990.
> > > (XEN) traps.c:2684:d1v1 Domain attempted WRMSR 00000000c0000083
> > > from 0xffff82d0bffff020 to 0xffffffff817f1f60.
> > > (XEN) traps.c:2684:d1v1 Domain attempted WRMSR 0000000000000174
> > > from 0x000000000000e008 to 0x0000000000000010.
> > > (XEN) traps.c:2684:d1v1 Domain attempted WRMSR 0000000000000175
> > > from 0xffff8300866fffc0 to 0x0000000000000000.
> > > (XEN) traps.c:2684:d1v1 Domain attempted WRMSR 0000000000000176
> > > from 0xffff82d08023eaf0 to 0xffffffff817f1d60.
> > > (XEN) traps.c:2684:d1v1 Domain attempted WRMSR 00000000c0000084
> > > from 0x0000000000074700 to 0x0000000000047700.
> > > =

> > > Because this is what you just said above, and that's... well...
> > > just
> > > impossible?!?! :-O
> > =

> > This is a Linux PV trying to set up the SYSCALL/SYSENTER MSRs when it
> > shouldn't.=A0=A0There is a fix upstream, but this specifically is
> > harmless
> > noise.
> > =

> That's ok... What we're arguing is that is happens as a consequence of
> a domain being created, not just "by itself, after boot, without
> starting any domain" !!!! :-)

It has booted. It says 'about to get started...' which is in the early
code of the Linux pvops.