Samsung Evo Speeds in Windows 10 VM

[fahadshery]

Hi,

I have installed an `1TB Evo Plus` in my proxmox server.
However, once the windows vm is up and running. The read/write speeds and `significantly` lower than the actual spec.
Why would that be the case?

I attached the NVME using lvm.

thanks

 

[oguz]

hi,

However, once the windows vm is up and running. The read/write speeds and `significantly` lower than the actual spec.

how do you mean exactly?

are you checking the r/w speed inside the VM or on the host?
with which tool are you checking it?

Why would that be the case?

could be a lot of reasons... hard to tell without you posting any information

please post the outputs from the following commands:
* pveversion -v
* qm config VMID (VMID is your windows VM)
* fdisk -l 2>/dev/null | grep nvme -C 2

 

[fahadshery]

are you checking the r/w speed inside the VM or on the host?
with which tool are you checking it?

Yes, checking within the Windows 10 VM. Using Crystal Disk Mark
Here are some of the results:

could be a lot of reasons... hard to tell without you posting any information

please post the outputs from the following commands:
* pveversion -v

pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-3-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-8
pve-kernel-5.13: 7.1-6
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.4-1
proxmox-backup-file-restore: 2.1.4-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

* qm config VMID (VMID is your windows VM)

qm config 105
agent: 1
balloon: 0
bios: ovmf
boot: order=ide0;ide2;net0;sata3
cores: 32
cpu: host,flags=+pcid
efidisk0: nvme1tb:vm-105-disk-1,efitype=4m,size=4M
hostpci0: 0000:05:00,pcie=1,x-vga=1
ide0: nvme1tb:vm-105-disk-0,cache=writeback,discard=on,size=128G
machine: pc-q35-6.1
memory: 16384
meta: creation-qemu=6.1.0,ctime=1643302514
name: win10iot
net0: virtio=DA:8A:D6:EC:56:16,bridge=vmbr0,firewall=1
numa: 1
ostype: win10
sata3: iso_images:iso/virtio-win.iso,media=cdrom,size=543390K
scsihw: virtio-scsi-pci
smbios1: uuid=a8049ca6-0b0d-4e9d-93a7-ad75e09598b6
sockets: 1
vmgenid: 80d9b42b-b2ab-4a39-a4d6-c885e6f74fe4

* fdisk -l 2>/dev/null | grep nvme -C 2

Disk /dev/mapper/nvme1tb-vm--105--disk--0: 128 GiB, 137438953472 bytes, 268435456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 6793CF69-3185-4E1B-B2C7-36C34B627919

Device                                         Start       End   Sectors   Size Type
/dev/mapper/nvme1tb-vm--105--disk--0-part1      2048    206847    204800   100M EFI System
/dev/mapper/nvme1tb-vm--105--disk--0-part2    206848    239615     32768    16M Microsoft reserved
/dev/mapper/nvme1tb-vm--105--disk--0-part3    239616 267387532 267147917 127.4G Microsoft basic data
/dev/mapper/nvme1tb-vm--105--disk--0-part4 267388928 268431359   1042432   509M Windows recovery environment


Disk /dev/mapper/nvme1tb-vm--105--disk--1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes

 

[oguz]

okay first thing, you should make sure the virtio drivers are installed, and use a virtio scsi bus with virtio-scsi disk controller instead of ide for the VM (this should make some performance improvements).

also take a look here for our best practices [0]

please try that and let me know if it helps!

[0]: https://pve.proxmox.com/wiki/Windows_10_guest_best_practices

EDIT: use scsi