From owner-freebsd-xen@freebsd.org Mon Oct 19 15:33:03 2015 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08118A195AC for ; Mon, 19 Oct 2015 15:33:03 +0000 (UTC) (envelope-from lausts@acm.org) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) by mx1.freebsd.org (Postfix) with ESMTP id C417F148D for ; Mon, 19 Oct 2015 15:33:01 +0000 (UTC) (envelope-from lausts@acm.org) Received: from [173.88.10.122] ([173.88.10.122:22511] helo=mail.laus.org) by cdptpa-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 15/E4-01181-AEC05265; Mon, 19 Oct 2015 15:31:55 +0000 Received: from [192.168.1.100] (laust2 [192.168.1.100]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id t9JFVsJf039381 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Mon, 19 Oct 2015 11:31:54 -0400 (EDT) (envelope-from lausts@acm.org) X-Authentication-Warning: mail.laus.org: Host laust2 [192.168.1.100] claimed to be [192.168.1.100] From: "Thomas Laus" Organization: ABB To: freebsd-xen@freebsd.org Date: Mon, 19 Oct 2015 11:31:49 -0400 Subject: Xen Kernel Won't Boot Reply-to: lausts@acm.org Message-ID: <56250CE5.17484.2086AC@lausts.acm.org> Priority: normal X-mailer: Pegasus Mail for Windows (4.70) X-RR-Connecting-IP: 107.14.168.118:25 X-Cloudmark-Score: 0 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: Mon, 19 Oct 2015 15:33:03 -0000 List: I have a new installation of FreeBSD Current that won't boot the Xen kernel. I loaded the most recent snapshot and then ran 'svnup' to bring my source tree up to date on Saturday 10/17/2015. I followed the instructions on the FreeBSD Wiki page on setting up Dom0 support. I made the changes to sysconf.conf, /etc/ttys, /boot/loader.conf and generated a new /boot/menu.rc.local. When the computer was rebooted, it would not load the Xen boot file and choked giving me the OK? prompt. This is my dmesg output showing the CPU information: Oct 19 10:55:41 xenserver kernel: FreeBSD 11.0-CURRENT #0: Sun Oct 18 04:21:24 EDT 2015 Oct 19 10:55:41 xenserver kernel: root@xenserver:/usr/obj/usr/src/sys/XENSERVER amd64 Oct 19 10:55:41 xenserver kernel: FreeBSD clang version 3.7.0 (tags/RELEASE_370/final 246257) 20150906 Oct 19 10:55:41 xenserver kernel: WARNING: WITNESS option enabled, expect reduced performance. Oct 19 10:55:41 xenserver kernel: VT(efifb): resolution 1280x1024 Oct 19 10:55:41 xenserver kernel: CPU: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz (2000.05-MHz K8-class CPU) Oct 19 10:55:41 xenserver kernel: Origin="GenuineIntel" Id=0x30673 Family=0x6 Model=0x37 Stepping=3 Oct 19 10:55:41 xenserver kernel: Features=0xbfebfbff Oct 19 10:55:41 xenserver kernel: Features2=0x41d8e3bf Oct 19 10:55:41 xenserver kernel: AMD Features=0x28100800 Oct 19 10:55:41 xenserver kernel: AMD Features2=0x101 Oct 19 10:55:41 xenserver kernel: Structured Extended Features=0x2282 Oct 19 10:55:41 xenserver kernel: VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID Oct 19 10:55:41 xenserver kernel: TSC: P-state invariant, performance statistics Oct 19 10:55:41 xenserver kernel: real memory = 4294967296 (4096 MB) Oct 19 10:55:41 xenserver kernel: avail memory = 3997675520 (3812 MB) Oct 19 10:55:41 xenserver kernel: Event timer "LAPIC" quality 600 Oct 19 10:55:41 xenserver kernel: ACPI APIC Table: Oct 19 10:55:41 xenserver kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs Oct 19 10:55:41 xenserver kernel: FreeBSD/SMP: 1 package(s) x 4 core(s) Oct 19 10:55:41 xenserver kernel: cpu0 (BSP): APIC ID: 0 Oct 19 10:55:41 xenserver kernel: cpu1 (AP): APIC ID: 2 Oct 19 10:55:41 xenserver kernel: cpu2 (AP): APIC ID: 4 Oct 19 10:55:41 xenserver kernel: cpu3 (AP): APIC ID: 6 Having a non-functioning entry in /boot/loader.conf is a tough one to recover and requires booting to a live filesystem. Loading one of the working kernels still loads the same loader.conf. This motherboard uses UEFI and was installed with a UEFI kernel. This computer was able to successfully load the Citrix XenServer 6.5 and had all 'green' lights when I ran 'xl dmesg'. I used another hard drive for the Citrix load. It seemed to be happy with all of my CPU and hardware features. I was able to make a DomU image from an OpenBSD 5.8 snapshot. I have been running FreeBSD since version 4.11 and would prefer not to run the Citrix XenServer because of all of it's 'Linux-isms'. Their filesystem uses Logical Volume Manager and I much prefer ZFS for disk management. Is there any other information that should be sent to this list? Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF