From owner-freebsd-virtualization@freebsd.org Wed Nov 11 08:25:42 2015 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37FCEA1F854 for ; Wed, 11 Nov 2015 08:25:42 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 7E4DF1C97 for ; Wed, 11 Nov 2015 08:25:40 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA26529 for ; Wed, 11 Nov 2015 10:25:39 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ZwQio-000G7j-VF for freebsd-virtualization@freebsd.org; Wed, 11 Nov 2015 10:25:39 +0200 To: "freebsd-virtualization@freebsd.org" From: Andriy Gapon Subject: bhyve vtblk error X-Enigmail-Draft-Status: N1110 Message-ID: <5642FB32.1040006@FreeBSD.org> Date: Wed, 11 Nov 2015 10:24:18 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.20 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: Wed, 11 Nov 2015 08:25:42 -0000 The following happened with an illumos VM in bhyve. Usually I reboot that VM by first powering it off using illumos 'poweroff' command. But yesterday I tried to do that using 'reboot' command. Apparently in that case illumos performs a warm reboot where a new kernel instance is executed without the full hardware reset and firmware boot. So, I got the following error in the guest during the reboot: Block device: blkdev@0,0, blkdev0 blkdev0 is /pci@0,0/pci1af4,2@4/blkdev@0,0 /pci@0,0/pci1af4,2@4/blkdev@0,0 (blkdev0) online WARNING: blkdev0: Invalid media block size (0) WARNING: blkdev0: Invalid media block size (0) NOTICE: Cannot read the pool label from '/pci@0,0/pci1af4,2@4/blkdev@0,0:a' NOTICE: spa_import_rootpool: error 5 Cannot mount root on /pci@0,0/pci1af4,2@4/blkdev@0,0:a fstype zfs At the same time bhyve printed the following message: vtblk: read from CFGVEC: bad size 4 P.S. There is another problem that perhaps is worth some attention as well. The guest paniced after it failed to import the root pool. bhyve got stuck in a weird way after that: vm exit[2] vm exit[1] vm exit[3] reason SVM rip 0xfffffffffb8440aa inst_length 0 exitcode 0x7f exitinfo1 0 exitinfo2 0 reason SVM rip 0xfffffffffb8440aa inst_length 0 exitcode 0x7f exitinfo1 0 exitinfo2 0 reason SVM rip 0xfffffffffb8440aa inst_length 0 exitcode 0x7f exitinfo1 0 exitinfo2 0 ^T load: 0.98 cmd: bhyve 87140 [suspended] 20861.13r 643.47u 41127.33s 0% 3727592k As you can see the process somehow became suspended and I was not able to recover it (SIGKILL didn't help) and had to reboot the host. -- Andriy Gapon