From owner-freebsd-ports-bugs@freebsd.org Tue Dec 17 11:55:19 2019 Return-Path: Delivered-To: freebsd-ports-bugs@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 4698D1E509A for ; Tue, 17 Dec 2019 11:55:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 47cc5g1FDkz4FyB for ; Tue, 17 Dec 2019 11:55:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 2A9881E5099; Tue, 17 Dec 2019 11:55:19 +0000 (UTC) Delivered-To: ports-bugs@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 2A5B31E5098 for ; Tue, 17 Dec 2019 11:55:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::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.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47cc5g0Lswz4Fy9 for ; Tue, 17 Dec 2019 11:55:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 0765FD828 for ; Tue, 17 Dec 2019 11:55:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id xBHBtINb032256 for ; Tue, 17 Dec 2019 11:55:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xBHBtI0A032255 for ports-bugs@FreeBSD.org; Tue, 17 Dec 2019 11:55:18 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: ports-bugs@FreeBSD.org Subject: [Bug 242684] sysutils/vm-bhyve: service vm stop Date: Tue, 17 Dec 2019 11:55:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bernhard@blberger.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc flagtypes.name Message-ID: 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-ports-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2019 11:55:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242684 Bug ID: 242684 Summary: sysutils/vm-bhyve: service vm stop Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: bernhard@blberger.de CC: churchers@gmail.com Flags: maintainer-feedback?(churchers@gmail.com) CC: churchers@gmail.com I found a problem with VM-BHYVE. VM-BHYVE provides a service vm which starts /stop the VM's on system startup and on system stop.=20 The problem is with shutdown of the host system. The script in /usr/local/etc/rc.d/vm uses "vm stopall" to terminate the VM's.=20 vm stopall sends the VM's the signal to shut down the system. if "vm stopal= l" is done, the script "/usr/local/etc/rc.d/vm" is done, too, so that the shut= down process of the host is continued and this is the problem, because "vm stopa= ll" does not wait until the VM's are really finished and the shutdown processes= of the host are continued, the VM's which are not finished with the schutdown = will be aborted. This leads to broken file systems in the VM's -> fatal they can easily verify that. Start a VM in a shell a: vm -f start test and = now stop the VM: vm stop test in another shell b and you will see that the comm= and in shell b is finished faster and the VM in shell a is still in the shutdown process.=20=20 My suggestion: In the script: /usr/local/lib/vm-bhyve/vm-core=20 in the function core::stopall() or core::stop() to add a check function that waits with the continuation until the VM's are actually finished. so the task: bhyve has disappeared. This way you can make sure that when the host system is stopped, all VM's a= re really stopped. --=20 You are receiving this mail because: You are the assignee for the bug.=