From owner-freebsd-virtualization@freebsd.org Sun Sep 20 21:00:17 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 C67D9A05487 for ; Sun, 20 Sep 2015 21:00:17 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A172E1251 for ; Sun, 20 Sep 2015 21:00:17 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8KL0HVA048798 for ; Sun, 20 Sep 2015 21:00:17 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201509202100.t8KL0HVA048798@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-virtualization@FreeBSD.org Subject: Problem reports for freebsd-virtualization@FreeBSD.org that need special attention X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Date: Sun, 20 Sep 2015 21:00:17 +0000 Content-Type: text/plain; charset="UTF-8" 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: Sun, 20 Sep 2015 21:00:17 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 202321 | [bhyve,patch] More verbose error reporting in bhy New | 202322 | [bhyve,patch] add option to have bhyve write its 2 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Tue Sep 22 06:06:11 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 05D3AA05D52 for ; Tue, 22 Sep 2015 06:06:11 +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 59E7617B5 for ; Tue, 22 Sep 2015 06:06:06 +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 JAA28729; Tue, 22 Sep 2015 09:05:58 +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 1ZeGiE-0009hD-2O; Tue, 22 Sep 2015 09:05:58 +0300 Subject: Re: bhyve: centos 7.1 with multiple virtual processors To: Neel Natu References: <5587EE05.2020001@FreeBSD.org> <558900A7.40609@FreeBSD.org> <55891335.5090403@FreeBSD.org> <55A514D1.7040805@FreeBSD.org> Cc: "freebsd-virtualization@freebsd.org" From: Andriy Gapon X-Enigmail-Draft-Status: N1110 Message-ID: <5600EF8D.2070109@FreeBSD.org> Date: Tue, 22 Sep 2015 09:05:01 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: 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, 22 Sep 2015 06:06:11 -0000 On 15/07/2015 10:02, Neel Natu wrote: > > Could you update the host with the following patch? > https://people.freebsd.org/~neel/patches/ktr_stray_nmi.patch > > It enables KTR_GEN logging by default and turns it off when a VM-exit > due to NMI is detected. If there is a pattern to the NMIs then it can > be correlated with the guest activity around that time. Neel, sorry that it took so long to gather the additional data. Yesterday I got another host NMI while running a VM with KTR turned on. I panic-ed the system from the debugger prompt after the NMI. Below is several dozen of last messages taken from the crash dump. It does not look like there was a guest NMI or, at least, it didn't get a chance to be logged. Please let me know if the full log dump would be more useful. Initially, the last reported address 0x7f8c1185129b looked suspicious to me, but grepping the dump for 'extintr' I see many addresses like that. $ ktrdump -N /boot/kernel.dn/kernel -M /var/crash/vmcore.21 | head -40 index trace ------ ----- 253313 vm centos7[0]: Resume execution at 0x7f8c1185129b 253312 vm centos7[0]: vmcb clean 0x3bf 253311 vm centos7[0]: handled extintr vmexit at 0x7f8c1185129b/0 253310 vm centos7[0]: Resume execution at 0xffffffff8105059c 253309 vm centos7[0]: vmcb clean 0x3bf 253308 vm centos7[0]: Guest interrupt blocking cleared due to rip change: 0xffffffff81050596/0xffffffff8105059c 253307 vm centos7[0]: vcpu state changed from frozen to running 253306 vm centos7[0]: nextrip updated to 0xffffffff8105059c after instruction decoding 253305 vm centos7[0]: inst_emul fault accessing gpa 0xfed000f0 253304 vm centos7[0]: vcpu state changed from running to frozen 253303 vm centos7[0]: unhandled nptfault vmexit at 0xffffffff81050596/0 253302 vm centos7[0]: inst_emul fault for gpa 0xfed000f0/0x100000004 at rip 0xffffffff81050596 253301 vm centos7[0]: Resume execution at 0xffffffff8105058f 253300 vm centos7[0]: vmcb clean 0x3bf 253299 vm centos7[0]: Guest interrupt blocking cleared due to rip change: 0xffffffff8105058d/0xffffffff8105058f 253298 vm centos7[0]: vcpu state changed from frozen to running 253297 vm centos7[0]: nextrip updated to 0xffffffff8105058f after instruction decoding 253296 vm centos7[0]: inst_emul fault accessing gpa 0xfed00108 253295 vm centos7[0]: vcpu state changed from running to frozen 253294 vm centos7[0]: unhandled nptfault vmexit at 0xffffffff8105058d/0 253293 vm centos7[0]: inst_emul fault for gpa 0xfed00108/0x100000006 at rip 0xffffffff8105058d 253292 vm centos7[0]: Resume execution at 0xffffffff8105057c 253291 vm centos7[0]: vmcb clean 0x3bf 253290 vm centos7[0]: Guest interrupt blocking cleared due to rip change: 0xffffffff81050576/0xffffffff8105057c 253289 vm centos7[0]: vcpu state changed from frozen to running 253288 vm centos7[0]: nextrip updated to 0xffffffff8105057c after instruction decoding 253287 vm centos7[0]: inst_emul fault accessing gpa 0xfed000f0 253286 vm centos7[0]: vcpu state changed from running to frozen 253285 vm centos7[0]: unhandled nptfault vmexit at 0xffffffff81050576/0 253284 vm centos7[0]: inst_emul fault for gpa 0xfed000f0/0x100000004 at rip 0xffffffff81050576 253283 vm centos7[0]: Resume execution at 0xffffffff8104accc 253282 vm centos7[0]: vmcb clean 0x3b7 253281 vm centos7[0]: Clearing V_IRQ interrupt injection 253280 vm centos7[0]: Guest interrupt blocking cleared due to rip change: 0xffffffff8104acc6/0xffffffff8104accc 253279 vm centos7[0]: vcpu state changed from frozen to running 253278 vm centos7[0]: vlapic_update_ppr 0x00 253277 vm centos7[0]: vlapic_process_eoi isr7 0x00000000 253276 vm centos7[0]: vlapic_process_eoi isr6 0x00000000 And a snippet from the stack-trace: ... #9 0xffffffff8081ed84 in trap (frame=0xfffffe01dc531f30) at /usr/src/sys/amd64/amd64/trap.c:372 #10 0xffffffff808074e3 in nmi_calltrap () at /usr/src/sys/libkern/explicit_bzero.c:28 #11 0xffffffff81c92327 in enable_gintr () at /usr/src/sys/modules/vmm/../../amd64/vmm/amd/svm.c:1895 #12 0xffffffff81c91c57 in svm_vmrun (arg=0xfffffe006d29c000, vcpu=0, rip=-2130377316, pmap=0xfffff801e4771138, evinfo=0xfffffe02b8c45820) at /usr/src/sys/modules/vmm/../../amd64/vmm/amd/svm.c:2022 #13 0xffffffff81c7661e in vm_run (vm=0xfffffe0076277000, vmrun=0xfffff8013fe43000) at /usr/src/sys/modules/vmm/../../amd64/vmm/vmm.c:1643 #14 0xffffffff81c79b78 in vmmdev_ioctl (cdev=, cmd=, data=0xfffff8013fe43000 "", fflag=-1, td=0x0) at /usr/src/sys/modules/vmm/../../amd64/vmm/vmm_dev.c:392 ... -- Andriy Gapon From owner-freebsd-virtualization@freebsd.org Tue Sep 22 17:30:04 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 28BB3A0671F for ; Tue, 22 Sep 2015 17:30:04 +0000 (UTC) (envelope-from bsd-src@helfman.org) Received: from mail-io0-f177.google.com (mail-io0-f177.google.com [209.85.223.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F29541628 for ; Tue, 22 Sep 2015 17:30:03 +0000 (UTC) (envelope-from bsd-src@helfman.org) Received: by ioii196 with SMTP id i196so21575236ioi.3 for ; Tue, 22 Sep 2015 10:29:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to:content-type; bh=r8r2Ozdv69Pt+TxygK9qSU26mxFos3G4FSMo73VT68U=; b=aHsPPHCSdOZ0OQu+RCbm9X5nTntV/WBE8gkQw7Hsahz69Cwjg9QGPLplgn/GwM8qlu 2OInEeuxdYWy49XMww45+u/nb92eCL7Kw9y9Qv9Zd6A5AjhNiaZdmDqg09oZ7iDdPW4g 5Ov3mSYXVxcXWYB8AmY2U7vZ9LRxyBc/s/Y8H5iBBs2dxFFUUG/R+JbtsJzi9wexqPs0 xDrM+EfEPfHsd8lkSO9kEaMGPg1jg7I2/WMP5a/TY5Ea5TzWKMI/7zFkVVL0dv/3qIpD uf/gWORrpbq0F+6xMtfdBkCfk18gjYjEuIsFqP5KrkpXr1FSI3FPHaCiFqfQFC7FgNux JOKQ== X-Gm-Message-State: ALoCoQk9QcQh5Ic7kDO50aHPF8CAK6AQnCVoSaMOWnxhyX5gZeW9Xzu7k9iGfUkN2aIGi8a1nOC7 MIME-Version: 1.0 X-Received: by 10.107.19.234 with SMTP id 103mr38048091iot.41.1442942996824; Tue, 22 Sep 2015 10:29:56 -0700 (PDT) Sender: bsd-src@helfman.org Received: by 10.107.56.193 with HTTP; Tue, 22 Sep 2015 10:29:56 -0700 (PDT) Date: Tue, 22 Sep 2015 10:29:56 -0700 X-Google-Sender-Auth: W70-y5xwfKC6vRB9mXdy2RRteR4 Message-ID: Subject: virtualization ports From: Jason Helfman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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, 22 Sep 2015 17:30:04 -0000 I have a number of ports that I maintain, that I really never use but at one time I did. Initially, I put them into the portstree to help out the community, with the idea that I would be using them one day, however I work at a VMware shop, and the likelihood of me using this software is looking far less likely. I was wondering if it would be okay to assign these ports to virtualization group? deskutils/virt-manager devel/libvirt devel/libvirt-glib devel/libvirt-java devel/py-libvirt devel/spice-protocol net-mgmt/virt-viewer Thanks, Jason -- Jason Helfman | FreeBSD Committer jgh@FreeBSD.org | http://people.freebsd.org/~jgh | The Power to Serve From owner-freebsd-virtualization@freebsd.org Thu Sep 24 07:32:37 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 798B4A08343 for ; Thu, 24 Sep 2015 07:32:37 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 183D71C3F; Thu, 24 Sep 2015 07:32:37 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by lacao8 with SMTP id ao8so53863553lac.3; Thu, 24 Sep 2015 00:32:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=SrKuXfkCoHC6QZyPFQ6s2Pbgy7MRrecrI5th/y2IR0c=; b=LJVc7BarKQwLTGPHz4F9hvEtKPwz/LpplYCj5ohelckwSaO9bJWVdTBp23JlIZnMdN Q20WWwMvbIdhtnkQzv4hN7HtG3Q5WY13QtTmixVmIQlH48Uc5zd2gp/7lGwkplyNS0R5 m0YaKp4CYY13NRdLgqkCrcko9VWP1S6b5SjHEgd1DgAq2+hQDj3roP1YCwQ4EfOHIOcW yFjWmEtrWxsS+VsUdAUWGisfmk6U5Ky77zmQz4kQ5JJnKzz3DctgldQyfLMbos8T8HlT Sma6Ey43BaUkU5BsU+39UIkwBty6G2NAiFr72B3RofXhPyrrLFSueSQTeK/XHLRBmtKy A0kw== X-Received: by 10.112.236.3 with SMTP id uq3mr12907911lbc.69.1443079953793; Thu, 24 Sep 2015 00:32:33 -0700 (PDT) Received: from dev.san.ru (dev.san.ru. [88.147.129.60]) by smtp.gmail.com with ESMTPSA id a138sm1082744lfe.19.2015.09.24.00.32.32 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Sep 2015 00:32:33 -0700 (PDT) Date: Thu, 24 Sep 2015 10:32:25 +0300 From: Roman Bogorodskiy To: Jason Helfman Cc: "freebsd-virtualization@freebsd.org" Subject: Re: virtualization ports Message-ID: <20150924073223.GA88752@dev.san.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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: Thu, 24 Sep 2015 07:32:37 -0000 Jason Helfman wrote: > I have a number of ports that I maintain, that I really never use but at > one time I did. Initially, I put them into the portstree to help out the > community, with the idea that I would be using them one day, however I work > at a VMware shop, and the likelihood of me using this software is looking > far less likely. I was wondering if it would be okay to assign these ports > to virtualization group? > > deskutils/virt-manager > devel/libvirt > devel/libvirt-glib > devel/libvirt-java > devel/py-libvirt > devel/spice-protocol > net-mgmt/virt-viewer FWIW, I could take care of libvirt, py-libvirt, libvirt-glib and virt-manager. Roman Bogorodskiy From owner-freebsd-virtualization@freebsd.org Thu Sep 24 16:59:48 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 1A0E3A06A5C for ; Thu, 24 Sep 2015 16:59:48 +0000 (UTC) (envelope-from bsd-src@helfman.org) Received: from mail-ig0-f174.google.com (mail-ig0-f174.google.com [209.85.213.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E0C4D10BA for ; Thu, 24 Sep 2015 16:59:47 +0000 (UTC) (envelope-from bsd-src@helfman.org) Received: by igbkq10 with SMTP id kq10so19773136igb.0 for ; Thu, 24 Sep 2015 09:59:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=W5r/rW0hEFqwAJ73XmevU/8V7bfxSf/aE3bc2QhrvGg=; b=TkgesJOlK5tXog4Kscb0CdAE6JNkyP2LH7vx1P8eyYnRzYJ5wWGtQ7VLdGbveqF3k2 0Jhl78muUL65fv3C00K6Ew77GNjx3Yr0wmLgqybPwQSci7H/1KW0+YYIi16COczRM46G LMMBprkOeJTlAOGLq/Ky8tZoQ/kUPawAjJi6PQRvEzsU7RnNJozaXPC7N3RAnQ0itDRG rpX+isu+WRxFzTZipRSHtt7jw8lEf8tLLzTxWLA6c5uVeJT/N5DL1jPAPZPCP6wzqNCN IumxP+71/AsUmqOicrtMl5SCLLpRsr+C5oTi47nBRtgujMLqvYMXDEU/XYljdpGVrUmD Vbag== X-Gm-Message-State: ALoCoQkVMRvXPKTQfTkXcmh2byQbzNDf/BZMckajAk1B8/2VLTjDNvbN2FxeYnG5JHsWMMin1O8Q MIME-Version: 1.0 X-Received: by 10.50.64.146 with SMTP id o18mr1709917igs.81.1443113980846; Thu, 24 Sep 2015 09:59:40 -0700 (PDT) Sender: bsd-src@helfman.org Received: by 10.107.56.193 with HTTP; Thu, 24 Sep 2015 09:59:40 -0700 (PDT) In-Reply-To: <20150924073223.GA88752@dev.san.ru> References: <20150924073223.GA88752@dev.san.ru> Date: Thu, 24 Sep 2015 09:59:40 -0700 X-Google-Sender-Auth: mB4Y5dIOJK8Pel0QLsCilUo94_Y Message-ID: Subject: Re: virtualization ports From: Jason Helfman To: Roman Bogorodskiy Cc: Jason Helfman , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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: Thu, 24 Sep 2015 16:59:48 -0000 On Thu, Sep 24, 2015 at 12:32 AM, Roman Bogorodskiy wrote: > Jason Helfman wrote: > > > I have a number of ports that I maintain, that I really never use but at > > one time I did. Initially, I put them into the portstree to help out the > > community, with the idea that I would be using them one day, however I > work > > at a VMware shop, and the likelihood of me using this software is looking > > far less likely. I was wondering if it would be okay to assign these > ports > > to virtualization group? > > > > deskutils/virt-manager > > devel/libvirt > > devel/libvirt-glib > > devel/libvirt-java > > devel/py-libvirt > > devel/spice-protocol > > net-mgmt/virt-viewer > > FWIW, I could take care of libvirt, py-libvirt, libvirt-glib and > virt-manager. > > Roman Bogorodskiy > > Sounds good, thanks! Additionally, if you are going to take virt-manager, you really should take spice-protocol and virt-viewer as they are dependencies and require updates for virt-manager. Thoughts? -jgh -- Jason Helfman | FreeBSD Committer jgh@FreeBSD.org | http://people.freebsd.org/~jgh | The Power to Serve