From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C64596C5EC for ; Mon, 29 Mar 2021 15:53:28 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id AF28216020 for ; Mon, 29 Mar 2021 15:53:28 +0200 (CEST) Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 id 6CE3F1600B for ; Mon, 29 Mar 2021 15:53:27 +0200 (CEST) Received: by mail-lf1-x136.google.com with SMTP id o10so18526327lfb.9 for ; Mon, 29 Mar 2021 06:53:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tecnetmza-com-ar.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=oTzOSKXA8WA0FwSkrsKZobzCPOZv9QyxbXNhdLbL/Bg=; b=jETp9a11B04ddMKkowRd8uSDWThGGVT7LYrMxAgK4uERftBuDPUzzEnaklnl2vsGS2 +gYoWapziz4jS+GDFz4Nv4HL8UyYOp4ZoFwz/bSxHqCHuFw9NB6ix0J7erG/UXYFhtIh hp5gUsERbETmuNIFZwOwOkBWRIx7TwSjn7X01Ja52p+sac3mqS45RQyzhsWuzy6VLtbW KWPwSrbzqE0Kw8aJwgBJLKUZinY8k79B0etFmwv7qzEWSKIPWTeClHr5j7OKHgHHjp7A NUhR0C++4d6iOEVn9ClXDtvGvfa1aoi+y6PckPIEti9SuCGmZ6UooO/WM/e8SesPV99y 7InQ== 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; bh=oTzOSKXA8WA0FwSkrsKZobzCPOZv9QyxbXNhdLbL/Bg=; b=p2DqxWzUipMfCZAFfGF6BDcroyzXlfUGMNGgbm1LZyGyx1E3VZos10UlDqBd4RcxbD wfE8AoqsfKCwXnZ4Ff3LK9NOlTlXjysZcEWbFBCfxIRrvk6HB1iSTF50BIIlUcnIOAuT 4qtkeZuII7G7/w4sED5sBJVZrBiz53sumV45fmlGU1y2wAvkZHstJuAtC4Nu5CTygmDJ wX7UTBUlthti0gGqLNMC0qsLr2iNjpTi434fz4m0NYLW+w+Q8qsPRXTQToAv62ePQfpN 5Tdkz/tL6aEm6yPyeayNCdd7uq1c5iiaiTr0nKe2PpohdG2LYgcZb2uOqoJhMJLb7NyS pXKg== X-Gm-Message-State: AOAM533fTe0y+U2+RfpptjlNSF9g10TYlhV6jR68ae5Yw6fKW+w9iCu/ aVLfyBCUOVaoZIx9STgzyMIoo7gqeTwHFKtF7GKA8II7CqOYTGGZ2g== X-Google-Smtp-Source: ABdhPJxgVQ+FSAF+bHMiLqeXJuIkxWxp0kTJTshJMfpl6Spgw8XCPs/a6T5OFiXnePcOs1xe2E5I9EmhNICKjl3vR+o= X-Received: by 2002:a19:5005:: with SMTP id e5mr17317048lfb.109.1617026000583; Mon, 29 Mar 2021 06:53:20 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Leandro Roggerone Date: Mon, 29 Mar 2021 10:53:08 -0300 Message-ID: To: Proxmox VE user list X-SPAM-LEVEL: Spam detection results: 1 AWL 0.203 Adjusted score from AWL reputation of From: address 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 HTML_MESSAGE 0.001 HTML included in message 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_SOFTFAIL 0.972 SPF: sender does not match SPF record (softfail) T_KAM_HTML_FONT_INVALID 0.01 Test for Invalidly Named or Formatted Colors in HTML Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] Windows sever 2016 vm with very high ram usage X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2021 13:53:28 -0000 BTW ... Im using Default (kvm64) in cpu config. Is there other option recommended for Windows VMs ? I can not find soem doc related to this. Regards. Leandro. El lun, 29 mar 2021 a las 10:37, Leandro Roggerone (< leandro@tecnetmza.com.ar>) escribi=C3=B3: > Hi guys , thanks for your words , have some feedback: > > Maybe Proxmox cannot look inside the VM for the actual memory usage > because the VirtIO balloon driver is not installed or active? Or maybe th= e > other 90% is in use as Windows file cache? > I think so ... > Dont know about windows file cache ... > > Have you installed the VirtIO drivers for Windows? Are you assigning too > many vCPUs or memory? Can you share the VM configuration file? Can you te= ll > us something about your Proxmox hardware and version? > No , I have not ... now you mentioned im reading about VirtIO , I will > try to install and let you know how it goes > Should install it no my pve box or directly inside windows vm ? > I'm assigning max vCPUs abailables (24 , 4 sockets 6 cores) and 32gb for > memory. > (I really don't know about any criteria to assign vcpus) > > This is VM config file: > > root@pve:~# cat /etc/pve/nodes/pve/qemu-server/107.conf > > bootdisk: ide0 > > cores: 6 > > ide0: local-lvm:vm-107-disk-0,size=3D150G > > ide1: local-lvm:vm-107-disk-1,size=3D350G > > ide2: > local:iso/Windows_Server_2016_Datacenter_EVAL_en-us_14393_refresh.ISO,med= ia=3Dcdrom,size=3D6808810K > > memory: 32768 > > name: KAIKENII > > net0: e1000=3D1A:F1:10:BF:92:0A,bridge=3Dvmbr3,firewall=3D1 > > numa: 0 > > ostype: win10 > > scsihw: virtio-scsi-pci > > smbios1: uuid=3Ddaf8f767-59c7-4e87-b3be-75d4a8020c38 > > sockets: 4 > > vmgenid: a7634624-1230-4a3e-9e7c-255d32ad2030 > > My PVE is: > CPU(s) 24 x Intel(R) Xeon(R) CPU X5680 @ 3.33GHz (2 Sockets) > Kernel Version Linux 5.0.15-1-pve #1 SMP PVE 5.0.15-1 (Wed, 03 Jul 2019 > 10:51:57 +0200) > PVE Manager Version pve-manager/6.0-4/2a719255 > Total Mem =3D 64GB. > > That's all. > Thanks > > > > > El vie, 26 mar 2021 a las 11:40, Arjen via pve-user (< > pve-user@lists.proxmox.com>) escribi=C3=B3: > >> >> >> >> ---------- Forwarded message ---------- >> From: Arjen >> To: Proxmox VE user list >> Cc: >> Bcc: >> Date: Fri, 26 Mar 2021 14:39:13 +0000 >> Subject: Re: [PVE-User] Windows sever 2016 vm with very high ram usage >> On Friday, March 26th, 2021 at 15:28, Leandro Roggerone < >> leandro@tecnetmza.com.ar> wrote: >> >> > Hi guys , Just wanted to share this with you. >> > >> >> > After creating a VM for a windows sever 2016 with 32 GB ram I can >> > >> >> > see continuos high memory usage (about 99-100%). >> > >> >> > I have no running task , since it is a fresh server and from task >> manager >> > >> >> > can see a 10% of memory usage. >> > >> >> > Regarding those confusing differences, server performance is very bad. >> >> Maybe Proxmox cannot look inside the VM for the actual memory usage >> because the VirtIO balloon driver is not installed or active? Or maybe t= he >> other 90% is in use as Windows file cache? >> >> > User experience is very poor with a non fluent user interface. >> > >> >> > Is there something to do / check to improve this ? >> >> Have you installed the VirtIO drivers for Windows? Are you assigning too >> many vCPUs or memory? Can you share the VM configuration file? Can you t= ell >> us something about your Proxmox hardware and version? >> >> > Any advice would be welcome. >> >> >> Maybe search the forum for similar Windows performance questions? >> >> >> https://forum.proxmox.com/forums/proxmox-ve-installation-and-configurati= on.16/ >> >> > Thanks. >> >> best of luck, Arjen >> >> >> ---------- Forwarded message ---------- >> From: Arjen via pve-user >> To: Proxmox VE user list >> Cc: Arjen >> Bcc: >> Date: Fri, 26 Mar 2021 14:39:13 +0000 >> Subject: Re: [PVE-User] Windows sever 2016 vm with very high ram usage >> _______________________________________________ >> pve-user mailing list >> pve-user@lists.proxmox.com >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >> >