From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <jmr.richardson@gmail.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 5CEA5C7D8 for <pve-user@lists.proxmox.com>; Sat, 8 Jul 2023 16:34:39 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4479732B9D for <pve-user@lists.proxmox.com>; Sat, 8 Jul 2023 16:34:09 +0200 (CEST) Received: from mail-oa1-x2a.google.com (mail-oa1-x2a.google.com [IPv6:2001:4860:4864:20::2a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-user@lists.proxmox.com>; Sat, 8 Jul 2023 16:34:08 +0200 (CEST) Received: by mail-oa1-x2a.google.com with SMTP id 586e51a60fabf-1b06da65bdbso2593383fac.1 for <pve-user@lists.proxmox.com>; Sat, 08 Jul 2023 07:34:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688826840; x=1691418840; h=content-language:thread-index:content-transfer-encoding :mime-version:message-id:date:subject:to:from:from:to:cc:subject :date:message-id:reply-to; bh=HhtvfC8si0EgbzXowAXpnk7+U5pXWKP/n6sXxdcvmhs=; b=nZ57xdv4/vIazgDRW2LHPtiaVerP49d+8mzzlyFIFkdcF+uruyMwkITqawOHWum8m0 WsoAV4Dnce7F3BEfkzkEi7CRYIKxIzyentx3j7MTSSRkS0f+rYbM3/LRKWBejtNjI3qS rFeH7n7n9kLTHT2Kx9OwZq8UQzP76taQXSyVvZq5xVxHrC0rR4tC2N2ppdYK5B3wW9MV Gyx7pygPq8Vn+ODO2FHdKHnLvdnjYVhhfwDH6lvrmnW5JrKipWvtqRDmvdSYdgactWD+ lTBkqe77wp7Fizccxym5d4e2Afw5qGp+jvwOnpkfzJGNRCl7lgJRMStaezgYXYggKEMH hW6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688826840; x=1691418840; h=content-language:thread-index:content-transfer-encoding :mime-version:message-id:date:subject:to:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=HhtvfC8si0EgbzXowAXpnk7+U5pXWKP/n6sXxdcvmhs=; b=DRZ1VM/lIeWz1+gKFcbFjaCJMSrktALzqvzxqUzfcjhrXJ6UJe0+g1xmW4V8plkgmB PHoEVfQ1AoHxOsWfquD018qbDCOE12K9BOf5Qr0QnYQmoVorO+Y0FeemwZenTx8Nfy7D T48T9+tDy2gOFbxnWY5Pc9KDhp2ehlb6J5fWap0q2KqnpRDtOEFi/8W36PzyQ2B/cwVX gbCIPctKxJocPzSYH4znlgwTD/oYVd/dNzuw6KKrNZkczTEKqsTbJ2LYde8OQs2rx7SB d/HJh1g8UjxfwE42JHkLCPTyoCMonj/oYT2rEe2W7J1nJlk8a754RXVBTC8THIcT6pbv wDMw== X-Gm-Message-State: ABy/qLZ01SqTWsHFWg7IJkUWdIcFpyFCeVeyr19grBMvlewwyNuX//iZ WiVsjYBI+EFbzH6GeZdaJFd/tCVV9fI= X-Google-Smtp-Source: APBJJlGc0VBdIf/hUZiog6oS/JEgBObVpmUPaJaoJLkHCVMJaykJ8/nu0neLWOoWyBlaEVQjJzS9zg== X-Received: by 2002:a05:6870:c0d2:b0:177:ad57:cb36 with SMTP id e18-20020a056870c0d200b00177ad57cb36mr8946770oad.27.1688826840188; Sat, 08 Jul 2023 07:34:00 -0700 (PDT) Received: from JRT7500 (076-085-083-050.res.spectrum.com. [76.85.83.50]) by smtp.gmail.com with ESMTPSA id dx26-20020a056870769a00b001a68feb9440sm2804357oab.9.2023.07.08.07.33.59 for <pve-user@lists.proxmox.com> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Jul 2023 07:33:59 -0700 (PDT) From: "JR Richardson" <jmr.richardson@gmail.com> To: <pve-user@lists.proxmox.com> Date: Sat, 8 Jul 2023 09:33:57 -0500 Message-ID: <000601d9b1a9$3b35ef00$b1a1cd00$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdmxqTqmH3UTERb1TmO20zTmz2KEqQ== Content-Language: en-us X-SPAM-LEVEL: Spam detection results: 0 AWL -0.563 Adjusted score from AWL reputation of From: address BAYES_20 -0.001 Bayes spam probability is 5 to 20% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [PVE-User] Question on Enabling Disk I/O after disk is in use X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> List-Post: <mailto:pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Sat, 08 Jul 2023 14:34:39 -0000 Confirmed, when enabling SSD or Disk I/O, you must shutdown VM before changes are effected. Thanks. JR Hi I always edited disk I/O limits while VM was running without issue and the new limit was immediately enabled. Ciao Il 06/07/23 21:04, JR Richardson ha scritto: > Hey Folks, > > I recently upgraded some hypervisors from spinning disks to using SSD > storage. The VMs were created without SSD or Disk I/O settings > enabled. Any thoughts on enabling these settings for disks, would I > have to turn off the VMs first or what would the implication be if > done while VM is running? > > I have a some VMs that are heavy disk i/o usage and want to increase > performance where possible. > > Thanks. > > JR