Recent content by RCK

I'm totally agree, this kind of hardware is not for for production. What is interesting here is that the v208 windows driver doesn't kill the VM, contrary to v266 + v271 (blk_drain in block-backend.c with iothread=1)

Thoses tests were done on a very simple station: Ryzen 7 5700X + SSD Crucial MX500 sata + Local Thin LVM. When I will have time, I will also test PVE 8.4 and Qemu 9.2

Well, I also had to rollback from v266 / v271 to v208 to be stable again. :( I have a workload to run scsi stresstest with different KMS tuning : It's using OODefrag to run "complete/name" hard drive optimisation 4 times consecutively (htop = 100% Disk IO)...

It just happened to me. The real problem is that the design of shutdown button is the same for "node" or "vm". Idea : If PVE team can change the picto fa-power-off to fa-plug for halt one node, it would be less confusing :)

Thanks for the info ! v271 have been released 15 days ago, do you know if the viostor fixes you were talking about are inside ? https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/

Hello Kwinz, I just setup a new proxmox 7.4 cluster with 3 x Dell Poweredge R630 and the DRAC hardware watchdog like you did here, and I don't see this problem when I manually reboot one node. (I can't see in my drac log : "The watchdog timer power cycled the system.", so I think the node...

I have the same question :) For me Win2022 should be on ostype: win10, because his kernel is based on 21H2_build_19044 (same as Windows 10 LTSC 2021)

Awesome, thanks for the information Fiona :)

Hello All, I'm looking to extract one vma backup directly from one file.vma.zst. I know I could unztd the file.vma.zst first, then use "vma extract" on this file, but the challenge is to use the standard output to not write the temp .vma file :) When restoring backup, proxmox is using such...

I'm wondering the same thing :) Did you try with and without T8038 flag and check the number of context switches ?

From my test with SMBv3, discard is not working like NFS < 4.2

Hello guys, I confirm the problem with .qcow2 on NFS v3 , v4 , and v4.1 between proxmox v6.2 and Synology NAS v6.4 Discarded files are not deleted inside the .qcow2 file on the NFS (confirmed with qemu-img info command). Let's hope Synology will implement NFS v4.2 soon !

Okay, this is strange, I also test here with another Chrome version 89 + Win10x64, and this time the console is OK !

Hi dcsapak, I would like to know what version of Chrome are you using with no websocket problem :) I have the problem with Win7x64 + Chrome Version 89.0.4389.114 (Build officiel) (64 bits) Look at the attached files for the WS problem in console:

I can confirm the problem here, I got a bunch of proxmox without letsencrypt (they don't have internet, no way). The vnc console is: - working fine with Firefox 87 - working fine with Chrome Embedded Framework 88 - does NOT work with Chrome 88 - does NOT work with Chrome 89 There must be...