Search results

what about mdadm Raid10, which is recommended ? raid5 isn't performance oriented.

weird, ZFS should be slower than mdadm. but I haven't exp neither hw with mdadm over nvme. what numbers for single nvme vs mdadm ?

I don't think hw controller will help you. If you need one big space, I would use regular software raid mdadm. if you can split your process, create one datastore per disk.

it's only peak perf in multi threads and long queue. vNIC isn't limited to 10 Gb/s, it's only cosmetic, it's limited to CPU as it's an emulated NIC. imo, it's ZFS which slowdown your process. Try a LXC Ubuntu as Samba Server, as LXC use bridge instead a vNIC. non, Windows cannot do this...

eno1 ip must be different from vmbr0 ip. by "act as router", I would mean as Masquerading (NAT) router, where guests has private LAN. ( https://pve.proxmox.com/wiki/Network_Configuration#sysadmin_network_masquerading ) If provider allow assign public ip directly within guest (require...

cannot reproduce here, even if Windows OS 32bits cannot assign more than 4GB RAM , VM set to 16GB on vanilla pve 8.2 (shipped with qemu 8.1) works.

have you tried with reverting to the default qemu 8.x ?

it's known issue with SDN when host act as router, its virtual MAC bridge is random. There a post which spirit explain, it seemed to me last updates set fixed MAC. edit: Post in thread 'Windows VMs with SNAT and DHCP recognizing new networks on each reboot'...

Adapter name in device manager ? or only the network name ? do you use SDN ?

check if ARC size is correct with arc_summary

if you haven't limited ZFS ARC memory size, it will use 50% of your host RAM. Proxmox iso nowadays set it to 10%. As you've done manual installation, seems the 50% default limit is used.

Windows sleep by default after 30 minutes. afaik, VM can't go in sleep because virtual basic video, but since you've pass the GPU, Sleep function is available.

I doubt SSD will unlock, try it, but, imo, no invest should be done in an E5-2620.

only as VM running on pre 2016 hardware.

are they used as RDS ? of course all RDS never to be public opened. imo, RDS on 2008r2 (= Win7) running HDD are acceptable, then RDS 2012r2 = Win8.1 begins hungry, then 2016 to 2022 (=Win10) as RDS are heavy, breaking HDD usage. of course context usage needs to be taken into account.

what do you mean with "internal only"?

Check BIOS to set Max Power / Performance. Default is often best effficiency instead best performance. btw, nowadays, running Windows as RDS VM HDD require more than patience.

you've created a hw raid 10 array, isn't it ? for this old cpu, you need to disable mitigations : https://forum.proxmox.com/threads/ubuntu-20-vm-much-slower-than-in-esxi.149444/post-677546

don't forget to edit title to set SOLVED tag.

I would connect to host directly : 1/ VPN (when you connect from random WAN ip) 2/ Enable and Add Firewall rules if you connect from static WAN ip. 3/ Add Firewall rule to allow SSH only on public ipv6 (greatly reduce bot access, at least, imo for the next years)