Recent content by brandon_welsch

  1. B

    Proxmox restore backup take too long time and with kernel error

    Hello, It's impossible to restore a VM, it takes too much time, it never ends. And errors appear in the kernel logs. it's been running for about 2 hours for a VM with a 200GB disk containing 50GB of data. I think this problem is related to...
  2. B

    kworker 99% IO

    The network throughput is good (1Gbps dedicated network yes). The transfer of the disk is done quite quickly on the destination machine. But is seems blocked on the destination machine with dd of=/dev/pve/vm-300-~k-0 conv=sparse bs=64k running process. It doesn't seem to me that bandwidth is...
  3. B

    Purchasing Proxmox

    Hello no, on the price page, it's not per CPU core but per CPU socket. So if you have 16 cores but they are on a single CPU socket, there is no need to take an option. If the 16 cores are spread over 2 sockets, you have to take an option in addition. To check your number of CPU socket. cat...
  4. B

    kworker 99% IO

    I don't understand where the trouble is. I've been retrying to find the trouble for hours, but I still haven't figured out why it's doing this.
  5. B

    kworker 99% IO

    For me, I used 2x1 TB SSD (RAID 1). The model is Crucial_CT1050MX300SSD1. iotop result: Proxmox log: 2020-04-05 14:10:01 use dedicated network address for sending migration traffic (...) 2020-04-05 14:10:01 starting migration of VM 300 to node 'dedicated' (...) 2020-04-05 14:10:01 found...
  6. B

    kworker 99% IO

    I have set the bandwidth limit to 25MB/s, but I have the same problem. The migration of my 20 GB VM never ends :'(.