From owner-freebsd-current@FreeBSD.ORG  Tue Feb 17 04:10:08 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@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 B578C855;
 Tue, 17 Feb 2015 04:10:08 +0000 (UTC)
Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 97A0223F;
 Tue, 17 Feb 2015 04:10:08 +0000 (UTC)
Received: from [192.168.200.212] (unknown [50.136.155.142])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 (Authenticated sender: sbruno@ignoranthack.me)
 by mail.ignoranthack.me (Postfix) with ESMTPSA id DA401192A3B;
 Tue, 17 Feb 2015 04:10:06 +0000 (UTC)
Message-ID: <54E2BF1E.4090002@ignoranthack.me>
Date: Mon, 16 Feb 2015 20:10:06 -0800
From: Sean Bruno <sbruno@ignoranthack.me>
Reply-To: sbruno@freebsd.org
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject: Xen HVM Panic, HEAD
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Feb 2015 04:10:08 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

https://people.freebsd.org/~sbruno/Xen_APIC_panic.png

I suspect that there may be one or two more lines above this that are
relevant to this panic, but XENHVM kernel's now panic booting on Xen
server.  The working kernel output looks like this:

FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
XEN: Hypervisor version 4.2 detected.
CPU: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz (2400.05-MHz
K8-class CPU)
  Origin="GenuineIntel"  Id=0x206c2  Family=0x6  Model=0x2c  Stepping=2
 Features=0x1783fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT>
 Features2=0x81ba2201<SSE3,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,HV>
  AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
Hypervisor: Origin = "XenVMMXenVMM"
real memory  = 1434451968 (1368 MB)
avail memory = 1353293824 (1290 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <Xen HVM>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  2
ioapic0: Changing APIC ID to 1
MADT: Forcing active-low polarity and level trigger for SCI


bcc: royger@
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQF8BAEBCgBmBQJU4r8bXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kOTcH/R4jzSNBELU+Jc1E0N7b97wS
pRzbL69AQaDnjI8yCHvMX9AwmqC1x4Fd+bpk4Xqf9Aut9SHZTUhlZlw3BAqZfPmj
ofPaaDn3B4AUIMW/K1yPUE7tup1GlM+hSdX4czoBzzO3wKC5aBz4qgv+Peb2FMDe
LwEoeWpbJFu5y11uITN0en08bdRAg7B+gJCPkPbzY+W6m0RKpWJ8PavXNfxlMTYt
WQThTEy8SdRIPQRdAKURYSqWAPkfMP2s07h4Ckm9rXybbLWCQBYMwJZxhcDfXWlz
EoYLHoQ2nt0dT3Lu9lxH8EppCZpVQRAnVLYYB6tBpeDt9boNpNxoJ0UuOf906AM=
=EspR
-----END PGP SIGNATURE-----