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
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
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
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>
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...
I suspect that 'fsgsbase' cpuflag is really needed.
Redhat almost says as much here https://bugzilla.redhat.com/show_bug.cgi?id=1346153
I suspect that presenting it will get windows going, but sooner or later its called and everything crashes.
these onapp.com people explicitly say its needed...
the system lasted nearly a week before crashing again. which is obviously a huge improvement.
ive set the cpu now to 'host'
is it possible to get the debug package for the kernel so that the vmcore can be analyzed?
Installation completed without this setting, the crash seems to happen quite infrequently (hours to days) with it on or off.
Does reinstallation with the setting on impact the install?
I would like to look at the vmcore but there doesnt seem to be a debug package? this would be extremely...
Im running a single Windows 2016 server essentials VM, but every few hours (max 2 days) the whole system crashes and reboots.
I have captured kernel dumps, but there doesnt seem to be a debug package to assist in analyzing.
pveversion --verbose
proxmox-ve: 5.2-2 (running kernel...
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.