Search results

wrong, you miss the point of PLP. it's like a RAID cache accelerator protected by battery. PLP ensure data is always written to disk, even if crash or power loss.

upgrade scsi directly from Windows Device Manager.

zfs with consumer grade ?

for me v266 fixed the hang, I'm unable to hang on my two reproducer in a VM test. with v240 , I'm easy able reproduce the hang in VM + windows log event id 129 vioscsi reset device with CrystalDiskMark test NVMe Profile 5x8GB Read&Write. Will update production VM this week-end.

edit: it seems :cool: :cool: :cool: , I'm not able yet to hang a VM with v266

UFW is not installed in Proxmox

Turn off "MAC filter" under PVE VM -> Firewall -> Options

Enabling Firewall at Datacenter level is mandatory, if not, firewall isn't active for the Node and its Guests.

HDD is the bottleneck, even bare metal Win10 is slow, even more when Windows Update active. switch to SSD is mandatory. mitigations=off as kernel will help old cpu.

edit: indeed, set discard_granularity is the correct fix. Thanks @ky41083 for sharing link where is tip for global set discard_granularity. btw, I wonder if the SSD model has something to do with it. a side fix, downgrade virtio scsi to version 0.1.208...

shutdown + start VM required to use new version.

it's expected, firewall need to be enable on the three levels.

It should work in (my) theory, but I'm not a VLAN user :-/ Have you tried attach vmbr1.1002 to VM without VLAN tag in VM's NIC ?

isn't registering MAC to public ip required ?

Where is defined your ip .65 ?

VLAN is 1002 but you said VLAN 1000 in your first post. Are VLAN provided by ionos ?

post your pve /etc/network/interfaces + ip a into CODE tags please.

you don't need NAT from 161 public ip if 1 guest use the 161 ip, juste remove ip from vmbr1 interface and set iface vmbr1 inet manual edit: you lost me, where are others ip in your interfaces ? + put content into CODE TAG

it can't work, only one default gateway is possible in a OS. do not set additionnal public ip on vmbr1 but directly in your guest VM/CT which has vmbr1.

you can make a netsh portproxy if VM is Windows or a socat if VM is Linux.