From owner-freebsd-virtualization@freebsd.org Tue Jul 14 13:56:30 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 CBA4C99BE1F for ; Tue, 14 Jul 2015 13:56:30 +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 100429FD for ; Tue, 14 Jul 2015 13:56:29 +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 QAA12591; Tue, 14 Jul 2015 16:56:26 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ZF0h8-0000fW-Cw; Tue, 14 Jul 2015 16:56:26 +0300 Message-ID: <55A514D1.7040805@FreeBSD.org> Date: Tue, 14 Jul 2015 16:55:29 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: "freebsd-virtualization@freebsd.org" Subject: Re: bhyve: centos 7.1 with multiple virtual processors References: <5587EE05.2020001@FreeBSD.org> <558900A7.40609@FreeBSD.org> <55891335.5090403@FreeBSD.org> In-Reply-To: <55891335.5090403@FreeBSD.org> 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: Tue, 14 Jul 2015 13:56:30 -0000 On 23/06/2015 11:05, Andriy Gapon wrote: > On 23/06/2015 10:26, Neel Natu wrote: [snip] >> Does this ever happen with a single vcpu guest? > > Never seen the problem with a single CPU so far. > Also, never had that problem with FreeBSD guests. > >> The other mystery is the NMIs the host is receiving. I (re)verified to >> make sure that bhyve/vmm.ko do not assert NMIs so it has to be >> something else on the host that's doing it ... > > But the correlation with the multi-CPU non-FreeBSD guests seems to be significant. Today I've got another NMI with a Linux guest, but a few things were different: - the host was fresh after a reboot - the guest was single CPU - the NMI happened during boot up of the very first VM kernel: NMI ISA 2c, EISA ff kernel: NMI ... going to debugger Not what causes those NMIs but when they happen they always happen during a bhyve guest boot... -- Andriy Gapon