If set the maximum migration bandwidth, the "virsh domjobabort" command doesn't work correctly

Solution Unverified - Updated -

Issue

  • If set the maximum migration bandwidth by using "virsh migrate-setspeed", the "virsh domjobabort" command cannot abort the following jobs:

      - virsh dump
      - virsh save
      - virsh managedsave
    

Environment

  • Red Hat Enterprise Linux 6.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.