Search results

The Benchmark kills the complete proxmox host not only the VM. That is really crazy ...

:-) :-) but its good to know that this setup is working as production server.

@omegamen exactly the same. I don't think that this messages are critical. can you do a benchmark with CrystalDiskMark in the VM (windows server 2016 essentials)? of course only if this is a test server ...

here it is: proxmox-ve: 5.1-31 (running kernel: 4.13.13-1-pve) pve-manager: 5.1-39 (running version: 5.1-39/5fa9d6c1) pve-kernel-4.13.4-1-pve: 4.13.4-26 pve-kernel-4.13.13-1-pve: 4.13.13-31 libpve-http-server-perl: 2.0-8 lvm2: 2.02.168-pve6 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster...

I too have this issue. (Proxmox 5.1-39) During Windows Server 2016 Essentials bootup it trigger the Error Messsage on Console. But what is really strange that when I do a benchmark with CrystalDiskMark in the VM the complete Host crashes! That is very reassuring but that is another topic ...