Bug 1149523 - Allow updating disk IO QoS in run time.
Summary: Allow updating disk IO QoS in run time.
Keywords:
Status: CLOSED DUPLICATE of bug 1201482
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.5.4
Assignee: Roy Golan
QA Contact: Aharon Canan
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-05 20:04 UTC by Doron Fediuck
Modified: 2022-05-16 06:38 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-17 08:11:23 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46029 0 None None None 2022-05-16 06:38:39 UTC

Description Doron Fediuck 2014-10-05 20:04:36 UTC 
Description of problem:
Currently IO QoS for a disk is set only when starting a VM.
We should allow updating it when the VM is already running.
Comment 1 Roy Golan 2014-10-26 10:12:10 UTC 
(In reply to Doron Fediuck from comment #0)
> Description of problem:
> Currently IO QoS for a disk is set only when starting a VM.
> We should allow updating it when the VM is already running.

would changing at runtime mean something? only for next configuration?
Comment 2 Doron Fediuck 2014-10-28 11:51:04 UTC 
(In reply to Roy Golan from comment #1)
> (In reply to Doron Fediuck from comment #0)
> > Description of problem:
> > Currently IO QoS for a disk is set only when starting a VM.
> > We should allow updating it when the VM is already running.
> 
> would changing at runtime mean something? only for next configuration?

Yes- it should change the IO limitations we impose on a disk.
Comment 3 Roy Golan 2014-10-28 11:51:41 UTC 
Martin I guess we need you VDSM patches and discuss the engine side
Comment 4 Eyal Edri 2015-02-25 08:40:20 UTC 
3.5.1 is already full with bugs (over 80), and since none of these bugs were added as urgent for 3.5.1 release in the tracker bug, moving to 3.5.2
Comment 5 Doron Fediuck 2015-05-17 08:11:23 UTC 

*** This bug has been marked as a duplicate of bug 1201482 ***
Note You need to log in before you can comment on or make changes to this bug.