Bug 1595931

Summary: RFE: qemu: support for scsi-disk/ide rotation_rate
Product: [Community] Virtualization Tools Reporter: Mai Ling <mailinglists35>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: berrange, crobinso, eskultet, gscrivan, ko, libvirt-maint, nikolay
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-05 10:21:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mai Ling 2018-06-27 20:14:39 UTC
#1498042 has added support for telling the guest the rotation rate of drives.
I'd like to be able to use this with virt-xml.

[root@gw2 vmstore]# virt-xml gwwin --edit --disk rotation_rate=0                                                                                               ERROR    Unknown options ['rotation_rate']

Comment 1 Cole Robinson 2018-06-27 21:41:54 UTC
This needs to be exposed in libvirt first, so reassigning.

This is in qemu 2.11, patch posting was: https://lists.gnu.org/archive/html/qemu-devel/2017-10/msg00697.html

Comment 2 Kevin Olbrich 2019-05-01 22:16:03 UTC
I would really like to see this implemented at the XML layer.
As far as I understand, VMs also get entropy from disks if they are rotating but don't when they are solid state drives.
Windows guests also behave differently if they detect SSD media (virtio-scsi with discard solves this mostly).

There seems to be a workaround (not tested):
https://serverfault.com/a/924717/453453

Comment 3 Erik Skultety 2020-10-05 10:21:08 UTC
Since this is now assigned to the libvirt component, there already is a product BZ tracking this feature, hence I'm closing this as a duplicate.

*** This bug has been marked as a duplicate of bug 1498955 ***