Xen Kernel Won't Boot
Roger Pau Monné
roger.pau at citrix.com
Mon Oct 19 15:45:56 UTC 2015
Hello,
El 19/10/15 a les 17.31, Thomas Laus ha escrit:
> 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 at 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)
AFAICT you won't be able to boot a FreeBSD/Xen Dom0 on this box because
FreeBSD Dom0 runs as a PVH guest and it requires an IOMMU (aka VT-d in
Intel speech), which your CPU doesn't seem to support.
A traditional Linux PV Dom0 will work fine, but FreeBSD doesn't support
traditional PV mode. Anyway, see the rest of reply below to figure out
why you weren't able to boot...
> 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<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
> MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> Oct 19 10:55:41 xenserver kernel:
> Features2=0x41d8e3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,x
> TPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,TSCDLT,RDRAND>
> Oct 19 10:55:41 xenserver kernel: AMD
> Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
> Oct 19 10:55:41 xenserver kernel: AMD Features2=0x101<LAHF,Prefetch>
> Oct 19 10:55:41 xenserver kernel: Structured Extended
> Features=0x2282<TSCADJ,SMEP,ERMS,NFPUSG>
> 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: <ATComp GT140130>
> 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.
FWIW, and I know it won't help much now, but you can use:
> unload
> unset xen_kernel
> boot ...
And the loader won't try to load the Xen kernel anymore.
> 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?
Booting a FreeBSD/Xen Dom0 using UEFI is not yet supported, if you want
to use this box as a FreeBSD/Xen Dom0 you will have to switch back to
BIOS boot I'm afraid (although as noted above I think your CPU is
missing a feature in order to run a FreeBSD/Xen Dom0).
Roger.
More information about the freebsd-xen
mailing list