Possible to limit IO for disk move or live migration

Discussion in 'Proxmox VE: Installation and configuration' started by mailinglists, Feb 21, 2019.

  1. mailinglists

    mailinglists Active Member

    Joined:
    Mar 14, 2012
    Messages:
    387
    Likes Received:
    34
    When I move a VM disk on ZFS i have high IO WAIT.
    Reasons aside, I want to reduce IO WAIT by reducing IO strain by disk moving operation.
    I think the same logic is used also when doing live migraton with local disks.

    Is there a way to specify disk bandwidth for such operations, or maybe IO priority?

    I guess in extreme cases I could use ionice on the already running process to reduce IO strain.
     
  2. wolfgang

    wolfgang Proxmox Staff Member
    Staff Member

    Joined:
    Oct 1, 2014
    Messages:
    4,763
    Likes Received:
    315
    Hi,

    see
    Code:
    man datacenter.cfg
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    mailinglists likes this.
  3. check-ict

    check-ict Member

    Joined:
    Apr 19, 2011
    Messages:
    93
    Likes Received:
    1
    The bwlimit: function in datacenter.cfg doesn't work. You can only copy disks with rsync bwlimit when the VM is stopped.

    See other forum posts, moving disks with limits in datacenter.cfg doesn't work. It will just use the full MBps possible.
     
  4. mailinglists

    mailinglists Active Member

    Joined:
    Mar 14, 2012
    Messages:
    387
    Likes Received:
    34
    @check-ict I will test and report back. Somehow i doubt such feature would not work.

    @wolfgang can we set limit specific for single storage in storage.cfg, or must we use global config which will apply to all our storages?
    Also is the unit MiB/s MebiBytes per second, right?
     
    #4 mailinglists, Feb 28, 2019
    Last edited: Feb 28, 2019
  5. wolfgang

    wolfgang Proxmox Staff Member
    Staff Member

    Joined:
    Oct 1, 2014
    Messages:
    4,763
    Likes Received:
    315
    He is correct it is not implemented.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. mailinglists

    mailinglists Active Member

    Joined:
    Mar 14, 2012
    Messages:
    387
    Likes Received:
    34
    Em...? What gives?
    Any links to bug reports or feature requests?
    Why would manual already have not yet implemented or redacted options?
     
  7. wolfgang

    wolfgang Proxmox Staff Member
    Staff Member

    Joined:
    Oct 1, 2014
    Messages:
    4,763
    Likes Received:
    315
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. mailinglists

    mailinglists Active Member

    Joined:
    Mar 14, 2012
    Messages:
    387
    Likes Received:
    34
    I see. :-(
    @wolfgang do you think adding ionice before qemu migrate or whathever commands are used for disk moving, cloning, etc would be an option for ProxMox developers? We can probably get away with just a static value, since these commands should never interfere with running VMs, but they do. We could also limit bw with cstream or mbuffer and such.

    Optionally, we could have bw as well as ionice options on those commands as parameters.
     
  1. 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.
    Dismiss Notice