From owner-freebsd-virtualization@freebsd.org Wed Dec 19 19:36:32 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C13E1341E47 for ; Wed, 19 Dec 2018 19:36:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 28D9B6A2FF for ; Wed, 19 Dec 2018 19:36:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E077D1341E40; Wed, 19 Dec 2018 19:36:31 +0000 (UTC) Delivered-To: virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE1F61341E3D for ; Wed, 19 Dec 2018 19:36:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 773746A2F9 for ; Wed, 19 Dec 2018 19:36:31 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7E19F1D38B for ; Wed, 19 Dec 2018 19:36:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id wBJJaUup005672 for ; Wed, 19 Dec 2018 19:36:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id wBJJaUPG005671 for virtualization@FreeBSD.org; Wed, 19 Dec 2018 19:36:30 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 231117] I/O lockups inside bhyve vms Date: Wed, 19 Dec 2018 19:36:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kkc@duckpond.dk X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.29 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, 19 Dec 2018 19:36:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231117 --- Comment #11 from Kristian K. Christensen --- (In reply to Allan Jude from comment #10) I'll give it a shot, but expect it to take a little while to get the output. Let me quickly explain: Currently, the only thing that stops doing io is our bhyve instances running anything 11.2 or newer. (11.1 rarely ever have issues, though it *does* hap= pen, see Niels' comment on how it differs). However, it's the entire instance th= at stops doing io. The zvol simply receives no updates from here on out. Regretably, on 11.2+, it's mostly on production vms we can effectively reproduce it often enough to debug on it, so we tend to roll them back after testing. I can reproduce on test vms, but they crash more infrequently and = thus it could be a long wait. Furthermore, ALL writes stop and any process that wants to write to anything, stalls. This easily gives me a pid to debug wit= h, but very little access to run commands on the vm. The only fix is to kill t= he bhyve pid and start it up again. We can run 11.2+ on the hypervisor, it's o= nly running 11.2+ inside the VM that causes the hang. VMs running UFS do not ha= ng. I'm going to leave a couple of sessions logged in and run procstat and ps fairly often, to keep them in memory, but I suspect it can take me a little= bit to get the required output. I'll get back to you, I'm going to assume zfskern is the most interesting p= id to get output from, but if any random that can't write will do, let me know. --=20 You are receiving this mail because: You are the assignee for the bug.=