Search results

we need to know the two "sides" specs and if inter VM or from/to physical.

if you iperf3 inter VM, hw NIC is not used, it's a software network flow, bounded to CPU.

We need some ip, nobody can guess your network topoly.

How did you that so far ?

:eek:

except high idle, have you notice performance impact in regular load or cpu benchmark ?

it's not PVE side thing. You need to install yourself a reverse proxy as LXC or VM.

Here add -global scsi-hd.discard_granularity=8M to args: 8M because with 2M Windows 10 v1809 / Server 2019 doesn't report "SLAB" size. Not yet tried with PVE v9

This is the result of failed not-so-annoying nag screen removal attempt.

Systemd-boot is installed with UEFI Not Enabled Secure Boot with ZFS/BTRFS. GRUB bootloader is installed when Secure Boot is enabled in UEFI, even with ZFS or BTRFS.

Attaching USB disks directly on the host will be faster and easier.

Not required as it's included since v3

try with Windows Server 2019 or 2022. try with Windows 10 or 11

then try boot into Safemode

please use bs=4k for iops then bs=1m for bandwidth what is server model ?

Server grade are often set in Balanced Performance/Energy, set to Max Performance in BIOS/UEFI.

no, Virtio-scsi driver is correctly installed for Storage Controller, showed in your screenshot. What do you want to test ? iops or bandwidth ? becauses each requires different settings. Mainly bs=4k for iops / bs=1M for bandwidth. BTW, NVMe is limited in 1 VM at a time. You need to test multi...

exact model will be more useful. Windows 10/2019 does not run smooth on this 10 years old Xeon CPU, even more when virtualized. Many cores but run too slow for modern Windows. In my exp. , was only OK with Windows 7/8/2008r2/2012r2

it's expected that VirtIO scsi ( and VirtIO block) driver is only for Storage Controller not for disks itself. Like real life with hardware storage controller like raid controller.

what do you mean ? what physical cpu do they have ?