From owner-freebsd-xen@FreeBSD.ORG Fri May 22 16:11:38 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 717C954B for ; Fri, 22 May 2015 16:11:38 +0000 (UTC) Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (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 E84A319E6 for ; Fri, 22 May 2015 16:11:37 +0000 (UTC) Received: by lbbqq2 with SMTP id qq2so16177558lbb.3 for ; Fri, 22 May 2015 09:11:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=YO5WOSY5lhWR4T547QHrv7tbrcBxYugmuaAMtKfKrjg=; b=hZN9T6zoh7FkjIY+2L3Kdka6Eqc8L0mrL3FaWD5WZBtnEl1eDljHZ8FLtEjugq/spN 8sO8OOfGmh08S775WG60MpJU8uG/a9528ZDPNVli7qj4Q7Z0J086nzn6Tbmxh5jx/bt1 52CsA9gL5BQz9HMQRAAqS3bpLFj7rncnRMBwuR0vi5exQuSV5m/+cpslgoE+Ru+f4HWq qS18zq1U1HKiJKt9QSfRFqsZh92nYAKG1J48psQk8IL3VRS26sdsHQUJr1AQ4LVI8YCI BZXtTcK3RqLA9VJoxVU4xHUct3iR66RcgTz3WVad3zpj3AsFTQcdAJb7v6Fb4Xs0ziiK 5M2A== X-Received: by 10.152.19.198 with SMTP id h6mr7069162lae.62.1432311096034; Fri, 22 May 2015 09:11:36 -0700 (PDT) Received: from kloomba ([217.65.211.144]) by mx.google.com with ESMTPSA id j1sm585729lbc.15.2015.05.22.09.11.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 May 2015 09:11:35 -0700 (PDT) Sender: Roman Bogorodskiy Date: Fri, 22 May 2015 19:11:19 +0300 From: Roman Bogorodskiy To: Roger Pau =?iso-8859-1?Q?Monn=E9?= Cc: "Eggert, Lars" , "freebsd-xen@freebsd.org" Subject: Re: Xen dom0 crash Message-ID: <20150522161117.GA59488@kloomba> References: <7CB114B9-B666-4764-86B6-B94F07973389@netapp.com> <5559EB2E.6080609@citrix.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <5559EB2E.6080609@citrix.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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: Fri, 22 May 2015 16:11:38 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Roger Pau Monn=E9 wrote: > El 18/05/15 a les 15.04, Eggert, Lars ha escrit: > > Hi, > >=20 > > I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xe= n crashes when starting the kernel. Log below; any ideas? > >=20 > > Thanks, > > Lars > > (XEN) ----[ Xen-4.6-unstable x86_64 debug=3Dy Not tainted ]---- > > (XEN) CPU: 0 > > (XEN) RIP: 0000:[] > > (XEN) RFLAGS: 0000000000000200 CONTEXT: hvm guest (d0v0) > > (XEN) rax: 0000000000000000 rbx: ffff82d0802e8000 rcx: ffff82d0802e= ff80 > > (XEN) rdx: ffff82d0801e1500 rsi: 0000000000000000 rdi: ffff82d0801e= d77c > > (XEN) rbp: ffff82d0801061d2 rsp: ffffffff81bb5000 r8: ffff83103ff0= 0000 > > (XEN) r9: ffff82d08010623f r10: ffff82d0802eff70 r11: 000000000000= 0000 > > (XEN) r12: ffff82d0802eff50 r13: ffff831033ae7000 r14: ffff83103ff0= 0000 > > (XEN) r15: ffff82d08018eae3 cr0: 0000000080000011 cr4: 000000000000= 0020 > > (XEN) cr3: 0000000001ba1000 cr2: 0000000000000000 > > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: 0000 > > (XEN) Guest stack trace from rsp=3Dffffffff81bb5000: > > (XEN) Fault while accessing guest memory. > > (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds. > > (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. >=20 > Hello, >=20 > This looks very similar to the crash reported at: >=20 > https://lists.freebsd.org/pipermail/freebsd-xen/2015-April/002315.html >=20 > Which was also reported at xen-devel, but nobody seems to have looked > into it. >=20 > Could you send a bug report to xen-devel with the following trace > (please make sure to mention PVH in the subject line) CCing the Intel > VT-X maintainers? (the emails are in the MAINTAINERS file in the Xen > source tree). H, I'm observing a crash that looks similar to me: (XEN) ----[ Xen-4.5.0 x86_64 debug=3Dn Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: 0020:[] (XEN) RFLAGS: 0000000000010246 CONTEXT: hvm guest (XEN) rax: fffff800d887c1b0 rbx: fffff8000ed85100 rcx: 0000000000000000 (XEN) rdx: ffffffff81788560 rsi: 0000000000000008 rdi: fffff8000ed85100 (XEN) rbp: fffffe023956a850 rsp: fffffe023956a850 r8: ffffffff815056f8 (XEN) r9: ffffffff8178857c r10: fffff8000ea9e0f0 r11: ffffffff81664200 (XEN) r12: 0000000000000004 r13: ffffffff80ee832b r14: fffff8000ed85118 (XEN) r15: fffff8000ed85100 cr0: 000000008005003b cr4: 00000000000406e0 (XEN) cr3: 0000000002cca000 cr2: 000000080a8da140 (XEN) ds: 003b es: 003b fs: 0013 gs: 001b ss: 0028 cs: 0020 (XEN) Guest stack trace from rsp=3Dfffffe023956a850: (XEN) Fault while accessing guest memory. (XEN) Domain 0 crashed: rebooting machine in 5 seconds. (XEN) Resetting with ACPI MEMORY or I/O RESET_REG. I'm wondering if it's related to the same issue? It's triggered only when I try to reboot/poweroff the guest. Roman Bogorodskiy --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVX1UlAAoJEMltX/4IwiJqLLIH/3elbMEjmNSebPx/Uph1ryEn yYP4CwBQLPZY1t8LN9gpBFUeKOjDctVLJW1XcuX4nxlvvA8y0xrqUX+4TErvMya2 a0TjRtCK63YE656Zxda4tTkEEfQ2M9KpRIhHl8zsQdYO1CU0XKZIjYi8AVqL7QeE LhAST663wmeYAmZJo/sSHdxN0n87EISiRhKdTNcOAZMVg56JyXYGrRSstUDPfnsY lt/+h3ai6YmAe1p5Ctbr9y/qS9fHoexZPiv/5BY1Ua4PFkgd/2JxpfgRzYVUIkoL L2BvlmG5HioNEAzka6Pi5W7aNsME1SPQgTleBsPKHm3zH+5rpe00N6w6gUsB36w= =IRwS -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm--