Search results

  1. D

    VM network freeze

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

    VM network freeze

    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
  3. D

    Grub Rescue ZFS Errors on Proxmox 5.3

    Did you find a solution to this?
  4. D

    Windows 2016 crashes whole pve 5.2 system

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

    Windows 2016 crashes whole pve 5.2 system

    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 ?
  6. D

    Windows 2016 crashes whole pve 5.2 system

    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
  7. D

    Windows 2016 crashes whole pve 5.2 system

    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.
  8. D

    latest update broke the whole system. need help!

    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" >...
  9. D

    latest update broke the whole system. need help!

    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.
  10. D

    Virtio Driver Crashing High Load

    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...
  11. D

    Virtual Machine Windows2016 lost network connection

    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
  12. D

    Virtual Machine Windows2016 lost network connection

    anyone else had this? i have this with netkvm nic
  13. D

    Recovering from lvm thin metadata exhaustion

    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>
  14. D

    Recovering from lvm thin metadata exhaustion

    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...
  15. D

    Windows 2016 crashes whole pve 5.2 system

    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...
  16. D

    Windows 2016 crashes whole pve 5.2 system

    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...
  17. D

    Windows 2016 crashes whole pve 5.2 system

    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?
  18. D

    Windows 2016 crashes whole pve 5.2 system

    excellent tip and much appreciated. that will be my next adjustment if this current configuration doesnt last longer than 48 hours
  19. D

    Windows 2016 crashes whole pve 5.2 system

    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...
  20. D

    Windows 2016 crashes whole pve 5.2 system

    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...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!