From owner-freebsd-virtualization@freebsd.org Mon Feb 8 00:50:46 2021 Return-Path: Delivered-To: freebsd-virtualization@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0674B53EC6B for ; Mon, 8 Feb 2021 00:50:46 +0000 (UTC) (envelope-from kiri@truefc.org) Received: from kx.truefc.org (1.212.52.36.ap.yournet.ne.jp [36.52.212.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp", Issuer "smtp" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DYnWS5bQFz3vWR for ; Mon, 8 Feb 2021 00:50:44 +0000 (UTC) (envelope-from kiri@truefc.org) Received: from kx.truefc.org (kx.truefc.org [36.52.212.1]) by kx.truefc.org (8.16.1/8.16.1) with ESMTP id 1180oXTn022952; Mon, 8 Feb 2021 09:50:34 +0900 (JST) (envelope-from kiri@kx.truefc.org) Message-Id: <202102080050.1180oXTn022952@kx.truefc.org> Date: Mon, 08 Feb 2021 09:50:33 +0900 From: KIRIYAMA Kazuhiko To: Yuri Pankov Cc: KIRIYAMA Kazuhiko , freebsd-virtualization@freebsd.org Subject: Re: fatal; loader returned error 139 In-Reply-To: References: <202102050125.1151Pcc6063607@kx.truefc.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 MULE XEmacs/21.4 (patch 24) (Standard C) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 4DYnWS5bQFz3vWR X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of kiri@truefc.org has no SPF policy when checking 36.52.212.1) smtp.mailfrom=kiri@truefc.org X-Spamd-Result: default: False [-1.87 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[36.52.212.1:from]; FREEFALL_USER(0.00)[kiri]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[truefc.org]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[36.52.212.1:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.966]; RCVD_COUNT_ONE(0.00)[1]; R_SPF_NA(0.00)[no SPF record]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:10013, ipnet:36.52.208.0/21, country:JP]; MAILMAN_DEST(0.00)[freebsd-virtualization]; ONCE_RECEIVED(0.10)[] X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Feb 2021 00:50:46 -0000 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=, argv=) at bhyveload.c:853:2 frame #5: 0x0000000000202f50 bhyveload`_start(ap=, cleanup=) 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" >