Now installed the latest free BIOS update from HPE (warranty is out and we don't have a contract) from 2019. (Before, it was 2016...)
Will look what happens...
Update: I was NOT COMPLETELY WRONG... the "freezing" (so to say - the spinner turns infinitely) is gone... but the performance is still a lil bit poor. But over the night, Windows 10 has not given up working.
So it seems...
...is was that "Balloon" device.
After unchecking "Balloon" in VM RAM options, the VM is much more faster.
So far * - all is ok!!
* BUT: MAJOR QUESTION: Why Proxmox does not ask the user which OS he want to install? I mean it like [e.g.] VirtualBox... VirtualBox asks the user...
Didn't help... now i set it back to defaault but with "I/O Thread" activated... will see what happens...
but i can't see any other way than to try all combinations and wait for ~2h until it occurs...
Additional info: It doesnt seems to be a "complete" freeze, just an infinite lagging... the mouse cursor has this spinner animation and it never stops ince almost ~2 hours until i get that message:
No change with "latest" instead of "stable" VirtIO drivers: "Ballon" has the same driver date on stable and on latest:
DriverVer = 08/30/2021,100.85.104.20800
Maybe the problem is somewhere here, on "Advanced" options?
"I use the bullseye debian-backports kernel because proxmox 7.x will not work on HP ProLiant ML360 Gen9"
Maybe a BIOS update would fix that, but we don't have access to all HP BIOS updates because the server is out of warranty...
And, i use software RAID-5 on /mnt/raid5 path... but that should also work, can't be the reason for that behavior i.m.o. - otherwise, ther other 3 Linux VMs would also not work stable if the issue is a filesystem I/O problem on host OS...
And also the different kernel would not be reason - same...
Maybe i will better go back to M$ Hyper-V for Window$ VMs and using Proxmox only for Linux (or UNIX) VMs...?
But now i will try it with "latest" instead of "stable" VirtIO drivers... maybe that will solve my issue, but i don't think
-> yesm seems so. But that's only a speed issue (i've changed many vm parameters to figure out the freezing problem), now with re-enabling write-throgh cache windows starts... (until it freezes the next time... ;-) )
Maybe to re-enable cache will solve that speed issue (currently, it will not freeze)... but write back cache seems to be buggy on proxmox 7.x version...
It freezes (on WebGUI and also on Remote Desktop)... while other 3 VMs (Debian 11) are stable since weeks... where shoud i start to debug - i have no idea...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.