From owner-freebsd-stable@freebsd.org Sat Apr 24 09:44:01 2021 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C29255F8869 for ; Sat, 24 Apr 2021 09:44:01 +0000 (UTC) (envelope-from robbelics@gmail.com) Received: from mail-io1-f43.google.com (mail-io1-f43.google.com [209.85.166.43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 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 4FS5p86pf3z4kBD for ; Sat, 24 Apr 2021 09:44:00 +0000 (UTC) (envelope-from robbelics@gmail.com) Received: by mail-io1-f43.google.com with SMTP id k25so8166718iob.6 for ; Sat, 24 Apr 2021 02:44:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=MLu3LcpkICPdfqSNLSslxkpBzXM4/9qzA9eiaMDnnhM=; b=A7DTh51XqJyNPx8kPd+77jarWVYGmb36UYjRQebwepHLROqHissAwYm39BEcwcTO4U uDllYht2XCwfqyP+XJ8vCbUvPoI/c1JSI1jxiKwGm5iiIeLIclpoMr3aYju3CSTK70HE rO7IgWA50dPqnjzfN2AvHJAekEJ0FM1fggHJDWKOWs2NfdpzIjMn8//5DXsu2f2WRuVM E9EKgCtBEU8C7BHIgCLQg5f/tCGUqGuA7i1t0L2j4XjIHvU0XhuNzeF0R9mfUsYGJ24y n1ch9v6Wqlc8NmlnyUiwH7q+X21oN2R2lh++SuQals0HuGd36mO64mRJyZlYJbhuO2r6 afYw== X-Gm-Message-State: AOAM532xLSU9VWZKICOuQT94b+sFw2NdxYqwTcTDnagrhE44Hn2zcjpu IuMCh3wyr4qi/uZ6Y9r+rUgPSjk0Fkki74F9a6n14BKFpQ== X-Google-Smtp-Source: ABdhPJyeZTFpMncOsUAlCeW+mYcdYN1y9VrvLGd4OOhlthJIXFbO8RgBpNp9/gnVwokpdj4nsQVH5TTM236KjdcMld4= X-Received: by 2002:a6b:e30e:: with SMTP id u14mr6358794ioc.18.1619257439763; Sat, 24 Apr 2021 02:43:59 -0700 (PDT) MIME-Version: 1.0 From: Rob Belics Date: Sat, 24 Apr 2021 04:43:49 -0500 Message-ID: Subject: Re: FreeBSD 13.0 terrible performance in KVM To: freebsd-stable@freebsd.org X-Rspamd-Queue-Id: 4FS5p86pf3z4kBD X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=belics.com (policy=none); spf=pass (mx1.freebsd.org: domain of robbelics@gmail.com designates 209.85.166.43 as permitted sender) smtp.mailfrom=robbelics@gmail.com X-Spamd-Result: default: False [0.10 / 15.00]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_DN_NONE(0.00)[]; FORGED_SENDER(0.30)[rob@belics.com,robbelics@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.166.43:from]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[rob@belics.com,robbelics@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[209.85.166.43:from:127.0.2.255]; NEURAL_SPAM_SHORT(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.43:from]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.43:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-stable]; DMARC_POLICY_SOFTFAIL(0.10)[belics.com : SPF not aligned (relaxed), No valid DKIM, none] X-Mailman-Approved-At: Sat, 24 Apr 2021 18:24:51 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Apr 2021 09:44:01 -0000 > I hope some other folks out there running FreeBSD on KVM as well. I set up a base VM while doing so I noticed that the disk operations are very slow. Many times I edit a file in vim or try to run a command there is a huge lag. I noticed this on Ramnode--my VPS--and tech support there has told me it is due to their container set up with Docker(?). They made some adjustments and then it worked fine.