I wasn't entirely sure where to put this, if it is in the wrong forum, please move it to where it belongs.
The boot process fails instantly with the message 'kernel trap 12 with interrupts disabled.' Virtio drivers are loaded. These should be compatible with 9.1-RELEASE.
Otherwise no message precedes or proceeds it.
The system boots fine with kernel.old: 9.0-RELEASE-p3(-p5).
Host system is:
Qemu-kvm is version 1.0.1 and the machine is executed with:
CPU is:
From inside the VM (on 9.0-RELEASE):
It is of course possible that upgrading the host system would fix it. Would be nice to have a confirmation first though.
From what I can find about the error it generally relates to the CPU. If it is the CPU, this would explain why I've previously got 9.1-RELEASE to boot fine on a similar host system but which is equipped with an i7. I do not know if FreeBSD boots on the hardware itself.
Any suggestions are appreciated. Thanks in advance.
The boot process fails instantly with the message 'kernel trap 12 with interrupts disabled.' Virtio drivers are loaded. These should be compatible with 9.1-RELEASE.
Otherwise no message precedes or proceeds it.
The system boots fine with kernel.old: 9.0-RELEASE-p3(-p5).
Host system is:
Code:
nulani@ganglere ~ $ uname -a
Linux ganglere 3.2.11-hardened #1 SMP Sat Jun 23 10:19:39 UTC 2012 x86_64 AMD Opteron(tm) Processor 4228 HE AuthenticAMD GNU/LinuxQemu-kvm is version 1.0.1 and the machine is executed with:
Code:
/usr/bin/qemu-system-x86_64 --enable-kvm -daemonize -name niflheim -pidfile /var/run/vm/niflheim.pid -monitor unix:/var/run/vm/niflheim.unix,server,nowait -cpu host -smp 2 -m 2048 -boot c -drive file=/dev/ganglere/niflheim,cache=none,if=virtio,index=0 -netdev tap,id=guest1 -device virtio-net,netdev=guest1,mac=00:16:3E:96:48:61 -monitor telnet:127.0.0.1:3023,server,nowait -display vnc=127.0.0.1:1CPU is:
Code:
nulani@ganglere ~ $ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 21
model : 1
model name : AMD Opteron(tm) Processor 4228 HE
stepping : 2
microcode : 0x6000624
cpu MHz : 2800.000
cache size : 2048 KB
physical id : 0
siblings : 6
core id : 0
cpu cores : 3
apicid : 16
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 nodeid_msr topoext perfctr_core arat cpb npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
bogomips : 5600.08
TLB size : 1536 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm 100mhzsteps hwpstate [9]
Code:
> dmesg | grep -i CPU
CPU: AMD Opteron(tm) Processor 4228 HE (2800.25-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
SMP: AP CPU #1 Launched!
> sysctl -a | grep -i CPU | more
cpu HAMMER
device cpufreq
kern.ccpu: 0
kern.sched.cpusetsize: 8
<cpu count="2" mask="3">0, 1</cpu>
kern.smp.cpus: 2
kern.smp.maxcpus: 64
net.inet.tcp.per_cpu_timers: 0
debug.cpufreq.verbose: 0
debug.cpufreq.lowest: 0
hw.ncpu: 2
hw.acpi.cpu.cx_lowest: C1
security.jail.param.cpuset.id: 0
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_SB_.CP00
dev.cpu.0.%pnpinfo: _HID=ACPI0007 _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.cx_supported: C1/0
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% last 6488us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_SB_.CP01
dev.cpu.1.%pnpinfo: _HID=ACPI0007 _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/0
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% last 9502usIt is of course possible that upgrading the host system would fix it. Would be nice to have a confirmation first though.
From what I can find about the error it generally relates to the CPU. If it is the CPU, this would explain why I've previously got 9.1-RELEASE to boot fine on a similar host system but which is equipped with an i7. I do not know if FreeBSD boots on the hardware itself.
Any suggestions are appreciated. Thanks in advance.
