Recent content by Humbug

  1. QEMU 2.5 - Setting L2 cache size drive option

    Hi MikeQ, thanks a lot for sharing this workaround!
  2. [SOLVED] NMIs on VE 5.1-42 and 4.15.18-4-pve

    I was able to fix the problem. - changed clocksource for VMs (clocksource=acpi_pm, was kvm_clock previously) - on the virtualization host /etc/sysctl.conf # 0 avoids swapping processes out of physical memory for as long as possible. vm.swappiness = 0 # lessen the IO blocking effect that...
  3. [SOLVED] NMIs on VE 5.1-42 and 4.15.18-4-pve

    Hallo nochmal, ich habe das Problem inzwischen lösen können. Die letzten beiden Änderungen, die vielleicht den Ausschlag gegeben haben könnte waren: - Dateisystemüberwachung auf dem Virtualisierungsserver erhöht (fs.inotify.max_user_instances=256) - Zeitgeber auf den VMs geändert...
  4. Advanced disk paramters

    Lucio, i added your request for a qcow2 cluster size parameter to the ticket https://bugzilla.proxmox.com/show_bug.cgi?id=1989 What application is your picture taken from?
  5. KVM guests freeze (hung tasks) during backup/restore/migrate

    I filed a feature request for qcow2 l2-cache-size parameter here: https://bugzilla.proxmox.com/show_bug.cgi?id=1989
  6. QEMU 2.5 - Setting L2 cache size drive option

    Thanks! I filed a feature request for qcow2 l2-cache-size parameter here: https://bugzilla.proxmox.com/show_bug.cgi?id=1989
  7. Advanced disk paramters

    I filed a feature request for qcow2 l2-cache-size parameter here: https://bugzilla.proxmox.com/show_bug.cgi?id=1989
  8. KVM guests freeze (hung tasks) during backup/restore/migrate

    There is a qemu parameter to set the size of qcow2 L2 cache properly (default is 8 GB disk size max) which has a dramatic impact on performance, but it is currently unusable with Proxmox PVE...
  9. QEMU 2.5 - Setting L2 cache size drive option

    Is there any workaround? E.g. can i create the qcow2 image manually, so i don't need to add the parameter later? And is there any plan to integrate this parameter as a Proxmox PVE feature in future?
  10. freeze during and after blackup

    Looks like you're currently running deadline (the one in the brackets is active). Yes, give it a try.
  11. freeze during and after blackup

    I just read that ionice generally does not work on NFS: https://forum.proxmox.com/threads/about-of-ionice-in-vzdump.16485/#post-84955 Maybe you can use another location instead? As far as i know all other availble io schedulers do not honour ionice parameters, so you would have to use CFQ...
  12. Proxmox Host and Clients Randomly Freeze. Have to restart the system

    Were you able to fix the problem? Did changing /proc/sys/fs/inotify/max_user_watches help?
  13. freeze during and after blackup

    I'm not an expert but i have similar problems (not involving NFS though). What you could try as a workaround is a) install the CFQ i/o scheduler on the host and then b) use vzdump in combination with ionice parameter in the shell. See man vzdump.
  14. Meltdown and Spectre Linux Kernel fixes

    I installed latest BIOS and intel-microcode package. Can i still use "noibrs noibpb" kernel parameters to disable these functions? Or do i have to downgrade BIOS again?
  15. Problems running Docker in VM (segfaults/gpf's)

    Were you able to solve the problem? I also see 'cpu soft lockup' in a KVM VM which contains a docker instance. Maybe a similar problem?

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!