bhyve: Abort trap

Евгений IRON iron at mail.ua
Sun Apr 5 03:20:47 UTC 2015


 Hello all,

After I upgraded FreeBSD STABLE up to r281095, I can't boot up VM with CentOS 6.

# uname -a
FreeBSD cobra 10.1-STABLE FreeBSD 10.1-STABLE #8 r281095: Sun Apr 5 05:20:57 EEST 2015 root at cobra:/usr/obj/usr/src/sys/COBRA amd64
# cat bitrix.grub
linux /vmlinuz-2.6.32-504.12.2.el6.x86_64 ro root=/dev/mapper/VolGroup-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD KEYTABLE=us rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16 console=ttyS0 crashkernel=auto rd_LVM_LV=VolGroup/lv_root rd_NO_DM
initrd /initramfs-2.6.32-504.12.2.el6.x86_64.img
boot

# cat bitrix_start.sh
#!/usr/local/bin/bash
 
ifconfig tap0 mtu 9000
ifconfig bridge0 deletem em0
ifconfig bridge0 addm em0 addm tap0
bhyvectl --destroy --vm=bitrix &> /dev/null
grub-bhyve -m device.map -r hd0,msdos1 -M 4096M bitrix < bitrix.grub
bhyve -c 4 -AI -H -P -s 0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap0 -s 3:0,virtio-blk,/dev/zvol/zroot/bitrix -l com1,stdio -m 4096M bitrix


Console output:
.......
CPU: Physical Processor ID: 0
alternatives: switching to unfair spinlock
ACPI: Core revision 20090903
ACPI Exception: AE_NO_ACPI_TABLES, While loading namespace from ACPI tables (20090903/tbxface-605)
ACPI: Unable to load the System Description Tables
ftrace: converting mcount calls to 0f 1f 44 00 00
ftrace: allocating 21919 entries in 86 pages
APIC routing finalized to flat.
..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...
..... (found apic 0 pin 0) ...
....... failed.
...trying to set up timer as Virtual Wire IRQ...
..... failed.
...trying to set up timer as ExtINT IRQ...
Unhandled outb 0x0071
./bitrix_start.sh: line 7: 5202 Abort trap (core dumped) bhyve -c 4 -AI -H -P -s 0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap0 -s 3:0,virtio-blk,/dev/zvol/zroot/bitrix -l com1,stdio -m 4096M bitrix
Tell me please, how can I fix this problem?
I can rebuild kernel with debug enabled and make backtrace of core dump if it will help somehow to find a reason. I guess  281075  commit is the reason.

Thanks a lot!


More information about the freebsd-virtualization mailing list