Date: Mon, 08 Feb 2021 09:50:33 +0900 From: KIRIYAMA Kazuhiko <kiri@truefc.org> To: Yuri Pankov <yuripv@yuripv.dev> Cc: KIRIYAMA Kazuhiko <kiri@truefc.org>, freebsd-virtualization@freebsd.org Subject: Re: fatal; loader returned error 139 Message-ID: <202102080050.1180oXTn022952@kx.truefc.org> In-Reply-To: <e2cbd053-2c81-27a1-4912-3f178e5bf88f@yuripv.dev> References: <202102050125.1151Pcc6063607@kx.truefc.org> <e2cbd053-2c81-27a1-4912-3f178e5bf88f@yuripv.dev>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 06 Feb 2021 05:14:52 +0900,
Yuri Pankov wrote:
>
> 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@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?
root@vm:~ # lldb -c bhyveload.core -- bhyveload
(lldb) target create "bhyveload" --core "bhyveload.core"
Core file '/root/bhyveload.core' (x86_64) was loaded.
(lldb) thread backtrace all
* thread #1, name = 'bhyveload', stop reason = signal SIGSEGV
* frame #0: 0x0000000a4185c983 userboot.so`strlen + 31
frame #1: 0x0000000a418542c8 userboot.so`strdup + 24
frame #2: 0x0000000a4184e1d1 userboot.so`putenv + 12
frame #3: 0x0000000a4181c887 userboot.so`loader_main + 144
frame #4: 0x0000000000203536 bhyveload`main(argc=<unavailable>, argv=<unavailable>) at bhyveload.c:853:2
frame #5: 0x0000000000202f50 bhyveload`_start(ap=<unavailable>, cleanup=<unavailable>) at crt1_c.c:75:7
(lldb)
>
> > Feb 05 09:50:19: destroying network device tap0
> > Feb 05 09:50:19: stopped
> > root@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@vm.truefc.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
> > root@vm:~ #
> >
> >
> > Is there any suggetions ?
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202102080050.1180oXTn022952>