From owner-freebsd-virtualization@freebsd.org Sun Apr 21 04:40:32 2019 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 55ACD1581836 for ; Sun, 21 Apr 2019 04:40: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 CCF578AD37 for ; Sun, 21 Apr 2019 04:40:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 90F7B1581833; Sun, 21 Apr 2019 04:40: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 7EA1F1581832 for ; Sun, 21 Apr 2019 04:40: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 1B5AC8AD35 for ; Sun, 21 Apr 2019 04:40: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 4CCE2DF77 for ; Sun, 21 Apr 2019 04:40: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 x3L4eU0c051641 for ; Sun, 21 Apr 2019 04:40:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3L4eUnj051640 for virtualization@FreeBSD.org; Sun, 21 Apr 2019 04:40: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 237429] bhyve not stable Date: Sun, 21 Apr 2019 04:40:28 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc bug_status keywords 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: Sun, 21 Apr 2019 04:40:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |virtualization@FreeBSD.org CC| |virtualization@FreeBSD.org Status|New |Open Keywords| |needs-qa, performance --- Comment #1 from Kubilay Kocak --- Thank you for the report. Could you please provide more information on the system, in particular: - Exact freebsd version (uname -a) - /var/run/dmesg.boot (as an attachment) - pciconf -lv output (as an attachment) - list of running processes when the system (or guest) is performing slowly= (as an attachment) - top -t output (as an attachment), during guest slowdown (when the perform= ance issue is apparenty) - /etc/rc.conf contents (as an attachment, sanitized if necessary) - complete host/guest bhyve vm configurations, including cpu/memory/disk confirations for the guests (as an attachment) Reduction of the test/reproduction case, and steps to reproduce are going t= o be critical to progressing this issue. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Sun Apr 21 04:51:45 2019 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 C8D251581E6E for ; Sun, 21 Apr 2019 04:51:45 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 D86A78B3A4 for ; Sun, 21 Apr 2019 04:51:44 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=Message-ID:Subject:To:From:Date:In-Reply-To; bh=TQA7Rfncy8DCtlaQr2Ir6ajPj/e6HSgoLLNe0y6KUw0=; b=mCD6WbvhRmurH6bny+BlI60WUe e+EI+uNfpkIRE1DpNVgICnmsmoBoiRS+o7BJ/YgiTeMde+0LxkCYEZKaionW93IXhT/A+ars1wzQC laKiNP51UMMgBJpvs5E22oqyc2rJ7bjGKyFG226ebYnE65l7OGOYcUZtqjvriKAz5uHQ=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hI4S7-000CpI-JS for freebsd-virtualization@freebsd.org; Sun, 21 Apr 2019 11:51:43 +0700 Date: Sun, 21 Apr 2019 11:51:43 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Message-ID: <20190421045143.GA49101@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Sun, 21 Apr 2019 04:51:46 -0000 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dear Colleages, I've noticed that it takes too long for Windows 2012 and 2016 servers guests to shutdown when I issue "vm stopall," several minutes even. Does vm-bhyve provide a way to power them off ungracefully if they would not stop within a predefined time? Or is there perhaps a way to tune the guest OSes to react more promptly to an ACPI shutdown? My primary concern is that my UPS and "apcupsd --kill-on-powerfail" give me about 30 seconds of grace time before the power supply is cut out. It is not sufficient for the bhyve box to shutdown shutdown properly because it waits for the guests to shutdown. If you know of a better way to configure apcupsd so that it powers down the UPS only after all the guest OSes and other daemons are safely down, I'd appreciate that too. For some reason, apctest does not allow me to change the grace period, perhaps this model does not support it. And it would mean a race condition anyway. --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcu/bfAAoJEA2k8lmbXsY0hhsH/3TXUJMWrIIgRUcrXRpmZgNq n6DVqTn3lmVFBTwiHV75WNCHCvd+Epd00dLKE41+dImfwKAWl68U1p7L9/lpdO0j Jh3vMFLAbVGxuoCC+2z6L16d15UklCUxiLB7kN27KqfgDxCOgXS8nfvX027aFc4T r6vUCPnVWfmV8rvW0ky9O/Bx6o4FWc2U5v3LEwxqWy7aGzQAFcBP5gIqWF7id3YE ebmlUXytGdaGGfm8Zr/GKjwa6B/5Onjm6NaAdqeqUKIzYZj750u3kWr9NC+AJyow BCbnXNJWZWFzL4q5eASLUmmgXDddBFY+RWTM7NXKcnSXmR8ZVnIghJRjGbUi1lY= =mge6 -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- From owner-freebsd-virtualization@freebsd.org Sun Apr 21 05:34:17 2019 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 8609F1582D01 for ; Sun, 21 Apr 2019 05:34:17 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0958B8C4EC for ; Sun, 21 Apr 2019 05:34:17 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-ot1-x32c.google.com with SMTP id e5so7204728otk.12 for ; Sat, 20 Apr 2019 22:34:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aDIoITiuUZmlLx0LJGSEY0zY6WUzBV7H+xbrWlTdg5U=; b=e8MwTks3iUDzsuFR2oH8YftriCFZ1HIYn+mGwEw9Yf8jCt5gXKe7eYvGOPgZewntOR 1g5qDKfC7ymZm4snzirQ1c9l0KdXKFxX0OMgz2D6nBd48XFwHyU473fwsCchnyy5iND0 z5v4Emo7OnCJxbENLYUWittOEH8Z1MbXSH1xHe/7h6mfddg7HYhq4XXFC4jel93t31U6 3JLgKiyAxUiK+mbxfaj4zvcRCHffrTDw1LCRqXw/WnywBGR9ea7PBImLZjlaOS53JWxU T/cX1LUpF98b7Zr8es208eEOUBagvNjjgRtL3nyQOWNmpkBX3PqZ367K58XSV/2EJ+eu bIfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aDIoITiuUZmlLx0LJGSEY0zY6WUzBV7H+xbrWlTdg5U=; b=Sbj0iIzQV52jQ3uQjXzXqZCsbhATQeiFn7wMm0CEd22lyFKf2snnp8m4yNaH65xj4k 1K+bMl0FDxDQa6KqmedAJyt5eEK/D0iDrEWSU6Ip5g9LOyfaOWvawQ7y7en7jjfJ3PYj yJKwthJAeuqoKSVG4wf22zIdQbFr0e2K9kYvzuOeJaTXvY6Or3z9DBYlVIiGv8I+ENOy PNDTHx9V8dYfm2vIleXe0Toyqhw29kTC9mtOTNnDA56QYgnc1BNFuSH3wPxHEcOCJ88r rNDCuZJHtHhMbexIHKMNuQ1x3E+DI1t3iN6bM29xtkZ93cwy5iwlqc7o+qkl0MS318Pv YM/g== X-Gm-Message-State: APjAAAXCa4Em10Kvh5NO9LcqhByRt5UVV1uH6zwCUpi7EITvTX43KDTe 7+4QOZXIC9hFHUlBA2URR9orR7RDv7/J5fjm0YyhCA== X-Google-Smtp-Source: APXvYqxWb8dcCJgcCuZVZ3hzR8VQj2v2oxyN3jY6SkZIMGgOo9ZQV7cPM649BMsm1jeRRN1llFb0EVsynqQpSNxTK3Q= X-Received: by 2002:a9d:604c:: with SMTP id v12mr6919620otj.247.1555824856104; Sat, 20 Apr 2019 22:34:16 -0700 (PDT) MIME-Version: 1.0 References: <20190421045143.GA49101@admin.sibptus.ru> In-Reply-To: <20190421045143.GA49101@admin.sibptus.ru> From: Jason Tubnor Date: Sun, 21 Apr 2019 15:34:05 +1000 Message-ID: Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop To: Victor Sudakov Cc: freebsd-virtualization@freebsd.org X-Rspamd-Queue-Id: 0958B8C4EC X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.974,0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Sun, 21 Apr 2019 05:34:17 -0000 On Sun., 21 Apr. 2019, 2:51 pm Victor Sudakov, wrote: > > > Does vm-bhyve provide a way to power them off ungracefully if they would > not stop within a predefined time? > You'd have to do your own checking but to force an instant power off of a guest simply execute: vm poweroff {guest} Cheers. > From owner-freebsd-virtualization@freebsd.org Sun Apr 21 06:10:46 2019 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 60F721583620 for ; Sun, 21 Apr 2019 06:10:46 +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 EF2918D01A for ; Sun, 21 Apr 2019 06:10:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AF228158361E; Sun, 21 Apr 2019 06:10:45 +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 9C94C158361C for ; Sun, 21 Apr 2019 06:10:45 +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 388168D014 for ; Sun, 21 Apr 2019 06:10:45 +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 77988EC56 for ; Sun, 21 Apr 2019 06:10:44 +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 x3L6AiMC056300 for ; Sun, 21 Apr 2019 06:10:44 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3L6AiHs056294 for virtualization@FreeBSD.org; Sun, 21 Apr 2019 06:10:44 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 237429] bhyve: Performance regression after 12 upgrade Date: Sun, 21 Apr 2019 06:10:44 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc 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: Sun, 21 Apr 2019 06:10:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|bhyve not stable |bhyve: Performance | |regression after 12 upgrade --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sun Apr 21 07:17:43 2019 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 3BE39158492D for ; Sun, 21 Apr 2019 07:17:43 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 A15328EA3E for ; Sun, 21 Apr 2019 07:17:42 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=1w7D9q+jl7xMiZBPKxR6n5tw+N9yeRzwr2mBKQhdZnI=; b=Sw7r34QvCKwljolyQNvipB7dXy IV8yIcCOht5Iec3vYR2WSPrmMaXqKlvfuHEdXzXgMaOLdUe76guQqaXUFhOzTRebMbHPCL0wjRaBp /A5njsoF+xUa1H7fS3kDxIaDCblTFdwB3+1vElcR8xKivnwojZ0W40lvx6PBfquBompk=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hI6jN-000DOv-IY for freebsd-virtualization@freebsd.org; Sun, 21 Apr 2019 14:17:41 +0700 Date: Sun, 21 Apr 2019 14:17:41 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Message-ID: <20190421071741.GA51438@admin.sibptus.ru> References: <20190421045143.GA49101@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Sun, 21 Apr 2019 07:17:43 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Jason Tubnor wrote: > On Sun., 21 Apr. 2019, 2:51 pm Victor Sudakov, wrote: >=20 > > > > > > Does vm-bhyve provide a way to power them off ungracefully if they would > > not stop within a predefined time? > > >=20 > You'd have to do your own checking but to force an instant power off of a > guest simply execute: >=20 > vm poweroff {guest} I don't need an *instant* poweroff, I need a poweroff only if a VM would not stop gracefully within a predefined time. Of course this should not be done manually but from the rc.d/vm script on shutdown. --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcvBkVAAoJEA2k8lmbXsY0g2oH/1Si05FrDsPEJXtnzZogrQJY KnkYBOfxXrlS4hr3uQXO0x4i/MlzDIahitYbJqSnaIb/nPWiK5A1bcaLwqCNIhjF +NJdfjQUTnUXfhTD9S1g1V/ITm/uP0WcKag5XBruR5FTIZhc68gQz3S4bzsGzZ0w lVcS0d9/8lZutobBiaIaJV0u4ioGfE/BwOg8t/5lmW8W75OSOWmZTB0yySIWaeCL 2HpsDiGuSN8gRF/K8tsAv0BHkJYvY9QWUgCDLXSQ0RcZsmVvCh39b8oWOrCKyy9H s2Xnu4KNF/tpd0wMsFupsIF5A6VQhC/saAz09azpvo74W7l1WC2iDC8+ojrof08= =nCrh -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- From owner-freebsd-virtualization@freebsd.org Sun Apr 21 14:32:36 2019 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 995DB158E80A for ; Sun, 21 Apr 2019 14:32:36 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F89473A5B for ; Sun, 21 Apr 2019 14:32:35 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x3LEWX4W027754; Sun, 21 Apr 2019 07:32:33 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x3LEWXqF027753; Sun, 21 Apr 2019 07:32:33 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904211432.x3LEWXqF027753@gndrsh.dnsmgr.net> Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop In-Reply-To: <20190421071741.GA51438@admin.sibptus.ru> To: Victor Sudakov Date: Sun, 21 Apr 2019 07:32:33 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 0F89473A5B X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.978,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,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: Sun, 21 Apr 2019 14:32:36 -0000 -- Start of PGP signed section. > Jason Tubnor wrote: > > On Sun., 21 Apr. 2019, 2:51 pm Victor Sudakov, wrote: > > > > > > > > > > > Does vm-bhyve provide a way to power them off ungracefully if they would > > > not stop within a predefined time? > > > > > > > You'd have to do your own checking but to force an instant power off of a > > guest simply execute: > > > > vm poweroff {guest} > > I don't need an *instant* poweroff, I need a poweroff only if a VM would > not stop gracefully within a predefined time. > > Of course this should not be done manually but from the rc.d/vm script > on shutdown. vm shutdown {guest} & (sleep N && vm poweroff {guest}) & A bit hackish, but that should work, if the guest has shutdown by the time you get to the poweroff an error might occur. This spawns a few processes, but is non blocking and highly parallel. One thing I noted, you said rc.d/vm, so I am assuming your actually using the vm-bhyve port, in which case it has a sequential shutdown with time delays between each guest. vm_delay specifically, and it shuts vm's down in reverse order of the startup. That is more likely your problem in that your sending these acpi shutdown requests one at a time, and they should be broadcast in the "power going out" case. It may be possile to adjust vm_delay to 0 and have that be better, though I have not locked at the code. You may also wish to discuss the issue with the vm-bhyve maintainer and maybe a "lights out" procedure needs to be added. > Victor Sudakov, VAS4-RIPE, VAS47-RIPN Regards, -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Sun Apr 21 15:46:18 2019 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 740ED158FF2D for ; Sun, 21 Apr 2019 15:46:18 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 C9B107606A for ; Sun, 21 Apr 2019 15:46:17 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=AOp9YVHPeM93GxVBeta587xG7h+r9TGQwbXOWsaJkW4=; b=Mpm0Y6dh3fR62lwyLdYDLg7fGq 0XAVXEghKXWxwI1TTuihbYE9mVj9crhjXcK8EM1aSSp5tl718RqR+cYNRx8ehUcYSnAFc42IdAC0S 9zQsi+ZOpGLGLN3qwT29is7w9sji8duul51YCIULiqeVkDoz36lopMBvTEuLERpTxxYk=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hIEfY-000FSV-AC for freebsd-virtualization@freebsd.org; Sun, 21 Apr 2019 22:46:16 +0700 Date: Sun, 21 Apr 2019 22:46:16 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Message-ID: <20190421154616.GA59283@admin.sibptus.ru> References: <20190421071741.GA51438@admin.sibptus.ru> <201904211432.x3LEWXqF027753@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Kj7319i9nmIyA2yE" Content-Disposition: inline In-Reply-To: <201904211432.x3LEWXqF027753@gndrsh.dnsmgr.net> X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Sun, 21 Apr 2019 15:46:18 -0000 --Kj7319i9nmIyA2yE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Rodney W. Grimes wrote: > -- Start of PGP signed section. > > Jason Tubnor wrote: > > > On Sun., 21 Apr. 2019, 2:51 pm Victor Sudakov, w= rote: > > >=20 > > > > > > > > > > > > Does vm-bhyve provide a way to power them off ungracefully if they = would > > > > not stop within a predefined time? > > > > > > >=20 > > > You'd have to do your own checking but to force an instant power off = of a > > > guest simply execute: > > >=20 > > > vm poweroff {guest} > >=20 > > I don't need an *instant* poweroff, I need a poweroff only if a VM would > > not stop gracefully within a predefined time. > >=20 > > Of course this should not be done manually but from the rc.d/vm script > > on shutdown. >=20 > vm shutdown {guest} & > (sleep N && vm poweroff {guest}) & >=20 > A bit hackish, but that should work, if the guest has > shutdown by the time you get to the poweroff an error > might occur. This spawns a few processes, but is > non blocking and highly parallel. Thank you, I might give it a try though it would involve hacking the rc.d/vm script. > =20 > One thing I noted, you said rc.d/vm, so I am assuming your actually > using the vm-bhyve port,=20 Yes, I thought that was pretty obvious from the Subject line. > in which case it has a sequential shutdown > with time delays between each guest. vm_delay specifically, and it > shuts vm's down in reverse order of the startup. >=20 > That is more likely your problem in that your sending these acpi > shutdown requests one at a time, and they should be broadcast in > the "power going out" case. Whence is the idea that "vm stopall" does a sequential shutdown? What sense would that make?=20 A sequential startup does make sense but a sequential shutdown? Useless I think. The man page says that=20 stopall Stop all running virtual machines. This sends a stop command = to all bhyve(8) instances, regardless of whether they were starti= ng using vm or not. >=20 > It may be possile to adjust vm_delay to 0 and have that be better, > though I have not locked at the code. You may also wish to discuss > the issue with the vm-bhyve maintainer and maybe a "lights out" > procedure needs to be added. Even if there is a single Windows 2012 or 2016 guest running, it takes the vm several minutes to transition to the "stopped" state. --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --Kj7319i9nmIyA2yE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcvJBIAAoJEA2k8lmbXsY0Ip0H/0u28Ug63LC8FdSX6H0JcoWx SURlIhdncjkbFmBDBmc2HEPrRFbEhkeOFjldaZwDfipMiTNxxx/VK1yiS/0sjlpA KRE8N03fh19j5PvKBjGaENibPx1VJG8JBDYXJip41UZxbbMyeEF97i9Hl3y0s+w5 9oFhkXZVS+x0kLimSkJhsbtOmpL4/pO+XQ+vR9WLQwWJ7PO43swE7Y0S2H1J4fIB qL3jSjcklxOt7Dy3fXZz0Ws9HEUdnEyaus9RsDCMGVVwqexuA3kn6dvMNqD0IQj1 mOmEF5xvL6ukK76hJHgE4xIJMsOgB0s7psLpM4o6YYKpfeNcGvTissfZWw/T+58= =3kM2 -----END PGP SIGNATURE----- --Kj7319i9nmIyA2yE-- From owner-freebsd-virtualization@freebsd.org Sun Apr 21 16:13:41 2019 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 5B11B15909C2 for ; Sun, 21 Apr 2019 16:13:41 +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 EACAC76DF9 for ; Sun, 21 Apr 2019 16:13:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AE58A15909B5; Sun, 21 Apr 2019 16:13:40 +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 9C00A15909B3 for ; Sun, 21 Apr 2019 16:13:40 +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 3828076DF4 for ; Sun, 21 Apr 2019 16:13:40 +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 5EF9314403 for ; Sun, 21 Apr 2019 16:13:39 +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 x3LGDdcN052381 for ; Sun, 21 Apr 2019 16:13:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3LGDdiE052380 for virtualization@FreeBSD.org; Sun, 21 Apr 2019 16:13:39 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 215737] [bhyve] utilizing virtio-net truncates jumbo frames at 4084 bytes length Date: Sun, 21 Apr 2019 16:13:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: see_also 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: Sun, 21 Apr 2019 16:13:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215737 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 374 | |41 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sun Apr 21 17:02:03 2019 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 10F0F1591C9A for ; Sun, 21 Apr 2019 17:02:03 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CBCD6806CC for ; Sun, 21 Apr 2019 17:02:01 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id B6BB78D4A216 for ; Sun, 21 Apr 2019 17:01:58 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id E8984E70823 for ; Sun, 21 Apr 2019 17:01:57 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id QdDa3D235mO1 for ; Sun, 21 Apr 2019 17:01:56 +0000 (UTC) Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:2ef0:eeff:fe03:ee34]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 89E98E70822 for ; Sun, 21 Apr 2019 17:01:56 +0000 (UTC) From: "Bjoern A. Zeeb" To: "FreeBSD virtualization mailing list" Subject: bhyve, sparse disk image and trim support? Date: Sun, 21 Apr 2019 17:01:55 +0000 X-Mailer: MailMate (2.0BETAr6135) Message-ID: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: CBCD6806CC X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of bzeeb-lists@lists.zabbadoz.net designates 2a01:4f8:13b:39f::9f:25 as permitted sender) smtp.mailfrom=bzeeb-lists@lists.zabbadoz.net X-Spamd-Result: default: False [-4.97 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a01:4f8:13b:39f::9f:25]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cross.sbone.de]; NEURAL_HAM_SHORT(-0.99)[-0.992,0]; DMARC_NA(0.00)[zabbadoz.net]; IP_SCORE(-2.67)[ip: (-9.24), ipnet: 2a01:4f8::/29(-2.12), asn: 24940(-1.99), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[] 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: Sun, 21 Apr 2019 17:02:03 -0000 Hi, I have been wondering about this with other (commercial) virtualisation solutions in the past. If running on a “disk image” ideally I’d love that image to be a sparse file and ideally I’d love for bhyve/underlying virtualisation for the disk to understand TRIM so in case one deletes huge junks inside the VM the disk image can actually shrink again. Examples might be: you do a buildworld or an OS update in the guest and then want to delete the obj tree or temporary files after that. Now the disk image on the host has been bloated up, and could massively shrink again saving space on the host. Do we support this? Has anyone worked on this? How do people deal with these problems? /bz From owner-freebsd-virtualization@freebsd.org Sun Apr 21 17:08:17 2019 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 5B4061591F38 for ; Sun, 21 Apr 2019 17:08:17 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2D9480828 for ; Sun, 21 Apr 2019 17:08:16 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x3LH8Dbb028283; Sun, 21 Apr 2019 10:08:13 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x3LH8DiK028282; Sun, 21 Apr 2019 10:08:13 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904211708.x3LH8DiK028282@gndrsh.dnsmgr.net> Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop In-Reply-To: <20190421154616.GA59283@admin.sibptus.ru> To: Victor Sudakov Date: Sun, 21 Apr 2019 10:08:13 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: E2D9480828 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.988,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,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: Sun, 21 Apr 2019 17:08:17 -0000 -- Start of PGP signed section. > Rodney W. Grimes wrote: > > -- Start of PGP signed section. > > > Jason Tubnor wrote: > > > > On Sun., 21 Apr. 2019, 2:51 pm Victor Sudakov, wrote: > > > > > > > > > > > > > > > > > > > Does vm-bhyve provide a way to power them off ungracefully if they would > > > > > not stop within a predefined time? > > > > > > > > > > > > > You'd have to do your own checking but to force an instant power off of a > > > > guest simply execute: > > > > > > > > vm poweroff {guest} > > > > > > I don't need an *instant* poweroff, I need a poweroff only if a VM would > > > not stop gracefully within a predefined time. > > > > > > Of course this should not be done manually but from the rc.d/vm script > > > on shutdown. > > > > vm shutdown {guest} & > > (sleep N && vm poweroff {guest}) & > > > > A bit hackish, but that should work, if the guest has > > shutdown by the time you get to the poweroff an error > > might occur. This spawns a few processes, but is > > non blocking and highly parallel. > > Thank you, I might give it a try though it would involve hacking the > rc.d/vm script. > > > > > One thing I noted, you said rc.d/vm, so I am assuming your actually > > using the vm-bhyve port, > > Yes, I thought that was pretty obvious from the Subject line. Subject line disappears off the screen once a screen full of email gets displayed :-) > > in which case it has a sequential shutdown > > with time delays between each guest. vm_delay specifically, and it > > shuts vm's down in reverse order of the startup. > > > > That is more likely your problem in that your sending these acpi > > shutdown requests one at a time, and they should be broadcast in > > the "power going out" case. > > Whence is the idea that "vm stopall" does a sequential shutdown? What sense > would that make? Well I am not sure that vm-bhyve does this, but esxi certainly does, and it is a royal PITA to deal with sometimes. It does make sense in some aspects, do not want the database server going offline before all the clients go down do we? Kinda makes for a bunch of nonsense errors logged due to missing server. I kinda like my virtual routers and firewalls to keep going tell the end too. This is all YMMV situations though. > A sequential startup does make sense but a sequential shutdown? Useless > I think. The man page says that For you perhaps useless, but that rarely rules out that there may be a totally valid and usefull case. > stopall > Stop all running virtual machines. This sends a stop command to > all bhyve(8) instances, regardless of whether they were starting > using vm or not. And the implementation is pretty brutal: # 'vm stopall' # stop all bhyve instances # note this will also stop instances not started by vm-bhyve # core::stopall(){ local _pids=$(pgrep -f 'bhyve:') echo "Shutting down all bhyve virtual machines" killall bhyve sleep 1 killall bhyve wait_for_pids ${_pids} } I wonder what the effect of the second kill is, that seems odd. Almost like you might cause more issues than you solve as now you already have a vm in what should be ACPI shutdown process. Also this killall operation probably puts a high stress on disk i/o as you just woke up and made all the vm's get busy all at once and your going to basically thrash on every single resource they are using (yet another reason you may actually want to serialize these shutdown operations.) IIRC windows, especially newer ones, do a boat load of work on a shutdown unless they are told to shutdown quickly. Ie they even try to apply pending updates and such, that could be part of why you see windows vm's lagging around. You may also want to: Disable Clear page file on shutdown that is a windows thing, if you have a huge page file that can do a LOT of io, if you have a few windows vm's on the same spindle and try to stop them all at once your going to trash that disk for much longer than you need. > > > > It may be possile to adjust vm_delay to 0 and have that be better, > > though I have not locked at the code. You may also wish to discuss > > the issue with the vm-bhyve maintainer and maybe a "lights out" > > procedure needs to be added. > > Even if there is a single Windows 2012 or 2016 guest running, it takes > the vm several minutes to transition to the "stopped" state. You might nuke the wait_for_pids? > Victor Sudakov, VAS4-RIPE, VAS47-RIPN -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Sun Apr 21 19:13:13 2019 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 12A8C15822B5 for ; Sun, 21 Apr 2019 19:13:13 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F26678660D for ; Sun, 21 Apr 2019 19:13:11 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: by mail-oi1-x231.google.com with SMTP id w139so7140910oie.9 for ; Sun, 21 Apr 2019 12:13:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=H6i2GVSODaOl1JQ1LGHsrk0+DMZu8tZLsN9BdnBPpFk=; b=Qd6gfORawVMR5OUnRIqVwij7MxmTN3kie9tbZKxkeCsvm+ELzd9wVQeUiir4sSMen5 AfGQqMr/eHChmfu09APvGXIUgXEUnEBAzIfX7pYNiuDCWu6ua5kx/l7W+FQsPW9ikjy9 GNIJb2LdwEB6pkz8Ra5eJZObuIloM5GQeLtNzNrPmliDRGLF6uDaPqd/gz+mY6KfGVWC uQKexrr+qZissoBEcIjfLlgWXsxs9YXEMm/iI+3b28oOxWcWkAsTpV2YIIie/Nh/Me2J RW2kOqFZXPsN/QNzW3C5LSDbLAsQSjgUQctrG44tT92VjVs5loYNc3bGX1nvHBjJd8hN 6A7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=H6i2GVSODaOl1JQ1LGHsrk0+DMZu8tZLsN9BdnBPpFk=; b=oF8U9Z4N2ZyfJxCZD8H+AYV2W/Vl/6/LRmTuUfMaJL+PV59HMWIXvhZ+epQNQtNRwa AlhQo+/80hNckY0sYWF207k8cbioncALcmTP2zIFMk/mEISSM4no/shxrMcmDhZAlQKy fJWQRn+YUi7eYUWiJlQ+ZUAYfCW5SCA/eatchHDq/IqNI5kw9qVGdDCUfA1QkWnHX1jK OTO8KPAwFQpZ2t/Y6PqU5n1aHiSCPnUAGquvzkxav/zllgSuZWG+SItnJSYa0VhnfkWx 6WxwqtSGYI7bpO8RTlE2sC5c0vlx5VKEXhG/7WpPG+qLRUO406LG9xfBNsJqWt6Tf5i8 UIwA== X-Gm-Message-State: APjAAAWpcnfC6pywcPOUG3jI/BbhmshFTPnDkzwvDVpSiNiEFGn36fxL Zoy65mxkJ7WBE6Te8Qh6jFbOCBDj X-Google-Smtp-Source: APXvYqxcUjpSxTRVt6npPR/bE7gy//vO7gUi1RmTJ8vqQBh3ql69D/wwIjm8AsRy9x8q1N2Vw9NMTw== X-Received: by 2002:aca:4dd1:: with SMTP id a200mr8649136oib.142.1555873990553; Sun, 21 Apr 2019 12:13:10 -0700 (PDT) Received: from [2600:100c:b21f:6f83:98ea:cb79:100::] ([2600:100c:b21f:6f83:9c2a:a15d:d75:2ae]) by smtp.gmail.com with ESMTPSA id m21sm4781994otj.48.2019.04.21.12.13.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 Apr 2019 12:13:09 -0700 (PDT) Date: Sun, 21 Apr 2019 14:12:26 -0500 From: Dustin Marquess To: FreeBSD virtualization mailing list , "Bjoern A. Zeeb" Message-ID: <7adb331c-7563-4d8d-a6bc-e616c6ff4299@Spark> In-Reply-To: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> References: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> Subject: Re: bhyve, sparse disk image and trim support? X-Readdle-Message-ID: 7adb331c-7563-4d8d-a6bc-e616c6ff4299@Spark MIME-Version: 1.0 X-Rspamd-Queue-Id: F26678660D X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Qd6gfORa; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of dmarquess@gmail.com designates 2607:f8b0:4864:20::231 as permitted sender) smtp.mailfrom=dmarquess@gmail.com X-Spamd-Result: default: False [-4.44 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[1]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.96)[-0.961,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-virtualization@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[1.3.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_NOT_FQDN(0.50)[]; IP_SCORE(-2.96)[ip: (-9.37), ipnet: 2607:f8b0::/32(-3.13), asn: 15169(-2.26), country: US(-0.06)] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Sun, 21 Apr 2019 19:13:13 -0000 Using a sparse zvol and either the ahci-hd or nvme drivers should support= TRIM. -Dustin On Apr 21, 2019, 12:02 PM -0500, Bjoern A. Zeeb , wrote: > Hi, > > I have been wondering about this with other (commercial) virtualisation= > solutions in the past. If running on a =E2=80=9Cdisk image=E2=80=9D ide= ally I=E2=80=99d > love that image to be a sparse file and ideally I=E2=80=99d love for > bhyve/underlying virtualisation for the disk to understand TRIM so in > case one deletes huge junks inside the VM the disk image can actually > shrink again. > > Examples might be: you do a buildworld or an OS update in the guest and= > then want to delete the obj tree or temporary files after that. Now the= > disk image on the host has been bloated up, and could massively shrink > again saving space on the host. > > Do we support this=3F Has anyone worked on this=3F How do people deal w= ith > these problems=3F > > > /bz > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > freebsd-virtualization=40freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to =22freebsd-virtualization-unsubscribe=40= freebsd.org=22 From owner-freebsd-virtualization@freebsd.org Sun Apr 21 19:47:11 2019 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 17E1E1582E62 for ; Sun, 21 Apr 2019 19:47:11 +0000 (UTC) (envelope-from paul@redbarn.org) Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (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 8B1A38760D for ; Sun, 21 Apr 2019 19:47:10 +0000 (UTC) (envelope-from paul@redbarn.org) Received: from [192.168.44.232] (dslb-178-005-140-226.178.005.pools.vodafone-ip.de [178.5.140.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 3EF71892C6; Sun, 21 Apr 2019 19:47:07 +0000 (UTC) Subject: Re: bhyve, sparse disk image and trim support? To: Dustin Marquess Cc: FreeBSD virtualization mailing list , "Bjoern A. Zeeb" References: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> <7adb331c-7563-4d8d-a6bc-e616c6ff4299@Spark> From: Paul Vixie Message-ID: <630cf550-ab81-b44e-a145-0ffd11b13a43@redbarn.org> Date: Sun, 21 Apr 2019 12:47:04 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/6.1.14 MIME-Version: 1.0 In-Reply-To: <7adb331c-7563-4d8d-a6bc-e616c6ff4299@Spark> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Sun, 21 Apr 2019 19:47:11 -0000 Dustin Marquess wrote on 2019-04-21 12:12: > Using a sparse zvol and either the ahci-hd or nvme drivers should support TRIM. is someone working on virtio-blk support? -- P Vixie From owner-freebsd-virtualization@freebsd.org Sun Apr 21 22:51:06 2019 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 26EAC1587FBA for ; Sun, 21 Apr 2019 22:51:06 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com [IPv6:2607:f8b0:4864:20::236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE2C28DD59 for ; Sun, 21 Apr 2019 22:51:05 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: by mail-oi1-x236.google.com with SMTP id x188so7291878oia.13 for ; Sun, 21 Apr 2019 15:51:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=YOuCUDGdFcklfe8qABJMnRArUGB+ToU14FB/nO2OZAw=; b=dOhk3yx+j0yB9lphKW8yg5sOs70hsL7XGMe6+gd4qmdF1He0QuXXWACo6ywvlyPcGg Fc4JgvKODkkX8ULby8jvzoP0qx53aREwfvvbGYRpCl4ZeCZbfznxOeJILSLRx7/KLwoP QnZ6QO8/TVJm8sfzReCIKmMn/L6dqNG3xG6Qpl0vwGK5wmV5mYVwF4BtQ/Vc5VUeuJcU GDOot7JjlZYPTAy5YHa878ZN+4TTJI4DZozQdij5sc0EoGfYzSFB0eYGoKxqEwooEoAv +6j2G+24BwGJmCAzf16zony9p9VNbau/Y/LMIZDktPk5JkR4TqoQHf10+cc7sij4rSnQ GDvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=YOuCUDGdFcklfe8qABJMnRArUGB+ToU14FB/nO2OZAw=; b=g0wkjduOks7viey+yDqk+kVlsU0m6xu0wzpDAVSjK0Igvp0xR3HnxhEyOr8Qf2hv+g xHinuIc0pO5w3mF3GAEdsLUNV6cg0nhEe7gGkZlJS0xifiRlOz8wgtPZHwudVzYu6JzJ 26PRPMOIeYkobz+S55/shuMwcihVGq7luXxVxPxVdhIGIQvkfDX4Y+/XcyYnZocCuV1c B1TGsYgYV87Wtvl52GJ44k1zZSXn0tOTy3yrVkj7lpVBjxQ+ylwrQUR/wF7GpwvtXD4y 0bwBzRwNqL9uDLtaxSoWCC7zlOyovEmcfK3LNwft4zAcHulh7GlNMHHqbE6Kz3IsLlyn blcQ== X-Gm-Message-State: APjAAAWUAVM81bgN/Oi13H4No9k08u4ez1HzMpEbBE4GMGlYHOTYTNTS v7YrrXBKrz4/bTnJzyfvyvWsSgqn X-Google-Smtp-Source: APXvYqyEhhCxGtz1kgo3tv57mbShpbd3E/S/zjiCFc1sQbn5z6Hk8+YEzFriKYcv+B+gYT2cKrnkGw== X-Received: by 2002:aca:c647:: with SMTP id w68mr8951642oif.173.1555887064616; Sun, 21 Apr 2019 15:51:04 -0700 (PDT) Received: from [2600:100c:b21f:6f83:98ea:597d:100::] ([2600:100c:b21f:6f83:9c2a:a15d:d75:2ae]) by smtp.gmail.com with ESMTPSA id h24sm4448176otr.39.2019.04.21.15.51.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 21 Apr 2019 15:51:03 -0700 (PDT) Date: Sun, 21 Apr 2019 17:50:04 -0500 From: Dustin Marquess To: Paul Vixie Cc: FreeBSD virtualization mailing list , "Bjoern A. Zeeb" Message-ID: In-Reply-To: <630cf550-ab81-b44e-a145-0ffd11b13a43@redbarn.org> References: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> <7adb331c-7563-4d8d-a6bc-e616c6ff4299@Spark> <630cf550-ab81-b44e-a145-0ffd11b13a43@redbarn.org> Subject: Re: bhyve, sparse disk image and trim support? X-Readdle-Message-ID: b3de1f51-e69a-46c2-aa6d-e4d17e8f1b43@Spark MIME-Version: 1.0 X-Rspamd-Queue-Id: AE2C28DD59 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-7.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-1.00)[-0.996,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Sun, 21 Apr 2019 22:51:06 -0000 As far as I know, virtio-blk works, but doesn=E2=80=99t support TRIM. I b= elieve virtio-scsi does, but it seems to require more configuration on th= e host side from what I=E2=80=99ve seen. I never got it working with Wind= ows at least. -Dustin On Apr 21, 2019, 2:47 PM -0500, Paul Vixie , wrote: > > > Dustin Marquess wrote on 2019-04-21 12:12: > > Using a sparse zvol and either the ahci-hd or nvme drivers should sup= port TRIM. > > is someone working on virtio-blk support=3F > > -- > P Vixie > From owner-freebsd-virtualization@freebsd.org Mon Apr 22 02:13:01 2019 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 8674F158BA20 for ; Mon, 22 Apr 2019 02:13:01 +0000 (UTC) (envelope-from marcel@xcllnt.net) Received: from mail.xcllnt.net (mail.xcllnt.net [50.0.150.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 267C66C265 for ; Mon, 22 Apr 2019 02:12:59 +0000 (UTC) (envelope-from marcel@xcllnt.net) Received: from [192.168.2.23] (atc.xcllnt.net [50.0.150.213]) by mail.xcllnt.net (8.15.2/8.15.2) with ESMTP id x3M2Cp0j001366; Sun, 21 Apr 2019 19:12:52 -0700 (PDT) (envelope-from marcel@xcllnt.net) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: bhyve, sparse disk image and trim support? From: Marcel Moolenaar In-Reply-To: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> Date: Sun, 21 Apr 2019 19:12:58 -0700 Cc: Marcel Moolenaar , FreeBSD virtualization mailing list Content-Transfer-Encoding: quoted-printable Message-Id: References: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> To: "Bjoern A. Zeeb" X-Mailer: Apple Mail (2.3445.9.1) X-Greylist: Sender IP whitelisted, ACL 39 matched, not delayed by milter-greylist-4.6.2 (mail.xcllnt.net [50.0.150.214]); Sun, 21 Apr 2019 19:12:53 -0700 (PDT) X-Rspamd-Queue-Id: 267C66C265 X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.29 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MV_CASE(0.50)[]; IP_SCORE(-0.15)[asn: 46375(-0.71), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[xcllnt.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.59)[0.593,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[mail.xcllnt.net]; NEURAL_SPAM_LONG(0.95)[0.945,0]; NEURAL_SPAM_SHORT(0.52)[0.517,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:46375, ipnet:50.0.144.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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: Mon, 22 Apr 2019 02:13:01 -0000 > On Apr 21, 2019, at 10:01 AM, Bjoern A. Zeeb = wrote: >=20 > Hi, >=20 > I have been wondering about this with other (commercial) = virtualisation solutions in the past. If running on a =E2=80=9Cdisk = image=E2=80=9D ideally I=E2=80=99d love that image to be a sparse file = and ideally I=E2=80=99d love for bhyve/underlying virtualisation for the = disk to understand TRIM so in case one deletes huge junks inside the VM = the disk image can actually shrink again. >=20 > Examples might be: you do a buildworld or an OS update in the guest = and then want to delete the obj tree or temporary files after that. Now = the disk image on the host has been bloated up, and could massively = shrink again saving space on the host. >=20 > Do we support this? Has anyone worked on this? How do people deal = with these problems? I started libvdsk a (long) time back: see = https://svnweb.freebsd.org/base/user/marcel/libvdsk/ I moved it to github to make collaboration easier: see = https://github.com/xcllnt/libvdsk The latest code is in GitHub. I mostly didn't work on it, but recently spent a bit of time on it. With = raw disk support integrated into the bundled bhyve, the next obvious step is to add = support for qcow or vmdk or vhd. Someone has the beginnings of qcow support, so maybe that can be = integrated soonish Into libvdsk. I was thinking that a sparse file could be created for raw disk images = in the context of TRIM, but didn=E2=80=99t yet worry about it. It could be useful in general, = not just raw disk images so I wanted to get off the ground with something like vmdk first... JFYI, --=20 Marcel Moolenaar marcel@xcllnt.net From owner-freebsd-virtualization@freebsd.org Mon Apr 22 02:50:25 2019 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 74616158C3E3 for ; Mon, 22 Apr 2019 02:50:25 +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 0CAD56CEEA for ; Mon, 22 Apr 2019 02:50:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C27CB158C3E2; Mon, 22 Apr 2019 02:50:24 +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 AF205158C3E1 for ; Mon, 22 Apr 2019 02:50:24 +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 40EB06CEE7 for ; Mon, 22 Apr 2019 02:50:24 +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 8259D19ED6 for ; Mon, 22 Apr 2019 02:50:23 +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 x3M2oNr8094252 for ; Mon, 22 Apr 2019 02:50:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3M2oNZQ094251 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 02:50:23 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 237429] bhyve: Performance regression after 12 upgrade Date: Mon, 22 Apr 2019 02:50:23 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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: Mon, 22 Apr 2019 02:50:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #2 from doctor@doctor.nl2k.ab.ca --- Created attachment 203880 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D203880&action= =3Dedit dmesg.boot --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 02:52:41 2019 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 7D6AD158C5BA for ; Mon, 22 Apr 2019 02:52:41 +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 14A146D1EE for ; Mon, 22 Apr 2019 02:52:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id CCC62158C5B9; Mon, 22 Apr 2019 02:52:40 +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 BAAE5158C5B8 for ; Mon, 22 Apr 2019 02:52:40 +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 562B56D1EB for ; Mon, 22 Apr 2019 02:52:40 +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 9E5821A037 for ; Mon, 22 Apr 2019 02:52:39 +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 x3M2qd2Q005823 for ; Mon, 22 Apr 2019 02:52:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3M2qdSM005822 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 02:52:39 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 237429] bhyve: Performance regression after 12 upgrade Date: Mon, 22 Apr 2019 02:52:39 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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: Mon, 22 Apr 2019 02:52:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #3 from doctor@doctor.nl2k.ab.ca --- Created attachment 203881 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D203881&action= =3Dedit pciconf -lv --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 02:54:45 2019 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 09AEF158C7C1 for ; Mon, 22 Apr 2019 02:54:45 +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 934DB6D3F6 for ; Mon, 22 Apr 2019 02:54:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 571FB158C7BF; Mon, 22 Apr 2019 02:54:44 +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 45C17158C7BE for ; Mon, 22 Apr 2019 02:54:44 +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 D40ED6D3F3 for ; Mon, 22 Apr 2019 02:54:43 +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 0DE691A03D for ; Mon, 22 Apr 2019 02:54:43 +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 x3M2sgjf007839 for ; Mon, 22 Apr 2019 02:54:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3M2sgFm007836 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 02:54:42 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 237429] bhyve: Performance regression after 12 upgrade Date: Mon, 22 Apr 2019 02:54:43 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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: Mon, 22 Apr 2019 02:54:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #4 from doctor@doctor.nl2k.ab.ca --- Created attachment 203882 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D203882&action= =3Dedit /etc/rc.conf as requested --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 02:55:52 2019 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 9B3E9158C844 for ; Mon, 22 Apr 2019 02:55:52 +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 2D9746D49A for ; Mon, 22 Apr 2019 02:55:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E2A0C158C842; Mon, 22 Apr 2019 02:55:51 +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 D02DC158C841 for ; Mon, 22 Apr 2019 02:55:51 +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 55A6C6D490 for ; Mon, 22 Apr 2019 02:55:51 +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 967691A041 for ; Mon, 22 Apr 2019 02:55:50 +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 x3M2toHI009027 for ; Mon, 22 Apr 2019 02:55:50 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3M2toQm009026 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 02:55:50 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 237429] bhyve: Performance regression after 12 upgrade Date: Mon, 22 Apr 2019 02:55:50 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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: Mon, 22 Apr 2019 02:55:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #5 from doctor@doctor.nl2k.ab.ca --- Created attachment 203883 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D203883&action= =3Dedit bhyveguests 3 samples as ran from script --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 02:56:46 2019 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 E9370158C8AA for ; Mon, 22 Apr 2019 02:56:45 +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 803816D505 for ; Mon, 22 Apr 2019 02:56:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 413DA158C8A9; Mon, 22 Apr 2019 02:56:45 +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 2EFA7158C8A8 for ; Mon, 22 Apr 2019 02:56:45 +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 B51906D4FC for ; Mon, 22 Apr 2019 02:56:44 +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 08C921A043 for ; Mon, 22 Apr 2019 02:56:44 +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 x3M2uhtK009905 for ; Mon, 22 Apr 2019 02:56:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3M2uh7s009904 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 02:56:43 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 237429] bhyve: Performance regression after 12 upgrade Date: Mon, 22 Apr 2019 02:56:44 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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: Mon, 22 Apr 2019 02:56:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #6 from doctor@doctor.nl2k.ab.ca --- Created attachment 203884 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D203884&action= =3Dedit uanme -a as requested --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 02:59:49 2019 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 A21FE158C9FD for ; Mon, 22 Apr 2019 02:59:49 +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 3A00F6D623 for ; Mon, 22 Apr 2019 02:59:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EE839158C9FC; Mon, 22 Apr 2019 02:59:48 +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 DCD58158C9FB for ; Mon, 22 Apr 2019 02:59:48 +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 75ED76D621 for ; Mon, 22 Apr 2019 02:59:48 +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 C69C21A048 for ; Mon, 22 Apr 2019 02:59:47 +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 x3M2xlt8012939 for ; Mon, 22 Apr 2019 02:59:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3M2xlQb012938 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 02:59:47 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 237429] bhyve: Performance regression after 12 upgrade Date: Mon, 22 Apr 2019 02:59:47 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: Open 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: Mon, 22 Apr 2019 02:59:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #7 from doctor@doctor.nl2k.ab.ca --- I have=20 - complete host/guest bhyve vm configurations, including cpu/memory/disk confirations for the guests (as an attachment) But it is 2M of info --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 04:02:40 2019 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 60387158E03D for ; Mon, 22 Apr 2019 04:02:40 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 368306FD1C for ; Mon, 22 Apr 2019 04:02:38 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=lsQg7aJbQf+xF2uV6kTSmuf49A2xgOc9tYQ7NkHRkPs=; b=pha7LpEiGlr/cnGCZzYn+kXfU/ ThFlnFcp7/uCf4dbML4miBL3UYvUN7FJHOu+ZALP3vA765dIyxwbKTEdfKcbL+Za97LsRxIZpXcxp 7/YJMz/e9v80GyCMw/SLRWE7sx3SbaIPrx33MiA3b9aQHN+1mG6SC3dF5y+rXDey55Zo=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hIQA9-000JzU-P6 for freebsd-virtualization@freebsd.org; Mon, 22 Apr 2019 11:02:37 +0700 Date: Mon, 22 Apr 2019 11:02:37 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: running FreePBX SNG7 Official Distro Message-ID: <20190422040237.GA76690@admin.sibptus.ru> References: <20190407031237.GA7489@admin.sibptus.ru> <201904070426.x374Q641048406@gndrsh.dnsmgr.net> <20190407081445.GB40361@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Mon, 22 Apr 2019 04:02:40 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subbsd wrote: > On Sun, Apr 7, 2019 at 11:15 AM Victor Sudakov wrote: >=20 > > I'll look into the VirtualBox directory tomorrow and report here. I was > > under the impression that efivars are stored in a configuration file in > > the EFI partition but I was probably wrong, they are kept in NVRAM > > somewhere, like BIOS settings, and not on a disk. >=20 > I just wanted to confirm that this is indeed an EVIVARS problem, > because through CBSD (which uses Refind [1]) FreePBX 1805-2 > boots without any problems. Therefore, as Rodney said, you can try > using a third-party EFI boot manager. > And just wait until someone finds the time to add support for UEFI > VARS in bhyve. >=20 > [1] - http://www.rodsbooks.com/refind/ Kudos to the FreeBSD team! I've just discovered that when you install FreeBSD in UEFI mode, the installer creates a /efi/boot/startup.nsh on the efi partition. So FreeBSD would boot without any problems in VirtualBox with EFI, no need for persistent efi variables. --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --UugvWAfsgieZRqgk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcvTzdAAoJEA2k8lmbXsY0Qy0H/1eg68rj65+LwX27NLIF1O9U 31YEgzg7je52G8TP9zoOBc2th732K9ye4R1WjVRdraSoC8eY3PhtQiL5hGHZLZcT +qMKM8XbCrucSQ2h4MI/Riv+n+0ll8ZZS26EZPvAG806Lsqu9mF3P7EgUb4xNYda Hka2K7UJeamNt1O8aTDji2yVAWQZJtOODSHGkUIxtSCxGE+PUKOQpsj13cTCBRvJ k49QjTWJ3iLEBWj2jewh2Vg7s5Gj9vinbtEyTVeCoRCnkRiPC0vkw+3H8DdBYD2u 9xaP82KhuoTp+wUJn5lxf/d2m7z7jrLyNo/6v+BVIkx/e9bqqXSGO75+coQ/vY8= =H2XN -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From owner-freebsd-virtualization@freebsd.org Mon Apr 22 15:56:13 2019 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 0FAA2159DDC3 for ; Mon, 22 Apr 2019 15:56:13 +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 9A45B6AA09 for ; Mon, 22 Apr 2019 15:56:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 57475159DDC2; Mon, 22 Apr 2019 15:56:12 +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 44E64159DDC1 for ; Mon, 22 Apr 2019 15:56:12 +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 CD38A6AA06 for ; Mon, 22 Apr 2019 15:56:11 +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 1111D1113 for ; Mon, 22 Apr 2019 15:56:11 +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 x3MFuAZX022696 for ; Mon, 22 Apr 2019 15:56:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3MFuACp022693 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 15:56:10 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 237429] bhyve: Performance regression after 12 upgrade Date: Mon, 22 Apr 2019 15:56:10 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: Open 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: Mon, 22 Apr 2019 15:56:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #8 from Rodney W. Grimes --- Something that jumps out is: warning: total configured swap (58982400 pages) exceeds maximum recommended amount (16155552 pages). You have ~60G of swap space configured, the system only has 16G of memory, do you actually expect to over commit near 4x on memory? To go with this the 3 vm's you show are 4G in memory size, so they would need 12 of the 16G for guests, leaving your host running ZFS with only 4G of memory. Have you tuned the arc cache to be < than say about 2G as with just these 3 VM's your gong to start having memory pressure. I see 16 tap devices configured manually, this is normally handled by vm-bhyve, but leads me to the question how many VM's are you trying to run at once and what is the total memory footprint? --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 17:35:28 2019 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 42505159FFCF for ; Mon, 22 Apr 2019 17:35:28 +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 CF23D6E68F for ; Mon, 22 Apr 2019 17:35:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 925AC159FFCE; Mon, 22 Apr 2019 17:35:27 +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 7FF5A159FFCD for ; Mon, 22 Apr 2019 17:35:27 +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 142C36E68D for ; Mon, 22 Apr 2019 17:35:27 +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 545AA1FAA for ; Mon, 22 Apr 2019 17:35:26 +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 x3MHZQfZ022572 for ; Mon, 22 Apr 2019 17:35:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3MHZQRm022571 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 17:35:26 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 237429] bhyve: Performance regression after 12 upgrade Date: Mon, 22 Apr 2019 17:35:26 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: Open 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: Mon, 22 Apr 2019 17:35:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #9 from doctor@doctor.nl2k.ab.ca --- (In reply to Rodney W. Grimes from comment #8) 1) In case I wish to expand to say 64G RAM I can do so without trying to rebuild the server. 2)Running UFS not ZFS. Did I forget to mention this? 3) In 11.2 There were not problems. in 12.0 These problems suddenly manifested. 4) I was able to put up to 8 VM in 11.2 and below without issue. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 18:57:11 2019 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 A24A915A1ABD for ; Mon, 22 Apr 2019 18:57:11 +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 3AA187194F for ; Mon, 22 Apr 2019 18:57:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id F20E415A1ABA; Mon, 22 Apr 2019 18:57:10 +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 DFB6215A1AB9 for ; Mon, 22 Apr 2019 18:57:10 +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 796DA7194D for ; Mon, 22 Apr 2019 18:57:10 +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 BA5412B26 for ; Mon, 22 Apr 2019 18:57:09 +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 x3MIv9TP004234 for ; Mon, 22 Apr 2019 18:57:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3MIv9an004233 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 18:57:09 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 237429] bhyve: Performance regression after 12 upgrade Date: Mon, 22 Apr 2019 18:57:09 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: Open 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: Mon, 22 Apr 2019 18:57:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #10 from Rodney W. Grimes --- (In reply to doctor from comment #9) > 1) In case I wish to expand to say 64G RAM I can do so without trying to = rebuild the server. Ok, valid, thanks for clarifing. > 2)Running UFS not ZFS. Did I forget to mention this? Your system shows it has loaded ZFS: ZFS filesystem version: 5 ZFS storage pool version: features support (5000) you can say your not using it, but your dmesg says differently. > 3) In 11.2 There were not problems. in 12.0 These problems suddenly mani= fested. Are you certain that the only change is that of from 11.2 to 12.0, or did some other change, perhaps a change not considered is the cause of issues. I am simply trying to identify what performance would be low on 12.0 independent of any prior status. > 4) I was able to put up to 8 VM in 11.2 and below without issue. 8 VM's with 4G each on 11.2 with 16G of memory, I do not accept this as tru= e, that is 32G of memory commit + host memory needs. That should of been tras= hing itself unless those 8vm's are pretty well idle --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 21:29:57 2019 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 B49491583A2C for ; Mon, 22 Apr 2019 21:29:57 +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 4C32A80CB5 for ; Mon, 22 Apr 2019 21:29:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0C6211583A29; Mon, 22 Apr 2019 21:29:57 +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 EE29E1583A26 for ; Mon, 22 Apr 2019 21:29:56 +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 81F1580CAF for ; Mon, 22 Apr 2019 21:29:56 +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 BDFF9436A for ; Mon, 22 Apr 2019 21:29:55 +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 x3MLTto3028508 for ; Mon, 22 Apr 2019 21:29:55 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3MLTtOj028507 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 21:29:55 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 236989] AWS EC2 lockups "Missing interrupt" Date: Mon, 22 Apr 2019 21:29:56 +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: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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: Mon, 22 Apr 2019 21:29:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236989 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |virtualization@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 21:50:42 2019 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 08AD51584986 for ; Mon, 22 Apr 2019 21:50:42 +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 96039820FE for ; Mon, 22 Apr 2019 21:50:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 59D651584984; Mon, 22 Apr 2019 21:50:41 +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 476BA1584982 for ; Mon, 22 Apr 2019 21:50:41 +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 D39D6820F9 for ; Mon, 22 Apr 2019 21:50:40 +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 EF5AC4676 for ; Mon, 22 Apr 2019 21:50:39 +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 x3MLodxG069284 for ; Mon, 22 Apr 2019 21:50:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3MLodg4069283 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 21:50:39 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 236989] AWS EC2 lockups "Missing interrupt" Date: Mon, 22 Apr 2019 21:50:39 +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: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: Mon, 22 Apr 2019 21:50:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236989 Rodney W. Grimes changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chuck@FreeBSD.org, | |rgrimes@FreeBSD.org --- Comment #1 from Rodney W. Grimes --- Pulling in Chuck Tuffli as am NVMe expert --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Apr 22 22:02:10 2019 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 7FC3B1584F7A for ; Mon, 22 Apr 2019 22:02:10 +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 0506482958 for ; Mon, 22 Apr 2019 22:02:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B93A91584F77; Mon, 22 Apr 2019 22:02:09 +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 A6CB31584F74 for ; Mon, 22 Apr 2019 22:02:09 +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 42BBB82954 for ; Mon, 22 Apr 2019 22:02:09 +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 6F7664946 for ; Mon, 22 Apr 2019 22:02:08 +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 x3MM28SO098817 for ; Mon, 22 Apr 2019 22:02:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3MM28SB098795 for virtualization@FreeBSD.org; Mon, 22 Apr 2019 22:02:08 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 237429] bhyve: Performance regression after 12 upgrade Date: Mon, 22 Apr 2019 22:02:08 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: Open 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: Mon, 22 Apr 2019 22:02:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #11 from doctor@doctor.nl2k.ab.ca --- (In reply to Rodney W. Grimes from comment #10) (In reply to doctor from comment #9) > 1) In case I wish to expand to say 64G RAM I can do so without trying to = rebuild the server. Ok, valid, thanks for clarifying. Well small server. > 2)Running UFS not ZFS. Did I forget to mention this? Your system shows it has loaded ZFS: ZFS filesystem version: 5 ZFS storage pool version: features support (5000) you can say your not using it, but your dmesg says differently. I know I have it enable, would like to experiment with a hybrid UFS / ZFS system. > 3) In 11.2 There were not problems. in 12.0 These problems suddenly mani= fested. Are you certain that the only change is that of from 11.2 to 12.0, or did some other change, perhaps a change not considered is the cause of issues. I am simply trying to identify what performance would be low on 12.0 independent of any prior status. I do have a 2M ps axww | top -t file That needs to be added. > 4) I was able to put up to 8 VM in 11.2 and below without issue. 8 VM's with 4G each on 11.2 with 16G of memory, I do not accept this as tru= e, that is 32G of memory commit + host memory needs. That should of been tras= hing itself unless those 8vm's are pretty well idle They idle for the most part on 11.2 . --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Apr 23 00:52:08 2019 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 20B431587D95 for ; Tue, 23 Apr 2019 00:52:08 +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 AABFA86FC0 for ; Tue, 23 Apr 2019 00:52:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 687DD1587D93; Tue, 23 Apr 2019 00:52:07 +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 546291587D92 for ; Tue, 23 Apr 2019 00:52:07 +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 C2DBE86FB9 for ; Tue, 23 Apr 2019 00:52:06 +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 E81286148 for ; Tue, 23 Apr 2019 00:52:05 +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 x3N0q5dL059007 for ; Tue, 23 Apr 2019 00:52:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3N0q5C0059006 for virtualization@FreeBSD.org; Tue, 23 Apr 2019 00:52:05 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 237429] bhyve: Performance regression after 12 upgrade Date: Tue, 23 Apr 2019 00:52:05 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: amvandemore@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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: Tue, 23 Apr 2019 00:52:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 amvandemore@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amvandemore@gmail.com --- Comment #12 from amvandemore@gmail.com --- I don't think this is a reasonable bug report. Greatly overcommitted resou= rces and configuration like loading ZFS when the system is already memory starve= d.=20=20 I expect the output of something like 'top -aSwd 2' would provide much clar= ity missing from this report. If you do believe this be an actual bug in 12, can you provide the minimal = test case for reproduction. Also can you expand on the CPU errors you are seeing in guest VM's? I susp= ect these are spinlock errors which occur because you are overcommited, not bec= ause you are running 12-STABLE. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Apr 23 00:58:41 2019 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 98AC715881E5 for ; Tue, 23 Apr 2019 00:58:41 +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 1A9DD871F3 for ; Tue, 23 Apr 2019 00:58:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id CFB3B15881E4; Tue, 23 Apr 2019 00:58:40 +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 BE0F415881E3 for ; Tue, 23 Apr 2019 00:58:40 +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 5B5C3871EF for ; Tue, 23 Apr 2019 00:58:40 +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 A016F615C for ; Tue, 23 Apr 2019 00:58:39 +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 x3N0wd0v065328 for ; Tue, 23 Apr 2019 00:58:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3N0wdF3065327 for virtualization@FreeBSD.org; Tue, 23 Apr 2019 00:58:39 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 237429] bhyve: Performance regression after 12 upgrade Date: Tue, 23 Apr 2019 00:58:39 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: Open 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: Tue, 23 Apr 2019 00:58:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #13 from Rodney W. Grimes --- (In reply to doctor from comment #11) I am concerned that you have loaded zfs, you have no pool what so ever pres= ent on this machine? So my assumption is neither did 11.2, so please can you remove zfs, just so we know in no possible way is that having an effect. I= am pretty sure that zfs grabs a chunk of memory at boot time even if you just = load it and never do a zpool import, but it should not be a very big chunk. If in fact you do have a pool, even if your not using it, zfs is going to import it and suck up a bunch of your memory. I am not so interested in a large chunk of top data, however a single shot of "ps alwwx" would be of interest if you could get one during the slow down phase. At this stage I am pretty convinced this is additional memory pressure and = or system tuning changes that came with 12.0. It does have a slightly larger memory foot print, and there are a fairly extensive amount of vm system cha= nges between 11.2 and 12.0. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Apr 23 02:43:04 2019 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 E8DA4158AC34 for ; Tue, 23 Apr 2019 02:43:03 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 2F41D8A39A for ; Tue, 23 Apr 2019 02:43:03 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=p5wvmfJMs/WlJnYtlputeEvlTqKS/xGAa4HtgRdLTjg=; b=In/QdzruB8iD5ySrUVVsNTdWNi d86dt2iwyC/ZmRNSb0skD5KOHeYhB2xYwrCBK+1e4nLa/RMENEz+b6vhAJJAewsJMyGId9iR/YlIO wNlsnEUcD4TKNfcC3bYjzSa6FRClwO5iMvAA4e1fXxrCMAs5JBYIKTSM/Hq+4WjPSp6o=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hIlOf-0000RA-7n for freebsd-virtualization@freebsd.org; Tue, 23 Apr 2019 09:43:01 +0700 Date: Tue, 23 Apr 2019 09:43:01 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Message-ID: <20190423024301.GA940@admin.sibptus.ru> References: <20190421154616.GA59283@admin.sibptus.ru> <201904211708.x3LH8DiK028282@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline In-Reply-To: <201904211708.x3LH8DiK028282@gndrsh.dnsmgr.net> X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Tue, 23 Apr 2019 02:43:04 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Rodney W. Grimes wrote: [dd] > > > That is more likely your problem in that your sending these acpi > > > shutdown requests one at a time, and they should be broadcast in > > > the "power going out" case. > >=20 > > Whence is the idea that "vm stopall" does a sequential shutdown? What s= ense > > would that make?=20 >=20 > Well I am not sure that vm-bhyve does this, but esxi certainly does, > and it is a royal PITA to deal with sometimes. It does make sense > in some aspects, do not want the database server going offline before > all the clients go down do we? Kinda makes for a bunch of nonsense > errors logged due to missing server. I kinda like my virtual routers > and firewalls to keep going tell the end too. >=20 > This is all YMMV situations though. OK, you have convinced me, a predictable sequential shutdown may make sense sometimes. Anyway, it's not there im vm-bhyve so it's not the reason for the slow shutdown. >=20 > > A sequential startup does make sense but a sequential shutdown? Useless > > I think. The man page says that=20 >=20 > For you perhaps useless, but that rarely rules out that there may be > a totally valid and usefull case. >=20 > > stopall > > Stop all running virtual machines. This sends a stop comm= and to > > all bhyve(8) instances, regardless of whether they were st= arting > > using vm or not. >=20 > And the implementation is pretty brutal: > # 'vm stopall' > # stop all bhyve instances > # note this will also stop instances not started by vm-bhyve > #=20 > core::stopall(){ > local _pids=3D$(pgrep -f 'bhyve:') >=20 > echo "Shutting down all bhyve virtual machines" > killall bhyve > sleep 1 > killall bhyve > wait_for_pids ${_pids} > } >=20 > I wonder what the effect of the second kill is, > that seems odd. Indeed. > Almost like you might cause more > issues than you solve as now you already have a > vm in what should be ACPI shutdown process. >=20 > Also this killall operation probably puts a high stress > on disk i/o as you just woke up and made all the vm's > get busy all at once and your going to basically thrash > on every single resource they are using (yet another reason > you may actually want to serialize these shutdown operations.) You are right. >=20 > IIRC windows, especially newer ones, do a boat load of work > on a shutdown unless they are told to shutdown quickly. Ie > they even try to apply pending updates and such, that could > be part of why you see windows vm's lagging around. Do you know how to configure Windows for an unconditional ACPI shutdown? Last time I stopped my Windows guests, they stopped pretty quickly. But sometimes it just takes them forever to stop. Maybe it was giving a shutdown warning to the users or something. Or maybe it was this issue: https://serverfault.com/questions/871792/acpi-shutdown-does-not-always-work= -on-a-windows-server-virtual-machine > You may also want to: Disable Clear page file on shutdown > that is a windows thing, if you have a huge page file that > can do a LOT of io, if you have a few windows vm's on the > same spindle and try to stop them all at once your going to > trash that disk for much longer than you need. Last time I checked on the Windows 2012 and 2016 servers, the ClearPageFileAtShutdown setting was 0x0. I think it is the default. > > > It may be possile to adjust vm_delay to 0 and have that be better, > > > though I have not locked at the code. You may also wish to discuss > > > the issue with the vm-bhyve maintainer and maybe a "lights out" > > > procedure needs to be added. What is needed in vm-bhyve is the feature that if ACPI does not stop the guest for a predefined period of time, the guest is powered off. --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcvnu1AAoJEA2k8lmbXsY0FG4IALkbCgpJ6ugOiqLaf6RCda/O ja9YqiKfikCc4fGfa3YrxWSNoDzj/etoGOa/oagZ2xD3lcXBZSNYqm1xuxNWopgr fSILZCN8UsJdZthe4id1n8HSbyLdiimiXEV9XmA+pUjxgJBlFMZOpZYDMoUioucU AUSmX/4wG2jGjxzIvWTQPZy9YU/x/XxaRq89otsKKEFN2Cq+fH5itI0/40nTo79E SRqqVUKQHdKl9i4AVRdUKyM631qynwon1W2jyn+w/GW6yvD//B+T02X71ArSVYVV xKsiuhwUeca/pb1BH9lpVD+Auw712WaAta++dH5VqKGxHnRhmkR/bxS4PXzpWfU= =Kz92 -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF-- From owner-freebsd-virtualization@freebsd.org Tue Apr 23 02:55:06 2019 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 1061B158AFA6 for ; Tue, 23 Apr 2019 02:55:06 +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 95BFA8A8F7 for ; Tue, 23 Apr 2019 02:55:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 55C21158AFA5; Tue, 23 Apr 2019 02:55:05 +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 434FA158AFA4 for ; Tue, 23 Apr 2019 02:55:05 +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 D36998A8F5 for ; Tue, 23 Apr 2019 02:55:04 +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 16AD0725D for ; Tue, 23 Apr 2019 02:55:04 +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 x3N2t3k0002532 for ; Tue, 23 Apr 2019 02:55:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3N2t3pK002531 for virtualization@FreeBSD.org; Tue, 23 Apr 2019 02:55:03 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 237429] bhyve: Performance regression after 12 upgrade Date: Tue, 23 Apr 2019 02:55:04 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: Open 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: Tue, 23 Apr 2019 02:55:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #14 from doctor@doctor.nl2k.ab.ca --- (In reply to amvandemore from comment #12) You might have a point. Now trying to install every VM with 512MB and see= if that helps. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Apr 23 02:56:12 2019 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 B6210158B02B for ; Tue, 23 Apr 2019 02:56:12 +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 5063D8A9A0 for ; Tue, 23 Apr 2019 02:56:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 10DD4158B02A; Tue, 23 Apr 2019 02:56:12 +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 F2B97158B029 for ; Tue, 23 Apr 2019 02:56:11 +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 68C3C8A99B for ; Tue, 23 Apr 2019 02:56:11 +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 9CA6B7260 for ; Tue, 23 Apr 2019 02:56:10 +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 x3N2uAWn003656 for ; Tue, 23 Apr 2019 02:56:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3N2uAul003655 for virtualization@FreeBSD.org; Tue, 23 Apr 2019 02:56:10 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 237429] bhyve: Performance regression after 12 upgrade Date: Tue, 23 Apr 2019 02:56:10 +0000 X-Bugzilla-Reason: AssignedTo CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: needs-qa, performance X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: doctor@doctor.nl2k.ab.ca X-Bugzilla-Status: Open 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: Tue, 23 Apr 2019 02:56:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237429 --- Comment #15 from doctor@doctor.nl2k.ab.ca --- (In reply to Rodney W. Grimes from comment #13) Spinoff errors make sense. What I will do now is to build VMs basedon 512MB and the next machine I obatin will be SAS and ZFS friendly --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Apr 23 02:56:23 2019 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 576A5158B04A for ; Tue, 23 Apr 2019 02:56:23 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 C38408A9CA for ; Tue, 23 Apr 2019 02:56:22 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=8Oa1MiWkQJ3CNGb5i1eFE0MSZSvNFLT87rA3VXEa4AE=; b=DidUZa/q6mO3AOkuqwoA0hg58p 2xKBIHuFx93saG7J/evfLFfGE+Kaq/A9BQNMTl9JlYJflpF9FWDFEz/+8bh7kzkw5eglqd14FjiU7 eNCruxaYGYzM2BCTOLbESUMt2zGxhTxM4QoFnLJLTBZ834HgRspB9wHva+x9rFOB5gEY=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hIlbZ-0000VJ-Vw for freebsd-virtualization@freebsd.org; Tue, 23 Apr 2019 09:56:21 +0700 Date: Tue, 23 Apr 2019 09:56:21 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Message-ID: <20190423025621.GB940@admin.sibptus.ru> References: <20190421154616.GA59283@admin.sibptus.ru> <201904211708.x3LH8DiK028282@gndrsh.dnsmgr.net> <20190423024301.GA940@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="24zk1gE8NUlDmwG9" Content-Disposition: inline In-Reply-To: <20190423024301.GA940@admin.sibptus.ru> X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Tue, 23 Apr 2019 02:56:23 -0000 --24zk1gE8NUlDmwG9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Victor Sudakov wrote: [dd] > > > > It may be possile to adjust vm_delay to 0 and have that be better, > > > > though I have not locked at the code. You may also wish to discuss > > > > the issue with the vm-bhyve maintainer and maybe a "lights out" > > > > procedure needs to be added. >=20 > What is needed in vm-bhyve is the feature that if ACPI does not stop the > guest for a predefined period of time, the guest is powered off. I've created a feature request https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237479 please support me for adding yourself to the CC list, or commenting. --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --24zk1gE8NUlDmwG9 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcvn7VAAoJEA2k8lmbXsY0810H/1swJQSkR50U3QaQG1CGAeJz Gaspt3LeYmd05HTR+ZYWCiFWkVjMXmXa0cH6j31jFsCYWRIXQz/bErR/Kxb32B+/ mWNdVUPmE2UQF3zCRBfzMlgmnBR6OQx92KuJEivXCGSKbJt+x8vS7hI8EWHc38da nHYwQFwrPt04Y5jmo3FjrOB8V7s6gn2jE0UvBKe1l85hv9AR/zzt0dQ7mMSzu0Hi bxAnKvfiZ6Rx4dzRv4y/CUVduzl+a5gvG4xgJ6qbHZHMzWbOwgxOlaP15C+fJUjf MXpvZeIyTt/CZ1W1rkmW8cGcX+giafw4r0L68Fi4d4qlSMpaDsqXuu2y2F3lJHI= =66Fq -----END PGP SIGNATURE----- --24zk1gE8NUlDmwG9-- From owner-freebsd-virtualization@freebsd.org Tue Apr 23 03:07:00 2019 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 EB0D5158BD5C for ; Tue, 23 Apr 2019 03:06:59 +0000 (UTC) (envelope-from paul@redbarn.org) Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (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 F1A908BE0E for ; Tue, 23 Apr 2019 03:06:58 +0000 (UTC) (envelope-from paul@redbarn.org) Received: from [IPv6:2601:151:c302:493d:7455:4dfb:93b3:783b] (unknown [IPv6:2601:151:c302:493d:7455:4dfb:93b3:783b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 7197B892C6; Tue, 23 Apr 2019 03:06:56 +0000 (UTC) Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop To: Victor Sudakov Cc: freebsd-virtualization@freebsd.org References: <20190421154616.GA59283@admin.sibptus.ru> <201904211708.x3LH8DiK028282@gndrsh.dnsmgr.net> <20190423024301.GA940@admin.sibptus.ru> From: Paul Vixie Message-ID: Date: Mon, 22 Apr 2019 20:06:54 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/6.1.14 MIME-Version: 1.0 In-Reply-To: <20190423024301.GA940@admin.sibptus.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Tue, 23 Apr 2019 03:07:00 -0000 Victor Sudakov wrote on 2019-04-22 19:43: ... >> And the implementation is pretty brutal: >> # 'vm stopall' >> # stop all bhyve instances >> # note this will also stop instances not started by vm-bhyve >> # >> core::stopall(){ >> local _pids=$(pgrep -f 'bhyve:') >> >> echo "Shutting down all bhyve virtual machines" >> killall bhyve >> sleep 1 >> killall bhyve >> wait_for_pids ${_pids} >> } yow. >> >> I wonder what the effect of the second kill is, >> that seems odd. > > Indeed. the first killall will cause each client OS to see a soft shutdown signal. the sleep 1 gives them some time to flush their buffers. the second killall says, time's up, just stop. i think this is worse than brutal, it's wrong. consider freebsd's own work flow when trying to comply with the first soft shutdown it got: https://github.com/freebsd/freebsd/blob/master/sbin/reboot/reboot.c#L220 this has bitten me more than once, because using "pageins" as a proxy for "my server processes are busy trying to synchronize their user mode state" is inaccurate. i think _any_ continuing I/O should be reason to wait the full 60 seconds. and so i think the "sleep 1" above should be a "sleep 65". > What is needed in vm-bhyve is the feature that if ACPI does not stop the > guest for a predefined period of time, the guest is powered off. i agree with this. -- P Vixie From owner-freebsd-virtualization@freebsd.org Tue Apr 23 04:14:00 2019 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 55416158D891 for ; Tue, 23 Apr 2019 04:14:00 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 937368E097 for ; Tue, 23 Apr 2019 04:13:59 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=+yMfVAiTJC1x872xsS+TlH+MDIW3BU8nc4FZThfT5As=; b=aWxLma/yE2U1mh7cD3/kEpY7yk bi9fT9DsWGNDt3bkMrezkAmKxGEodKIytei3vO4EyzsjrXs2PTsLYa5Q+HV6+UwoNWdWxpOOphRRn xIab7wSAmGk9MDs9NLY8340z5o1Mz6+Bp8FuO36utQu7i8viQj+884K/DhW3qkVu2SPI=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hImog-0000tl-Av for freebsd-virtualization@freebsd.org; Tue, 23 Apr 2019 11:13:58 +0700 Date: Tue, 23 Apr 2019 11:13:58 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Message-ID: <20190423041358.GA2992@admin.sibptus.ru> References: <20190421154616.GA59283@admin.sibptus.ru> <201904211708.x3LH8DiK028282@gndrsh.dnsmgr.net> <20190423024301.GA940@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Tue, 23 Apr 2019 04:14:00 -0000 --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Paul Vixie wrote: >=20 > Victor Sudakov wrote on 2019-04-22 19:43: > ... > >> And the implementation is pretty brutal: > >> # 'vm stopall' > >> # stop all bhyve instances > >> # note this will also stop instances not started by vm-bhyve > >> # > >> core::stopall(){ > >> local _pids=3D$(pgrep -f 'bhyve:') > >> > >> echo "Shutting down all bhyve virtual machines" > >> killall bhyve > >> sleep 1 > >> killall bhyve > >> wait_for_pids ${_pids} > >> } >=20 > yow. To be sure, I was unable to find the above code (as is) in /usr/local/lib/vm-bhyve/vm-* (the vm-bhyve port 1.3.0). It may be that something more intelligent is happening in a more recent version, like a sequential shutdown. However, "kill $pid; sleep 1; kill $pid" seems to be still present. >=20 > >> > >> I wonder what the effect of the second kill is, > >> that seems odd. > >=20 > > Indeed. >=20 > the first killall will cause each client OS to see a soft shutdown=20 > signal. the sleep 1 gives them some time to flush their buffers. the=20 > second killall says, time's up, just stop. >=20 > i think this is worse than brutal, it's wrong. consider freebsd's own=20 > work flow when trying to comply with the first soft shutdown it got: >=20 > https://github.com/freebsd/freebsd/blob/master/sbin/reboot/reboot.c#L220 >=20 > this has bitten me more than once, because using "pageins" as a proxy=20 > for "my server processes are busy trying to synchronize their user mode= =20 > state" is inaccurate. i think _any_ continuing I/O should be reason to=20 > wait the full 60 seconds. Would it be beneficial to just hack /usr/local/lib/vm-bhyve/vm-* ? >=20 > and so i think the "sleep 1" above should be a "sleep 65". >=20 > > What is needed in vm-bhyve is the feature that if ACPI does not stop the > > guest for a predefined period of time, the guest is powered off. >=20 > i agree with this. Will you please support the bug report: https://bugs.freebsd.org/bugzilla/s= how_bug.cgi?id=3D237479 --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcvpEGAAoJEA2k8lmbXsY0rBIH/iHyk57c2eQNmoEsVYnPN6Mw afifUtGt0DVzLpp2G67gnES6+OhvQXNmVyUdOf+pJW8WlwMetSG8XCQImXoCN/Mk asQ+jJiNmu3QxdJAs7acAsf5epUE+5Qe5SsGV/MKwuVevbvfpn3TFzKQ2dJf8dAg xQv9O/UD2csr5tkNSaRlICP1Bv5CKycSW0p3Qs9m3gGzdCs/k7F5/F7KLkmWzYgI BHXJCrGdFEGx53fBCRsU/IGUug1EAcLrwALCglzf1PaqinLeicVXK0Lb3Fgvbbmp FiT5elQe1gKs/T8RmaPp7IZXy0hALx97RLOkNulxPApjAEtOQr+frErdwzlUMYw= =UG4B -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- From owner-freebsd-virtualization@freebsd.org Tue Apr 23 05:18:33 2019 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 D3FBB158E940 for ; Tue, 23 Apr 2019 05:18:32 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B5858F8A2 for ; Tue, 23 Apr 2019 05:18:31 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x3N5ITa3036034; Mon, 22 Apr 2019 22:18:29 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x3N5IS8J036033; Mon, 22 Apr 2019 22:18:28 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904230518.x3N5IS8J036033@gndrsh.dnsmgr.net> Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop In-Reply-To: To: Paul Vixie Date: Mon, 22 Apr 2019 22:18:28 -0700 (PDT) CC: Victor Sudakov , freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 3B5858F8A2 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.987,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,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: Tue, 23 Apr 2019 05:18:33 -0000 > Victor Sudakov wrote on 2019-04-22 19:43: > ... > >> And the implementation is pretty brutal: > >> # 'vm stopall' > >> # stop all bhyve instances > >> # note this will also stop instances not started by vm-bhyve > >> # > >> core::stopall(){ > >> local _pids=$(pgrep -f 'bhyve:') > >> > >> echo "Shutting down all bhyve virtual machines" > >> killall bhyve > >> sleep 1 > >> killall bhyve > >> wait_for_pids ${_pids} > >> } > > yow. > > >> > >> I wonder what the effect of the second kill is, > >> that seems odd. > > > > Indeed. > > the first killall will cause each client OS to see a soft shutdown > signal. the sleep 1 gives them some time to flush their buffers. the > second killall says, time's up, just stop. > > i think this is worse than brutal, it's wrong. consider freebsd's own > work flow when trying to comply with the first soft shutdown it got: > > https://github.com/freebsd/freebsd/blob/master/sbin/reboot/reboot.c#L220 Interesting, more interesting would be to dig out the path that the system takes when it gets teh ACPI shutdown event. That is not going to end up in sbin/reboot is it? Doesnt that run from within init itself? I find in the init man page this: The init utility will terminate all possible processes (again, it will not wait for deadlocked processes) and reboot the machine if sent the interrupt (INT) signal, i.e. ``kill -INT 1''. This is useful for shutting the machine down cleanly from inside the kernel or from X when the machine appears to be hung. So my guess is that sending an ACPI shutdown event to the VM ends up sending a -INT to init. Looking inside init, it seems to end up execing a shell runing /etc/rc.shutdown. I do not know if the ACPI event is then blocked in the kernel so the second one is pointless, but I believe once we enter into -INT processing that signal is ignored, so infact this second signal is actaully OK. But I am not 100% sure on this, yet. > this has bitten me more than once, because using "pageins" as a proxy > for "my server processes are busy trying to synchronize their user mode > state" is inaccurate. i think _any_ continuing I/O should be reason to > wait the full 60 seconds. > > and so i think the "sleep 1" above should be a "sleep 65". I think the sleep and the second signal are near pointless. If we have a race in ACPI processing we need to fix that. > > What is needed in vm-bhyve is the feature that if ACPI does not stop the > > guest for a predefined period of time, the guest is powered off. > > i agree with this. There is a PR up, https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237479 please add comments there if you feel so inclined. > -- > P Vixie -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Tue Apr 23 05:27:12 2019 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 85129158EDB1 for ; Tue, 23 Apr 2019 05:27:12 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E8F9F8FED8 for ; Tue, 23 Apr 2019 05:27:11 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x3N5R9ap036074; Mon, 22 Apr 2019 22:27:09 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x3N5R96x036073; Mon, 22 Apr 2019 22:27:09 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904230527.x3N5R96x036073@gndrsh.dnsmgr.net> Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop In-Reply-To: <20190423041358.GA2992@admin.sibptus.ru> To: Victor Sudakov Date: Mon, 22 Apr 2019 22:27:09 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: E8F9F8FED8 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.982,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,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: Tue, 23 Apr 2019 05:27:12 -0000 -- Start of PGP signed section. > Paul Vixie wrote: > > > > Victor Sudakov wrote on 2019-04-22 19:43: > > ... > > >> And the implementation is pretty brutal: > > >> # 'vm stopall' > > >> # stop all bhyve instances > > >> # note this will also stop instances not started by vm-bhyve > > >> # > > >> core::stopall(){ > > >> local _pids=$(pgrep -f 'bhyve:') > > >> > > >> echo "Shutting down all bhyve virtual machines" > > >> killall bhyve > > >> sleep 1 > > >> killall bhyve > > >> wait_for_pids ${_pids} > > >> } > > > > yow. > > To be sure, I was unable to find the above code (as is) in > /usr/local/lib/vm-bhyve/vm-* (the vm-bhyve port 1.3.0). It may be that > something more intelligent is happening in a more recent version, like a > sequential shutdown. However, "kill $pid; sleep 1; kill $pid" seems to > be still present. I probably pulled that from old code, pulled from: vm-bhyve-1.2.3 Management system for bhyve virtual machines > > > > > >> > > >> I wonder what the effect of the second kill is, > > >> that seems odd. > > > > > > Indeed. > > > > the first killall will cause each client OS to see a soft shutdown > > signal. the sleep 1 gives them some time to flush their buffers. the > > second killall says, time's up, just stop. > > > > i think this is worse than brutal, it's wrong. consider freebsd's own > > work flow when trying to comply with the first soft shutdown it got: > > > > https://github.com/freebsd/freebsd/blob/master/sbin/reboot/reboot.c#L220 > > > > this has bitten me more than once, because using "pageins" as a proxy > > for "my server processes are busy trying to synchronize their user mode > > state" is inaccurate. i think _any_ continuing I/O should be reason to > > wait the full 60 seconds. > > Would it be beneficial to just hack /usr/local/lib/vm-bhyve/vm-* ? One can always hack experiments, my vm-bhyve is fairly diverged from the release bits as I have done stuff to it so that it better meets my needs. Most of that is not submittable as upstream changes, some I should really sort out and try to push up. Some is due to local changes to bhyve that are not mainstream and thus are not (yet) applicable. > > and so i think the "sleep 1" above should be a "sleep 65". > > > > > What is needed in vm-bhyve is the feature that if ACPI does not stop the > > > guest for a predefined period of time, the guest is powered off. > > > > i agree with this. > > Will you please support the bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237479 More powerfull would be if we could come up with some patches against 1.3.0 that effected some of the changes we desire. And some more investigation as to just how the guests are handling this ACPI shutdown event. What might be wrong for FreeBSD might be right for windows? Does the ACPI spec saying anything about hitting the power down button twice within 1 second for example? > Victor Sudakov, VAS4-RIPE, VAS47-RIPN -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Tue Apr 23 07:14:28 2019 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 8CE4E15909CB for ; Tue, 23 Apr 2019 07:14:28 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) (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 BAC7192A09 for ; Tue, 23 Apr 2019 07:14:21 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [217.29.44.10]) by gate2.intern.punkt.de with ESMTP id x3N6uP5Q026198; Tue, 23 Apr 2019 08:56:25 +0200 (CEST) Received: from [217.29.44.36] ([217.29.44.36]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id x3N6uONk045379; Tue, 23 Apr 2019 08:56:24 +0200 (CEST) (envelope-from hausen@punkt.de) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\)) Subject: Re: bhyve, sparse disk image and trim support? From: "Patrick M. Hausen" In-Reply-To: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> Date: Tue, 23 Apr 2019 08:56:24 +0200 Cc: FreeBSD virtualization mailing list Content-Transfer-Encoding: quoted-printable Message-Id: <9E907736-8F90-4600-853C-7C2F7AF166BA@punkt.de> References: <21E25588-ADC0-4101-B122-5782D9A94AC4@lists.zabbadoz.net> To: "Bjoern A. Zeeb" X-Mailer: Apple Mail (2.3445.104.8) X-Rspamd-Queue-Id: BAC7192A09 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of hausen@punkt.de designates 217.29.33.131 as permitted sender) smtp.mailfrom=hausen@punkt.de X-Spamd-Result: default: False [-1.83 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.983,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:217.29.32.0/20]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[punkt.de]; NEURAL_HAM_LONG(-0.97)[-0.974,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[mailin.pluspunkthosting.de,mailin.pluspunkthosting.de]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[131.33.29.217.list.dnswl.org : 127.0.10.0]; NEURAL_HAM_SHORT(-0.81)[-0.814,0]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:16188, ipnet:217.29.32.0/20, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.25)[ipnet: 217.29.32.0/20(-0.68), asn: 16188(-0.54), country: DE(-0.01)] 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: Tue, 23 Apr 2019 07:14:28 -0000 Hi! > Am 21.04.2019 um 19:01 schrieb Bjoern A. Zeeb = : > Do we support this? Has anyone worked on this? How do people deal = with these problems? I=E2=80=99m actually surprised this is supported for some configurations = - thanks for starting the thread. As for how others deal with this - e.g. VMware = files never shrink, but there is a =E2=80=9Evacuuming=E2=80=9C function that = compresses the virtual disk while the VM is offline in the workstation products. For = ESXi I think the only way is to actually copy the image file to a new one = with vmkfstools. Used to use defrag and sdelete a lot in Windows VMs in the past, then ran the compaction =E2=80=A6 Kind regards Patrick --=20 punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe info@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling From owner-freebsd-virtualization@freebsd.org Tue Apr 23 08:18:44 2019 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 04F4915926CC for ; Tue, 23 Apr 2019 08:18:44 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 733109525D for ; Tue, 23 Apr 2019 08:18:43 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id F0FFF39C6; Tue, 23 Apr 2019 09:18:33 +0100 (BST) Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 23 Apr 2019 09:18:33 +0100 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Tue, 23 Apr 2019 09:18:33 +0100 From: Matt Churchyard To: Paul Vixie , Victor Sudakov CC: "freebsd-virtualization@freebsd.org" Subject: RE: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Thread-Topic: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Thread-Index: AQHU9/34wf9fOjj/bk24Jj1lbYU4w6ZGBuuAgAAc8oCAAHmAgIAAFJkAgAAW5YCAAjLugIAABqwAgABlfNA= Date: Tue, 23 Apr 2019 08:18:33 +0000 Message-ID: <4a660af455444ff48f38dc26852d999b@SERVER.ad.usd-group.com> References: <20190421154616.GA59283@admin.sibptus.ru> <201904211708.x3LH8DiK028282@gndrsh.dnsmgr.net> <20190423024301.GA940@admin.sibptus.ru> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Rspamd-Queue-Id: 733109525D X-Spamd-Bar: ------ X-Spamd-Result: default: False [-7.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.998,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: Tue, 23 Apr 2019 08:18:44 -0000 Victor Sudakov wrote on 2019-04-22 19:43: ... >> And the implementation is pretty brutal: >> # 'vm stopall' >> # stop all bhyve instances >> # note this will also stop instances not started by vm-bhyve #=20 >> core::stopall(){ >> local _pids=3D$(pgrep -f 'bhyve:') >> >> echo "Shutting down all bhyve virtual machines" >> killall bhyve >> sleep 1 >> killall bhyve >> wait_for_pids ${_pids} >> } > yow. >> >> I wonder what the effect of the second kill is, that seems odd. >=20 > Indeed. > the first killall will cause each client OS to see a soft shutdown signal= . the sleep 1 gives them some time to flush their buffers. the second killa= ll says, time's up, just stop. Both of these killall commands send a soft shutdown signal and I've never s= een an instance in my own testing where the second has caused an instant po= weroff. I've just double checked this, and a FreeBSD guest stopped with the existin= g code fully shuts itself down, ending with "acpi0: Powering system off" The main reason for having both is that in my initial testing, I could not = get Windows to respond to a single SIGINT. 100% of the time it would simply= act like nothing had happened. Sending two however triggered a shutdown. I= only have a single test machine though so maybe it's something strange abo= ut my particular system that no one else experiences... Matt > i think this is worse than brutal, it's wrong. consider freebsd's own wor= k flow when trying to comply with the first soft shutdown it got: > https://github.com/freebsd/freebsd/blob/master/sbin/reboot/reboot.c#L220 > this has bitten me more than once, because using "pageins" as a proxy for= "my server processes are busy trying to synchronize their user mode state"= is inaccurate. i think _any_ continuing I/O should > be reason to wait the= full 60 seconds. > and so i think the "sleep 1" above should be a "sleep 65". > What is needed in vm-bhyve is the feature that if ACPI does not stop=20 > the guest for a predefined period of time, the guest is powered off. > i agree with this. -- > P Vixie _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/m= ailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebs= d.org" From owner-freebsd-virtualization@freebsd.org Tue Apr 23 11:49:23 2019 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 159461597677 for ; Tue, 23 Apr 2019 11:49:23 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CE5916DC60 for ; Tue, 23 Apr 2019 11:49:21 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x3NBnHiM037664; Tue, 23 Apr 2019 04:49:17 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x3NBnGwn037663; Tue, 23 Apr 2019 04:49:16 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904231149.x3NBnGwn037663@gndrsh.dnsmgr.net> Subject: Re: bhyve, sparse disk image and trim support? In-Reply-To: <9E907736-8F90-4600-853C-7C2F7AF166BA@punkt.de> To: "Patrick M. Hausen" Date: Tue, 23 Apr 2019 04:49:16 -0700 (PDT) CC: "Bjoern A. Zeeb" , FreeBSD virtualization mailing list X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: CE5916DC60 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.00 / 15.00]; IP_SCORE(0.03)[ip: (0.11), ipnet: 69.59.192.0/19(0.06), asn: 13868(0.03), country: US(-0.06)]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; NEURAL_HAM_SHORT(-0.14)[-0.136,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.33)[0.329,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.89)[0.892,0]; R_SPF_NA(0.00)[]; RCVD_TLS_LAST(0.00)[] 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: Tue, 23 Apr 2019 11:49:23 -0000 [ Charset UTF-8 unsupported, converting... ] > Hi! > > > Am 21.04.2019 um 19:01 schrieb Bjoern A. Zeeb : > > Do we support this? Has anyone worked on this? How do people deal with these problems? > > I?m actually surprised this is supported for some configurations - thanks > for starting the thread. As for how others deal with this - e.g. VMware files > never shrink, but there is a ?vacuuming? function that compresses the > virtual disk while the VM is offline in the workstation products. For ESXi > I think the only way is to actually copy the image file to a new one with > vmkfstools. The current state of affairs with respect to ESXi is expressed here: https://www.codyhosterman.com/2016/11/whats-new-in-esxi-6-5-storage-part-i-unmap/ There was some experimental stuff back in 5.0 that was mostly broken. And there is much more information out there to be read.... > Used to use defrag and sdelete a lot in Windows VMs in the past, then > ran the compaction ? I am not sure, but at one time I thought ESXi would detect writes of null blocks to thin provisioned disks and unmap those blocks on its own, and that was basically how the guest tools cleanup disk space thing worked, but I can not find that information on this today. I do know that dd conv=sparse is one way to relaim such null blocks from a FreeBSD host if you do dd if=/dev/zero of=somejunkplace bs=1m rm somejunkplace inside your guest first, shut it down, then run a conv=sparse you can get back host file system space. Though the dd inside the guest well usually fully inflate the disk image so be careful! You may need up to 2 times the volume size to do these operations. > Kind regards > Patrick -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Tue Apr 23 12:10:01 2019 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 0E6D01598A0F for ; Tue, 23 Apr 2019 12:10:01 +0000 (UTC) (envelope-from paul@redbarn.org) Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (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 603186EF03 for ; Tue, 23 Apr 2019 12:10:00 +0000 (UTC) (envelope-from paul@redbarn.org) Received: from [172.16.74.22] (unknown [50.235.236.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 98A17892C6 for ; Tue, 23 Apr 2019 12:09:57 +0000 (UTC) Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop To: freebsd-virtualization@freebsd.org References: <20190421154616.GA59283@admin.sibptus.ru> <201904211708.x3LH8DiK028282@gndrsh.dnsmgr.net> <20190423024301.GA940@admin.sibptus.ru> <20190423041358.GA2992@admin.sibptus.ru> From: Paul Vixie Message-ID: <212b6254-1e27-8311-885b-601f8b1d710c@redbarn.org> Date: Tue, 23 Apr 2019 05:09:56 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/6.1.14 MIME-Version: 1.0 In-Reply-To: <20190423041358.GA2992@admin.sibptus.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Tue, 23 Apr 2019 12:10:01 -0000 Victor Sudakov wrote on 2019-04-22 21:13: ... >>>> sleep 1 ... >> i think this is worse than brutal, it's wrong. consider freebsd's own >> work flow when trying to comply with the first soft shutdown it got: >> >> https://github.com/freebsd/freebsd/blob/master/sbin/reboot/reboot.c#L220 >> >> this has bitten me more than once, because using "pageins" as a proxy >> for "my server processes are busy trying to synchronize their user mode >> state" is inaccurate. i think _any_ continuing I/O should be reason to >> wait the full 60 seconds. > > Would it be beneficial to just hack /usr/local/lib/vm-bhyve/vm-* ? no, i really think the hypervisor should add i/o monitoring, so that if the soft shutdown signal is sent, the client kernel is allowed to keep running until either a really long timeout (60 seconds or more), but if it becomes quiet, then the hypervisor can exit sooner. >> i agree with this. > > Will you please support the bug report: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237479 done. -- P Vixie From owner-freebsd-virtualization@freebsd.org Tue Apr 23 13:57:38 2019 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 E6153159B4B7 for ; Tue, 23 Apr 2019 13:57:37 +0000 (UTC) (envelope-from kusuriya@serversave.us) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 8D1C472F94 for ; Tue, 23 Apr 2019 13:57:37 +0000 (UTC) (envelope-from kusuriya@serversave.us) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 75F4927C11; Tue, 23 Apr 2019 09:57:36 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 23 Apr 2019 09:57:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=serversave.us; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=mesmtp; bh=YuEb0jzExM501ii1BzdrvcPk1EbQk8GFZmhnSj2wvCI=; b=bK0aqgjulbot lMtUq+zYUTp01SyPGo4IIZPuDE49+aVPuAj9Wp0/6XsE9GgLdmEoljCPtalRC4S+ 0Td8qNtDF+huJkvUsbruE0hMfELqCU7iEh/Nl/6e3Fm3FMwOp7LnmBJxahysWbo1 D6JCpHFUhZQ4yu8drmrXa2iIrEC3fbQ= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=YuEb0jzExM501ii1BzdrvcPk1EbQk8GFZmhnSj2wv CI=; b=cr8zltyRk6KZzjf8S2fUTwRB0VkFouIfTXwmREIlMGvZcT3uNTh2Q46Aq Fb8qOU8kNVRdDlggY3umg6p9FRvYqHvejE0CFt8Y5bR8uxofRWhhQaG1YhnuPhqX ymO0zAYiJDch5ekxrVuim4agzlVO1WCCQkX8Bf8lV1WKea9asnpT8GSbh9FBTDWN ykKwi/hudHJu8NLZeq79XyTl1HEi+/xIM68rb7pZXweluyaEZwzf/12x5hZNdC8z vttYakPauy1ICtjzyGVrJO4B76rX+dhHugb0xYLRC8zsazEdPpvfbvNNTSHf/Mju I16JH3onuVbzREaWz029O8D011yVg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrgeekgdehlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdeimdenucfjughrpegtggfuhf fojgffgffkfhfvsehtqhhmtdhhtddvnecuhfhrohhmpeflrghsohhnuceurghrsghivghr uceokhhushhurhhihigrsehsvghrvhgvrhhsrghvvgdruhhsqeenucffohhmrghinhepgh hithhhuhgsrdgtohhmnecukfhppedujedvrdehkedrfeehrddunecurfgrrhgrmhepmhgr ihhlfhhrohhmpehkuhhsuhhrihihrgesshgvrhhvvghrshgrvhgvrdhushenucevlhhush htvghrufhiiigvpedt X-ME-Proxy: Received: from [IPv6:2607:fb90:a682:fde8:14ca:690c:b168:526] (unknown [172.58.35.1]) by mail.messagingengine.com (Postfix) with ESMTPA id 33295E424F; Tue, 23 Apr 2019 09:57:35 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop From: Jason Barbier X-Mailer: iPhone Mail (16E227) In-Reply-To: <20190423041358.GA2992@admin.sibptus.ru> Date: Tue, 23 Apr 2019 06:57:30 -0700 Cc: freebsd-virtualization@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3E2402FD-CA3E-4471-B7A9-6D6B0CB1B900@serversave.us> References: <20190421154616.GA59283@admin.sibptus.ru> <201904211708.x3LH8DiK028282@gndrsh.dnsmgr.net> <20190423024301.GA940@admin.sibptus.ru> <20190423041358.GA2992@admin.sibptus.ru> To: Victor Sudakov X-Rspamd-Queue-Id: 8D1C472F94 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-7.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-1.00)[-0.998,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,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: Tue, 23 Apr 2019 13:57:38 -0000 > On Apr 22, 2019, at 21:13, Victor Sudakov wrote: >=20 > Paul Vixie wrote: >>=20 >> Victor Sudakov wrote on 2019-04-22 19:43: >> ... >>>> And the implementation is pretty brutal: >>>> # 'vm stopall' >>>> # stop all bhyve instances >>>> # note this will also stop instances not started by vm-bhyve >>>> # >>>> core::stopall(){ >>>> local _pids=3D$(pgrep -f 'bhyve:') >>>>=20 >>>> echo "Shutting down all bhyve virtual machines" >>>> killall bhyve >>>> sleep 1 >>>> killall bhyve >>>> wait_for_pids ${_pids} >>>> } >>=20 >> yow. Eew no that is painful to read! >=20 > To be sure, I was unable to find the above code (as is) in > /usr/local/lib/vm-bhyve/vm-* (the vm-bhyve port 1.3.0). It may be that > something more intelligent is happening in a more recent version, like a > sequential shutdown. However, "kill $pid; sleep 1; kill $pid" seems to > be still present. >=20 >>=20 >>>>=20 >>>> I wonder what the effect of the second kill is, >>>> that seems odd. >>>=20 >>> Indeed. >>=20 >> the first killall will cause each client OS to see a soft shutdown=20 >> signal. the sleep 1 gives them some time to flush their buffers. the=20 >> second killall says, time's up, just stop. >>=20 >> i think this is worse than brutal, it's wrong. consider freebsd's own=20 >> work flow when trying to comply with the first soft shutdown it got: >>=20 >> https://github.com/freebsd/freebsd/blob/master/sbin/reboot/reboot.c#L220 >>=20 >> this has bitten me more than once, because using "pageins" as a proxy=20 >> for "my server processes are busy trying to synchronize their user mode=20= >> state" is inaccurate. i think _any_ continuing I/O should be reason to=20= >> wait the full 60 seconds. >=20 > Would it be beneficial to just hack /usr/local/lib/vm-bhyve/vm-* ? >>=20 >> and so i think the "sleep 1" above should be a "sleep 65". I would echo this and say it should probably be done in a way that you can h= ave a sliding window, some servers and services are not very fault tolerant o= n their own. The example that springs to mind for me is the busy AD domain c= ontroller I manage. It takes 15 mins to flush the disk buffer, if I kill it b= efore the buffer flushes I will have a bad day as my domain at best loses a f= ew transactions at worst is corrupted. From owner-freebsd-virtualization@freebsd.org Wed Apr 24 04:36:59 2019 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 48B09158BC04 for ; Wed, 24 Apr 2019 04:36:59 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 5814A71EF7 for ; Wed, 24 Apr 2019 04:36:57 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=Q5vdhMaeS+vZQ5MlJ+67WeS22l3U27f/PFQyer8mJeQ=; b=nPnDM63HADi9dFjgYewqmt1O0W TXOLUvjbBkRJc+vkj92tubjnt0yMN0Kr/PfR7LCauLE6F3VfswOCyjcfu6NQdVxc5TOucyTkzN/SF QZIovnaW0YSnKKJd2j34Noul2XAFyKLHI99AH6sAMx7JPRy4D8NnTqd5vnIWms+XVkoI=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hJ9eS-0006pp-Fj for freebsd-virtualization@freebsd.org; Wed, 24 Apr 2019 11:36:56 +0700 Date: Wed, 24 Apr 2019 11:36:56 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Message-ID: <20190424043656.GA25754@admin.sibptus.ru> References: <20190421045143.GA49101@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: <20190421045143.GA49101@admin.sibptus.ru> X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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, 24 Apr 2019 04:36:59 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Victor Sudakov wrote: >=20 > I've noticed that it takes too long for Windows 2012 and 2016 servers > guests to shutdown when I issue "vm stopall," several minutes even. >=20 > Does vm-bhyve provide a way to power them off ungracefully if they would > not stop within a predefined time? >=20 > Or is there perhaps a way to tune the guest OSes to react more promptly > to an ACPI shutdown? >=20 > My primary concern is that my UPS and "apcupsd --kill-on-powerfail" give > me about 30 seconds of grace time before the power supply is cut out. It > is not sufficient for the bhyve box to shutdown shutdown properly > because it waits for the guests to shutdown. For the present I think I've found a workaround not directly related to vm-bhyve. I'm going to insert "service vm stop" into the doshutdown() procedure in /usr/local/etc/apcupsd/apccontrol before the actual ${SHUTDOWN}. It should give the VMs sufficient time to shutdown before the actual /sbin/shutdown is executed. >=20 > If you know of a better way to configure apcupsd so that it powers down > the UPS only after all the guest OSes and other daemons are safely down, > I'd appreciate that too. Do you think the above hack would have any negative effects? --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --UugvWAfsgieZRqgk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcv+foAAoJEA2k8lmbXsY05hEH/jalvFUZkpzL1+U7HnRhdRXs OzyPx/828Jl5Hijk2fD3ton9rTw7VXfHZH6ZVDA6caWfWOD+i6R70XE05cUXBscX tbCEncOA5I1cS8358Bw3CbrzNif3E3imIj67Z9YewV597ulOf77Njo4NJeJH42Jo 5Qsge/i0S6f2FubCOrYXT8PJ42jurD3i8kPRZltCPAMWc093aDP7UeyzoETAO9jI T8QpHcV4pr42EiR6OgWrDyZAfQr9Rdl7Wu+SbC5iuiRqRmiUA99HBJtLg/27534/ Wm1YozFOnohky/WQosa+37sv+g2RFSt9gndJu7M1BX2lVQbuvQTir5AMas3S9Ns= =c5eQ -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From owner-freebsd-virtualization@freebsd.org Wed Apr 24 05:57:10 2019 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 C5C74158D723 for ; Wed, 24 Apr 2019 05:57:10 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3528074CDA for ; Wed, 24 Apr 2019 05:57:09 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x3O5v6Df041738; Tue, 23 Apr 2019 22:57:06 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x3O5v6AK041737; Tue, 23 Apr 2019 22:57:06 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904240557.x3O5v6AK041737@gndrsh.dnsmgr.net> Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop In-Reply-To: <20190424043656.GA25754@admin.sibptus.ru> To: Victor Sudakov Date: Tue, 23 Apr 2019 22:57:06 -0700 (PDT) CC: freebsd-virtualization@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 3528074CDA X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.988,0]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,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, 24 Apr 2019 05:57:10 -0000 > Victor Sudakov wrote: > > > > I've noticed that it takes too long for Windows 2012 and 2016 servers > > guests to shutdown when I issue "vm stopall," several minutes even. > > > > Does vm-bhyve provide a way to power them off ungracefully if they would > > not stop within a predefined time? > > > > Or is there perhaps a way to tune the guest OSes to react more promptly > > to an ACPI shutdown? > > > > My primary concern is that my UPS and "apcupsd --kill-on-powerfail" give > > me about 30 seconds of grace time before the power supply is cut out. It > > is not sufficient for the bhyve box to shutdown shutdown properly > > because it waits for the guests to shutdown. > > For the present I think I've found a workaround not directly related to > vm-bhyve. I'm going to insert "service vm stop" into the doshutdown() > procedure in /usr/local/etc/apcupsd/apccontrol before the actual > ${SHUTDOWN}. It should give the VMs sufficient time to shutdown before > the actual /sbin/shutdown is executed. Make sure it does not do the waitall for pids or your going to sit here waiting for that to complete for a long time, ie until all vm's go to power off. > > > > If you know of a better way to configure apcupsd so that it powers down > > the UPS only after all the guest OSes and other daemons are safely down, > > I'd appreciate that too. > > Do you think the above hack would have any negative effects? I think this is a reasonable approach given the current situation. > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Wed Apr 24 06:52:26 2019 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 5E07C158EDA4 for ; Wed, 24 Apr 2019 06:52:26 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 CA20C76FC8 for ; Wed, 24 Apr 2019 06:52:25 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=SrLHSogtPIZxRIjDG5BMaSIUNQ2szVAuXNyyNLEMFTE=; b=llNDoUR8xkevcy++ib+BwCxCez ysKQn/7kTJJqud4F5amYTYaUceXSJzytaH4RcMuN+SOzAms7GTCzTs2vmpQ2i15Qi1GzBMsTlI4FZ HXXnAp2Ja4pF+HMuJsCWV9k4w1N1bQDGHTNiL1ALDZWuOlP1TQV0sYAc/ddAwV8eLpMM=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hJBlX-0007LG-MT for freebsd-virtualization@freebsd.org; Wed, 24 Apr 2019 13:52:23 +0700 Date: Wed, 24 Apr 2019 13:52:23 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Message-ID: <20190424065223.GA28138@admin.sibptus.ru> References: <20190424043656.GA25754@admin.sibptus.ru> <201904240557.x3O5v6AK041737@gndrsh.dnsmgr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <201904240557.x3O5v6AK041737@gndrsh.dnsmgr.net> X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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, 24 Apr 2019 06:52:26 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Rodney W. Grimes wrote: > > >=20 > > > I've noticed that it takes too long for Windows 2012 and 2016 servers > > > guests to shutdown when I issue "vm stopall," several minutes even. > > >=20 > > > Does vm-bhyve provide a way to power them off ungracefully if they wo= uld > > > not stop within a predefined time? > > >=20 > > > Or is there perhaps a way to tune the guest OSes to react more prompt= ly > > > to an ACPI shutdown? > > >=20 > > > My primary concern is that my UPS and "apcupsd --kill-on-powerfail" g= ive > > > me about 30 seconds of grace time before the power supply is cut out.= It > > > is not sufficient for the bhyve box to shutdown shutdown properly > > > because it waits for the guests to shutdown. > >=20 > > For the present I think I've found a workaround not directly related to > > vm-bhyve. I'm going to insert "service vm stop" into the doshutdown() > > procedure in /usr/local/etc/apcupsd/apccontrol before the actual > > ${SHUTDOWN}. It should give the VMs sufficient time to shutdown before > > the actual /sbin/shutdown is executed. >=20 > Make sure it does not do the waitall for pids or your going to > sit here waiting for that to complete for a long time, ie until > all vm's go to power off. In fact, this is my intention to sit here waiting for all VM's to go power = off. I can configure apcupsd to start the doshutdown() routine when there is enough power in the UPS, like maybe for 20-30 minutes. > > > If you know of a better way to configure apcupsd so that it powers do= wn > > > the UPS only after all the guest OSes and other daemons are safely do= wn, > > > I'd appreciate that too. > >=20 > > Do you think the above hack would have any negative effects? >=20 > I think this is a reasonable approach given the current situation. >=20 --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcwAenAAoJEA2k8lmbXsY0K2AH/iGON5bDFbmyWGKoDhf3Y0pG 591ZxJl1/+0XMFbhX9VZ6ZdIwL5LwNtHLo7xvNJMzrvQoG4M8BRAxDDH3I7wGINn g1NVkgpv/crq/vqy3dHjOJq3uiIkySN9HRA9sVg+Wuqbmo3Tx3ZADrq69vUvqYCc GLHmXv/tw06t76q8XkANvKeBizeOkkG8gd3Wr/3wDSG3Jd2vKVa28JpTbFUfj2DS Ybzu6JxKzKrdzjpkLhzNP12H0d7pHLrSKNFfSHdZ1WeBxPUNd0LjKnoUfVn2UIjh UdbRu3PU7cRYoNy/Fa4FFWOJ0cfn8MzG7It88XpkXiQAlu0juwluCU8VwuPOLnI= =ZnO1 -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- From owner-freebsd-virtualization@freebsd.org Wed Apr 24 14:45:27 2019 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 ACCF4159AA1D for ; Wed, 24 Apr 2019 14:45:27 +0000 (UTC) (envelope-from stephen.stuart@gmail.com) Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2EC578FC7C for ; Wed, 24 Apr 2019 14:45:27 +0000 (UTC) (envelope-from stephen.stuart@gmail.com) Received: by mail-wr1-x429.google.com with SMTP id s18so722623wrp.0 for ; Wed, 24 Apr 2019 07:45:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2NPc3vaNMb3DxxrPKjZH3PWvL3MT0DbPIA3/0q+JmhQ=; b=PFBEKMzHysS2BzC2qVvz3txlpZqJyxSFSvzjSYVffMImt+rh02O6dgoGHsUAOQqovX oGoSvn0v/oVsg4aqBCHXpV73Za2A1tK8DWmQeko0an+FCWZ78ptjzeDZG7TWjveoeJpN F5Q/MYicvYno/3WNoSiC4QRI0kmLkkhA5BIm5c6bowEHANHGzpdHLpykVrN5x09ji9/z HnZZIOgtqhusHQY6aamnSMkK2CpCHDdWTuq6uDQwg+lAwDEOOgh9rqEjy3V0IgM9V4nF NcIG8oHzpUTMQFAK4SF/D2YOkxxNO9Sy1MzHdjCuhh21ZtNR4SYtbmMlPwrKLO4s8z2H H12w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2NPc3vaNMb3DxxrPKjZH3PWvL3MT0DbPIA3/0q+JmhQ=; b=FeIjFzcTO2eY3WELu3xt2tx36sTUYbHRU2q85nzxKliuuXqMo01z1Hrw55S8Q0B2GV 1LLvEJ4Ny7SZ6WSCn8+DogGG8HAF7lWI/RwPTwW8NUhQUL9+fZD8c0Y202IQQiqVHCyE azYJsEgiajC1CIba5QAHc7OGXFSeOD19fvqYJ36rd7uW+yqm3p90SmQUYLVtJcV4r2vr 8bRBdrCbsU287IDfZAvwO4mTCHm7aBZl3Uxjlllo5wlJ8jFQ8Dd/9ne/C2NdIUecZqJ4 UCePhdIIaZCmRvmsOy0AgbMVMo+/aj+CYiDbfLcJIfeOpLvp6IiQqYYy5u2i1POpTkHM ttCw== X-Gm-Message-State: APjAAAVaiJ4qrJ9eO+VIJu8M7QoSG6qA6wSj3PfoowJpdLGM/r1qJNbk v8zIIhI98us9VziiC0vGoowtevUO8RZUaUJy8RWU6SiJ X-Google-Smtp-Source: APXvYqxOoySDnqihP+blay3tIl37XSUo0JqN3FSDXRaZdSMFpzjwPWw4poHlp15Kzlujgf3VvTYzVhhXeFSyAQ8H8LQ= X-Received: by 2002:a5d:68c4:: with SMTP id p4mr13116043wrw.37.1556117125213; Wed, 24 Apr 2019 07:45:25 -0700 (PDT) MIME-Version: 1.0 References: <20190424043656.GA25754@admin.sibptus.ru> <201904240557.x3O5v6AK041737@gndrsh.dnsmgr.net> <20190424065223.GA28138@admin.sibptus.ru> In-Reply-To: <20190424065223.GA28138@admin.sibptus.ru> From: Stephen Stuart Date: Wed, 24 Apr 2019 07:45:13 -0700 Message-ID: Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop To: Victor Sudakov Cc: freebsd-virtualization@freebsd.org X-Rspamd-Queue-Id: 2EC578FC7C X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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, 24 Apr 2019 14:45:27 -0000 I call this in /etc/rc.shutdown.local to shut all VMs down gracefully and wait, perhaps a variant would help you. #!/bin/sh INTERVAL=5 /usr/bin/killall -TERM bhyve echo -n "/dev/vmm:" while test -d /dev/vmm ; do echo -n "" $(/bin/ls /dev/vmm | /usr/bin/wc -w) /bin/sleep $INTERVAL done echo " 0" Stephen On Tue, Apr 23, 2019 at 11:53 PM Victor Sudakov wrote: > Rodney W. Grimes wrote: > > > > > > > > I've noticed that it takes too long for Windows 2012 and 2016 servers > > > > guests to shutdown when I issue "vm stopall," several minutes even. > > > > > > > > Does vm-bhyve provide a way to power them off ungracefully if they > would > > > > not stop within a predefined time? > > > > > > > > Or is there perhaps a way to tune the guest OSes to react more > promptly > > > > to an ACPI shutdown? > > > > > > > > My primary concern is that my UPS and "apcupsd --kill-on-powerfail" > give > > > > me about 30 seconds of grace time before the power supply is cut > out. It > > > > is not sufficient for the bhyve box to shutdown shutdown properly > > > > because it waits for the guests to shutdown. > > > > > > For the present I think I've found a workaround not directly related to > > > vm-bhyve. I'm going to insert "service vm stop" into the doshutdown() > > > procedure in /usr/local/etc/apcupsd/apccontrol before the actual > > > ${SHUTDOWN}. It should give the VMs sufficient time to shutdown before > > > the actual /sbin/shutdown is executed. > > > > Make sure it does not do the waitall for pids or your going to > > sit here waiting for that to complete for a long time, ie until > > all vm's go to power off. > > In fact, this is my intention to sit here waiting for all VM's to go power > off. > > I can configure apcupsd to start the doshutdown() routine when there is > enough power in the UPS, like maybe for 20-30 minutes. > > > > > If you know of a better way to configure apcupsd so that it powers > down > > > > the UPS only after all the guest OSes and other daemons are safely > down, > > > > I'd appreciate that too. > > > > > > Do you think the above hack would have any negative effects? > > > > I think this is a reasonable approach given the current situation. > > > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49@fidonet http://vas.tomsk.ru/ > From owner-freebsd-virtualization@freebsd.org Thu Apr 25 04:10:30 2019 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 7F296158B449 for ; Thu, 25 Apr 2019 04:10:30 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 754248EEFC for ; Thu, 25 Apr 2019 04:10:29 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=/8+JoaqvVArWILrXtMsw/yJLn5q+YjtGhxfp2J2290E=; b=FhvpHUQboC0uRYTtgU2c1Gsm6r 5UpdQUsYARC7umsrY0UhpvBcyCHAXHWMIQMs3BkvBQAIb4w3z98JSH+W4xWUMJ6gYP/BXgbKiunL0 jnfdex3+7eQEdofkTL6DqzI8lghN+kPn8j6v/CAsQQntfb8veaQYf1fOJzYtJ3W2cocg=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hJViO-000DA5-8G for freebsd-virtualization@freebsd.org; Thu, 25 Apr 2019 11:10:28 +0700 Date: Thu, 25 Apr 2019 11:10:28 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Message-ID: <20190425041028.GA50526@admin.sibptus.ru> References: <20190421045143.GA49101@admin.sibptus.ru> <20190424043656.GA25754@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline In-Reply-To: <20190424043656.GA25754@admin.sibptus.ru> X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Thu, 25 Apr 2019 04:10:30 -0000 --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Victor Sudakov wrote: >=20 > For the present I think I've found a workaround not directly related to > vm-bhyve. I'm going to insert "service vm stop" into the doshutdown() > procedure in /usr/local/etc/apcupsd/apccontrol before the actual > ${SHUTDOWN}. It should give the VMs sufficient time to shutdown before > the actual /sbin/shutdown is executed. The workaround turned out useless: apcupsd sends the "kill power" command to the UPS before calling the doshutdown() procedure. F*ck, is there no correct, generally accepted way of powering off a busy FreeBSD server? Why am I inventing the wheel? > > If you know of a better way to configure apcupsd so that it powers down > > the UPS only after all the guest OSes and other daemons are safely down, > > I'd appreciate that too. --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcwTM0AAoJEA2k8lmbXsY0meYIALT5+1AeLBak/KOGr52fqMfA vNRy3S8zJj73MQwhDE5T6f6mz+ABrRbbQipXQWw590Pdd3n3dlM5Psj4UCuNddBN bD+PQixgStK+ZLHRJMD+Gh4OAR2Y8EzIp/N+LaJrHdg8s4MppWpcBGmcBuVUsaxQ U+9IwC1JQNPR8O67s0Zda3K/Nbf+9gO6tmUsIF44BfU6Snh6wLwB8Ya8lcS9dMkV cPIDY78FfCx8ZokreWbiHmkfxAv+awJZMHnwIzYQ+uQS2n8VRUuZtHmBuNpvssSK nWu5SaYXB6LF5dBreXjHHuhfoTxs7y3qLjxsxMMtenYPLxojP0x7vXeJJCOonPI= =adyu -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk-- From owner-freebsd-virtualization@freebsd.org Thu Apr 25 15:04:09 2019 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 114471599AE9 for ; Thu, 25 Apr 2019 15:04:09 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) Received: from admin.sibptus.ru (admin.sibptus.ru [IPv6:2001:19f0:5001:21dc::10]) (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 73C24894C1 for ; Thu, 25 Apr 2019 15:04:08 +0000 (UTC) (envelope-from vas@mpeks.tomsk.su) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sibptus.ru; s=20181118; h=In-Reply-To:Message-ID:Subject:To:From:Date; bh=GqCt5V1ObCbEWntKSvPdck5STH32mQ79WR5SRJZkPK0=; b=dXp1jGMpglH7gugZvDUMzerBEP vjx0xrVpAqNkHYG/szi5xHjaiqXlLPYSBMvF9Pc4glt2TeWgVt3d58drUiz9ofB7ghRUJp4hj5lZa 8iY4l1CLGfMuRFt6SGl6MDL/HPj/rISK6WJRyFhuSpWdToeStVMEwAINEVUHEoKETXRQ=; Received: from vas by admin.sibptus.ru with local (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hJfux-000GGZ-Kq for freebsd-virtualization@freebsd.org; Thu, 25 Apr 2019 22:04:07 +0700 Date: Thu, 25 Apr 2019 22:04:07 +0700 From: Victor Sudakov To: freebsd-virtualization@freebsd.org Subject: Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop Message-ID: <20190425150407.GA62313@admin.sibptus.ru> References: <20190424043656.GA25754@admin.sibptus.ru> <201904240557.x3O5v6AK041737@gndrsh.dnsmgr.net> <20190424065223.GA28138@admin.sibptus.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.11.4 (2019-03-13) Sender: Victor Sudakov 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: Thu, 25 Apr 2019 15:04:09 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Stephen Stuart wrote: > I call this in /etc/rc.shutdown.local to shut all VMs down gracefully and > wait, perhaps a variant would help you. >=20 > #!/bin/sh >=20 > INTERVAL=3D5 > /usr/bin/killall -TERM bhyve > echo -n "/dev/vmm:" > while test -d /dev/vmm ; do > echo -n "" $(/bin/ls /dev/vmm | /usr/bin/wc -w) > /bin/sleep $INTERVAL > done > echo " 0" Thanks for reminding me about /etc/rc.shutdown.local. I've tested a solution today and it seems working. 1. Start apcupsd with --term-on-powerfail apcupsd_enable=3D"YES" apcupsd_flags=3D"--term-on-powerfail" 2. Put the following line into /etc/rc.shutdown.local test -f /var/run/powerfail && /usr/local/sbin/apcupsd --killpower Now, when the UPS power is exhausted, apcupsd starts the shutdown procedure and exits. The system shuts down without any haste, as it pleases, and at the very end "apcupsd --killpower" is called and poweroffs the UPS. --=20 Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ --envbJBWh7q8WU6mo Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJcwcxnAAoJEA2k8lmbXsY0BE8H/3qJrBBNaXzlOXsL99eLmBWT /MCKBJa0+l2AueDgNyO3YWa4aKGtYwQJI4PrZDme9QAGv8Ijs1xXvgdCanfaquF9 HRSoC0wAy19lASkIW82xt+TVz4iyFtrlMBWrlr14rTrvxjWb6cMfct5jW66Iykhb WSHd8auLweqkkc1damoE2lRKKVJbuWEUHLn7JZoTc/C3Gwlrwijo3iDPUX+UyWM5 F3IC3Mri/zRhvbwEuqx5kNdc72sztpCN7Gc/yvzqh/Wq7EJXrRY0HKE8VPfohEF8 /P0hlZOasraYaGAoWnlHd6Nc7QmFs6SoSm/2smsVFEhe+M0//y7TTuOuE10fTUw= =p07H -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- From owner-freebsd-virtualization@freebsd.org Thu Apr 25 22:53:48 2019 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 C49D615807BC for ; Thu, 25 Apr 2019 22:53:47 +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 470DA6F57B for ; Thu, 25 Apr 2019 22:53:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id DEE2C15807B9; Thu, 25 Apr 2019 22:53:46 +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 5B48C15807B6 for ; Thu, 25 Apr 2019 22:53:46 +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 C9F5F6F573 for ; Thu, 25 Apr 2019 22:53:45 +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 25123C381 for ; Thu, 25 Apr 2019 22:53:45 +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 x3PMrjuK096970 for ; Thu, 25 Apr 2019 22:53:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x3PMrjZl096969 for virtualization@FreeBSD.org; Thu, 25 Apr 2019 22:53:45 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 212782] [bhyve] Increasing VM_MAXCPU to >= 26 will result in ACPI MADT table corruption Date: Thu, 25 Apr 2019 22:53:45 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rgrimes@FreeBSD.org X-Bugzilla-Flags: mfc-stable11+ mfc-stable12+ 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: Thu, 25 Apr 2019 22:53:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212782 --- Comment #5 from commit-hook@freebsd.org --- A commit references this bug: Author: rgrimes Date: Thu Apr 25 22:52:44 UTC 2019 New revision: 346715 URL: https://svnweb.freebsd.org/changeset/base/346715 Log: Acpi MADT table correction for VM_MAXCPU > 21 The bhyve acpi MADT table was given a static space of 256 (0x100) bytes, this is enough space to allow VM_MAXCPU to be 21, this patch changes that so VM_MAXCPU can be of arbitrary value and not overflow the space by actually calculating the space needed for the table. PR: 212782 Reviewed by: Patrick Mooney Approved by: bde (mentor), jhb (maintainer) MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D18815 Changes: head/usr.sbin/bhyve/acpi.c --=20 You are receiving this mail because: You are on the CC list for the bug.=