From owner-freebsd-xen@freebsd.org Sat May 19 11:31:53 2018 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5AB8EAA86F for ; Sat, 19 May 2018 11:31:53 +0000 (UTC) (envelope-from pratiy0100@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 451F76C024; Sat, 19 May 2018 11:31:53 +0000 (UTC) (envelope-from pratiy0100@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id j5-v6so19348997wme.5; Sat, 19 May 2018 04:31:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=zb//Hr/wHCnZLdbFwwIV7cNQjS4a3sSDv1b7fqOgk/4=; b=WffHttQFKyPoD8Tb9aXLKon9aYDiFoeFmg4WiR+dVz+jQyZLS1xParsDO4reoM3fsL 1VrqNsU0zoIz/ZPua7zhCwueylRhjKbixcTk4NjxRWd1+9EBpPhJ3pbjqFVaG9w+2CKc mhI/yBcyZ1hAcA9ZVQPfR2LAh3bMW366mA1Hf1WhslhNlSviD6OugmiH0SdG4dO1Wdm1 JepKudoaIStosyF05UTr9CtiVWl1TDjY6EK5alq7/9s07XUwH/n9VxppYfK0rGqogIlG APiC4g4HTIStf64Ic1T/KUn7gZ0PZpQLV+P0LXY2MqMpe9YxEM8LCdRKu3Vy6r7nft3i CJBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=zb//Hr/wHCnZLdbFwwIV7cNQjS4a3sSDv1b7fqOgk/4=; b=ZwLUyo0TSWMM666Ot3+Eiqw0u63DiWJ7FuD2cJNl0/WDBxSMs/HJWtApn73EhBA8s7 u67wh1EngYa+s+gFbpWjA+pOntLKT0b3UcAQ17Zx0m9iq+6k9Wr/Er0716ifjoLbBgII 3IxPtBZZMx/EafRUZ6Z/BnhJLtJD2tDhUV78p6LYJ4O5N7tMFau0HihelkhdNhbkHGcY K7iE9BZmd7zQwCk8DcEw4OnKiFrZePyk2ZxAWGz34F6mCO1IeUn5cjqXq5ry941AlYmJ X1xWerBKh7XPE9lF8B+p0N3ReFsiK7ybEqf1KDB9oKlFKaQ8erQtVYHxsmTrwkG4Id7A K1vw== X-Gm-Message-State: ALKqPwd+eMvzEFm8GrohLdIo9LIEFKEJaQDt1LkJHoSmT6YvBIz1G7AI nsBE2JXDxn0pLfqN8Q5tKZL+YHt1qxkOb67Gxl4= X-Google-Smtp-Source: AB8JxZp8SzoWAosvHqTLtVqywjhMYOV1clUmYYlQVzazVKR+YkL6nfUWEqGNCr7ZUolPkxDjcc19fvOlpyFFmNYm7ds= X-Received: by 2002:a50:b119:: with SMTP id k25-v6mr16194917edd.217.1526729511532; Sat, 19 May 2018 04:31:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.170.33 with HTTP; Sat, 19 May 2018 04:31:11 -0700 (PDT) In-Reply-To: References: <20180519081030.qhzyjdrpwcekmcac@MacBook-Pro-de-Roger.local> From: Pratyush Yadav Date: Sat, 19 May 2018 17:01:11 +0530 Message-ID: Subject: Re: Xen kernel fails to boot, d0v1 triple fault looks like the cuplrit To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Cc: FreeBSD-Xen , Akshay Jaggi , Edward Napierala Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2018 11:31:54 -0000 On Sat, May 19, 2018 at 3:45 PM, Pratyush Yadav wrot= e: > Hi, > > The line is > > /usr/src/sys/amd64/amd64/mp_machdep.c:307 > > Also, I tried with dom0_max_vcpus=3D1 but it keeps rebooting (despite nor= eboot > in the xen command line) Correction: It boots with dom0_max_vcpus=3D1. It did not boot for me earlier because I was trying to fix it by trying to make Xen from source so I had actually deinstalled it when I tested with max_vcpus=3D1. Now I reinstalled Xen and it works. Thanks for the temporary workaround! Let me know if you want more info about the panic. > > On Sat 19 May, 2018, 1:40 PM Roger Pau Monn=C3=A9, = wrote: >> >> On Fri, May 18, 2018 at 05:29:06PM +0530, Pratyush Yadav wrote: >> > Hi, >> > >> > So I have been trying to get Xen to boot on my laptop. It is getting >> > stuck with the following error messages: >> > >> > (XEN) Scrubbing free RAM on 1 nodes using 4 CPUs >> > (XEN) [VT-D] DMAR: [DMA Read} Request device [0000:00:1a.0] fault addr >> > 9ce13000. iommu reg - ffff82c000203000 >> > (XEN) [VT-D] DMAR: reason 06 - PTE read access is not set >> > (XEN) ........... done >> > (XEN) initial low memory virq threshold set at 0x200 pages. >> > (XEN) Std. Loglevel: All >> > (XEN) Guest Loglevel: All >> > (XEN) Xen is keeping VGA console >> > (XEN) Boot video device 00:02.0 >> > (XEN) ***Serial input -> DOM0 (type 'CTRL-a' three times to switch inp= ut >> > to Xen) >> > (XEN) Freed 320 kB init memory >> > FreeBSD PVH running on xen-3.0-x86_64p >> > Copyright (c) 1992-2018 The FreeBSD Project. >> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, >> > 1994 The regents of the University of California. All rights reserved. >> > FreeBSD is a registered trademark of The FreeBSD Foundation. >> > FreeBSD 12.0-CURRENT #0 r333606: Mon May 14 19:59:08 UTC 2018 >> > >> > root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC = amd64 >> > WARNING: WITNESS option enabled, expect reduced performance. >> > VT(vga): text 80x25 >> > CPU: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (2494.22-MHz K8-class >> > CPU) >> > Origin=3D"GenuineIntel" Id=3D0x306c3 Family=3D0x6 Model=3D0x3c Ste= pping=3D3 >> > >> > Features=3D0x17c1cbf5> > FXSR,SSE,SSE2,HTT> >> > >> > Features2=3D0xf6f83203> > POPCNT,AESNI,XSAVE,AVX,F16C,RDRAND,HV> >> > AMD Features=3D0x20101800NX,LM> >> > AMD Features2=3D0x21< >> > Structured Extended >> > Features=3D0x2329 >> > Hypervisor: Origin =3D "XenVMMXenVMM" >> > real memory =3D 9991770112 (9528 MB) >> > avail memory =3D 7936724992 (7569 MB) >> > (XEN) d0v1 Triple fault - invoking HVM shutdown action 0 >> > (XEN) *** Dumping Dom0 vcpu#1 state: *** >> > (XEN) ----[ Xen-4.7.2 x86_64 debug=3Dn Not tainted ]---- >> > (XEN) CPU: 1 >> > (XEN) RIP: 0020:[] >> > (XEN) RFLAGS: 0000000000010016 CONTEXT: hvm guest (d0v1) >> > (XEN) rax: 0000000000000000 rbx: ffffffff8201c100 rcx: >> > 0000000000000001 >> > (XEN) rdx: 0000000000003078 rsi: ffffffff81b992f8 rdi: >> > fffffe0003bb6078 >> > (XEN) rbp: fffffe00009ffff0 rsp: fffffe00009fffa0 r8: >> > 00000000ffffffff >> > (XEN) r15: 0000000000000400 cr0: 0000000000000011 cr4: >> > 0000000000000020 >> > (XEN) cr3: 00000000035a4000 cr2: 0000000000000ff0 >> > (XEN) ds: 0028 es: 0028 fs: 0028 gs: 0028 ss: 0028 cs: 0020 >> > (XEN) Guest stack trace from rsp=3Dfffffe00009fffa0: >> > (XEN) Fault while accessing guest memory. >> > (XEN) Hardware Dom0 halted: halting machine >> > >> > Any idea why this is happening and how can I fix this? >> >> Can you execute: >> >> addr2line -e /usr/lib/debug/boot/kernel/kernel.debug ffffffff8102042b >> >> This should print a file and line number that would help in order to >> debug what's going on. >> >> Since it seems like the crash is caused by a triple fault on an AP, >> you can try to boot with dom0_max_vcpus=3D1 on the xen_cmdline, that >> might prevent the panic from happening. >> >> We need however to figure out what's going on and fix it. >> >> Thanks, Roger. --=20 Regards, Pratyush Yadav