OK, I'm quite confident that I've found and isolated the problem (and will drop it on github soon).
So let's start with the analysis. At first, be careful that virtio releases in time are not relevant to the commit dates.
I mean that if you see...
It is also going to be a significant performance hit, especially when running under a hypervisor where nested virtualization must be enabled. The question is whether it is worth it or not. For a server that presumably doesn't have interactive...
If you made manual changes directly to the /etc/network/interfaces file, you can apply them by running ifreload -a
from the docs : https://pve.proxmox.com/wiki/Network_Configuration
1/ Firewall is not related as iptables PREROUTING bypass firewall.
2/ open 3389 publicly is not recommended as bots will try thousands credentials per seconds.
Windows does that (assign an APIPA address) when the IP is in use somewhere in the network and some device replies to the ARP discover for the address you've entered in the configuration.
you hit this bug :
(workaround is direct upload with scp / winscp)
Post in thread 'Proxmox VE 9.0 ISO Upload Corrupts Some Windows Server 2025 ISOs'...
Use RTM iso, as Windows updates itself monthly, it makes no difference.
( I don't see anymore the point of refreshed media, as each month, it'll outdated)
Yes. this isn't news or a mystery.
ZFS has many OTHER advantages over lvm on block. performance is only one factor; if the zfs subsystem is providing SUFFICIENT performance for your application it is by far preferrable. You might want to...
Hi all, I'm the author of this ass-kicking post. After more than year, I'm back to service, as bug hunting never ends.
I'm sorry that I've missed many of the questions and messages, but let's move forward, we have another urgent problem(s).
In...
SQLServer also had issues with storage virtio driver 0.1.285-1 in a heavy-load Windows Server 2016 and 2019 VM (Disk is a ZFS vdev).
DESCRIPTION: Read from file 'H:\SQLSERVER\db01_3.mdf' at offset 0x000007023d0000 succeeded after failing 1 time...
Hi @santiagobiali, I can confirm this behavior. WS2025 with SQL2022 and 0.1.285, highly-stressed test environment with such sql bugs, but no host or quest system errors (i.e. nothing like scsi reset, as I mentioned earlier: scsi reset bugs). So...