Recent content by djzort

i cant think of any reason not to use virtio, but be sure to disable all the different offloading in the firewall

Are you using virtio network cards or intel? Did you disable all the offloading in pf/opnsense? See also https://pfstore.com.au/blogs/guides/run-opnsense-in-proxmox

Did you find a solution to this?

maybe play with those settings and try the bleeding edge virtio-scsi drivers?

ah i read your comment again and see that you are using 141, which afaik is still "Stable" is the fsgsbase flag present on your cpu? also, have you set ignore_msrs ?

virtio-blk or virtio-scsi? it worth noting that the latest virtio network drivers have issues with windows server 2016 - see https://forum.proxmox.com/threads/virtio-driver-crashing-high-load.45609/#post-217865 it may well be the case with disk's too

the bad news is that my solution was to get new hardware. i cant say if my problem was a genuine bug in software or a hardware fault.

Sounds like exactly what I have, and whats in that link. In your old kernel, check and see if ipmi_si is loading: lsmod | grep ipmi look in /etc/modprobe.d/*conf files and see if its configured at all you can blacklist it with something like: echo "blacklist ipmi_si" >...

I have just had this same problem, it seems to be https://bugs.archlinux.org/task/57429 blacklisting ipmi_si seems to get things running - but not having ipmi_si loaded sucks it has nothing to do with ZFS etc.

using driver 149 and NetKVM this is quiet eash to replicate. Just install iperf3 in the vm and run it as iperf server iperf3.exe -s Turn the windows firewall off (or allow port 5201 tcp) Then on another machine (i just used the proxmox host) again install iperf3 and run iperf3 -c 192.0.2.2 -w...

ok thanks for quick reply. This seems to be my problem https://forum.proxmox.com/threads/virtio-driver-crashing-high-load.45609/#post-216990 noting it to help the next guy

anyone else had this? i have this with netkvm nic

I think i may be in serious trouble root@saito:/var/log# thin_dump /dev/pve/data_meta0 > /tmp/foo.txt root@saito:/var/log# grep superblock /tmp/foo.txt <superblock uuid="" time="0" transaction="6" data_block_size="128" nr_data_blocks="8192000"> </superblock>

Ok so this happened: Jul 3 13:16:24 saito kernel: [131695.910332] device-mapper: space map metadata: unable to allocate new metadata b lock Jul 3 13:16:24 saito kernel: [131695.910762] device-mapper: thin: 253:4: metadata operation 'dm_thin_remove_range' failed: error = -28 Jul 3 13:16:24...

So after setting up the console (its super annoying there is no kernel debug package - please make that) Jun 26 07:09:37 xxxx.bytefoundry.com.au [121030.583459] mce: [Hardware Error]: TSC 125df25667e3c Jun 26 07:09:37 xxxx.bytefoundry.com.au [121030.583490] mce: [Hardware Error]: PROCESSOR...