fatal; loader returned error 139

[Yuri Pankov]

KIRIYAMA Kazuhiko wrote:
> Hi, all
> 
> Yesterday, I've updated 14.0-CURRENT and tried to start VM,
> filed to start with "loader returned error 139". VM log is
> as follows :
> 
> root at vm:~ # tail -20 /vm/msrvkxb/vm-bhyve.log
> Feb 05 09:50:18: initialising
> Feb 05 09:50:18:  [loader: bhyveload]
> Feb 05 09:50:18:  [cpu: 2]
> Feb 05 09:50:18:  [memory: 4GB]
> Feb 05 09:50:18:  [hostbridge: standard]
> Feb 05 09:50:18:  [com ports: com1]
> Feb 05 09:50:18:  [uuid: c5ff2511-298f-11eb-9dae-0cc47ab3cfd4]
> Feb 05 09:50:18:  [utctime: yes]
> Feb 05 09:50:18:  [debug mode: no]
> Feb 05 09:50:18:  [primary disk: disk0.img]
> Feb 05 09:50:18:  [primary disk dev: file]
> Feb 05 09:50:19: initialising network device tap0
> Feb 05 09:50:19: setting mtu of tap0 to 9000
> Feb 05 09:50:19: adding tap0 -> vm-local (local addm)
> Feb 05 09:50:19: bring up tap0 -> vm-local (local addm)
> Feb 05 09:50:19: booting
> Feb 05 09:50:19: bhyveload -c /dev/nmdm-msrvkxb.1A -m 4GB -e autoboot_delay=3 -d /vm/msrvkxb/disk0.img msrvkxb
> Feb 05 09:50:19: fatal; loader returned error 139

That would normally mean process was killed by SIGSEGV (128 + 11 for 
signal); was a core dumped somewhere?

> Feb 05 09:50:19: destroying network device tap0
> Feb 05 09:50:19: stopped
> root at vm:~ # uname -a
> FreeBSD vm.truefc.org 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n244626-cb7cc72c546e: Thu Feb  4 17:12:09 JST 2021     admin at vm.truefc.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
> root at vm:~ #
> 
> 
> Is there any suggetions ?