From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Error booting Xen Date: Wed, 3 Feb 2016 13:10:03 +0000 Message-ID: <56B1FC2B.3060005@citrix.com> References: <1453389242.3116.106.camel@citrix.com> <56A6344C02000078000CAA56@prv-mh.provo.novell.com> <56A7815502000078000CB147@prv-mh.provo.novell.com> <56A7B98C02000078000CB3B8@prv-mh.provo.novell.com> <56A8D03E02000078000CB8B8@prv-mh.provo.novell.com> <56A8E20C02000078000CB944@prv-mh.provo.novell.com> <56AB495C02000078000CC4F5@prv-mh.provo.novell.com> <1454487813.9227.187.camel@citrix.com> <1454504139.9227.285.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1454504139.9227.285.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Dario Faggioli , Harmandeep Kaur Cc: xen-devel@lists.xen.org, Jan Beulich , Shuai Ruan List-Id: xen-devel@lists.xenproject.org On 03/02/16 12:55, Dario Faggioli wrote: > On Wed, 2016-02-03 at 17:05 +0530, Harmandeep Kaur wrote: >> On Wed, Feb 3, 2016 at 1:53 PM, Dario Faggioli >> wrote: >>> >> Maybe I failed to shutdown a guest which was showing up >> on next boot. But there are no auto-starting guests. >> Following link goes to latest serial log >> http://paste2.org/5PDz9bP1 >> > No, sorry, I probably am not getting. Are you saying that, just booting > Xen and *not* doing anything else --either from SSH, from the keyboard > of that box, from serial connection... anything at all-- and without > any guest configured to auto start itself, results in these lines to > appear on your serial console? > > 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. There is a fix upstream, but this specifically is harmless noise. ~Andrew