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 C2DB66C605 for ; Mon, 29 Mar 2021 15:38:19 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B1DD815E1D for ; Mon, 29 Mar 2021 15:38:19 +0200 (CEST) Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 45ECE15E09 for ; Mon, 29 Mar 2021 15:38:18 +0200 (CEST) Received: by mail-lj1-x22b.google.com with SMTP id u4so15979956ljo.6 for ; Mon, 29 Mar 2021 06:38:18 -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=PxGfnar4TricVYrFNTTuLk3LKpl5XRY5q2unD0dJAU4=; b=siuwMppJJgNdLicZG63jeI0kZpgWusoZpczonVGKdupJSDZGSOE0hvw2ihs4icAp49 rlBJVmGBU2FcDtSSlxNicwZBLLUB7AddkUv3ZdwTDo5TaciL80YWBoAjxG7RkM6sHyIE Y0sw6cQo8ma79LjlO+Yj7KdXFAoN7F9aj7V0hNesAGSXjTXTgYGlk5E7Ckqj/Hu8UPJc cEUlUt+sYhDdExf0oI8cIamocEUJ2Pjbb9kz/XuCoEOqoCwP9kwbHjtlPxR7X6Tx+qN9 nQ87A7HMAue+us/nuBcCZT+PgdYCUkxURugP4fC7SxbSLNeW9fZD8+8DH/TeP27vc/rp TnYA== 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=PxGfnar4TricVYrFNTTuLk3LKpl5XRY5q2unD0dJAU4=; b=JyE9nde2g41GYDtjhMlFRtBZODcnmHnGeqFo0dcokU0s/51QR1zfUP4dGH21Ll9IhQ +yjGvYDr7HR9TBA3wJkv2+AEYmroYIM3X480gJz81FTTM2oij//DdFxB4cGu3TqEtHkV wZ/6UYoHUmaFu88BpKlF3/NT43QTKXghZvpgy32XXyeFEapmu59AYe07WNtn0Zi8DJli bmkdpuxtqEHF/94S7UJXLVQGhbdpgwR6brBkHJ5qRm+sS0NBT0m2cHHWrMXA1TohKf5a 4E3dKBmoXTbNwv6RQDg1NsvDL4VJZW57c1HAgA6FJQGVvc45ryfUEHyd8F+n4ocvQec5 ZJ/A== X-Gm-Message-State: AOAM5315wXb8MeTIP2S9TnwFfmLTB3ziSfOLI3FCD614kMwxRy6JWk3E 3EyVq2YkyuQjAEmG20TRc4h4DCZ1PHi9Uayvh+Lk8P+LHSsyz94= X-Google-Smtp-Source: ABdhPJyrfoW3bXncGtwbG1+Tjs+rKN0v6ENOoZE4VM6MgLQekpnylSQ+0HDxHCS8SHU4PPwGDthcJ43wOEd7/o+axWM= X-Received: by 2002:a2e:868a:: with SMTP id l10mr17353328lji.343.1617025091146; Mon, 29 Mar 2021 06:38:11 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Leandro Roggerone Date: Mon, 29 Mar 2021 10:37:59 -0300 Message-ID: To: Proxmox VE user list X-SPAM-LEVEL: Spam detection results: 1 AWL 0.218 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:38:19 -0000 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 the 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 tell 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,media= =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 manag= er > > > > > 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 th= e > 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 te= ll > 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-configuratio= n.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 >