Bug 1529493
| Summary: | [Docs][RFE][VMM] Document Multiple queue NICs feature | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Daniele <dconsoli> |
| Component: | Documentation | Assignee: | Emma Heftman <eheftman> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Alona Kaplan <alkaplan> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.2.3 | CC: | alkaplan, aperotti, apinnick, danken, igreen, lbopf, lsurette, pkovar, srevivo |
| Target Milestone: | ovirt-4.2.7 | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | Flags: | eheftman:
needinfo-
lsvaty: testing_plan_complete- |
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | docs-accepted | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-12 12:11:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 821493, 1574771 | ||
| Bug Blocks: | 1541529 | ||
|
Description
Daniele
2017-12-28 11:31:34 UTC
*** Bug 1530032 has been marked as a duplicate of this bug. *** This request affects all currently-supported version. Let us fix it in a 4.2 Accepting into 4.2.4 (z1) program and assigning to Emma for review. Hi Dan
I'm documenting this feature and I have a few questions.
You wrote:
An administrator can define a new custom property called "queues" for vNIC profiles.
engine-config -s "CustomDeviceProperties={type=interface;prop={<other-nic-properties;>queues=[1-9][0-9]*}}"
Where <other-nic-properties;> is a semicolon-separated list of prexisting custom properties of nics.
A user can then set it to the number of queues he or she would like to allocate
to a vNIC using this profile, instead of the default single queue. For best
performance, use the number of vCPUs.
1. Please explain exactly what values they should enter here: [1-9][0-9]
In other words, i.e. is the first value the ID of the CPU and the second the number of queues for that vCPU?
2.
"Note that each queue consumes about 100KB
of host memory, so a non-default values only when the number of queues is a
true bottle neck, such as when a multicore VM is expected to communicate with
other VMs on the same host."
What did you mean by" a nonnon-default values only when the number of queues is a
true bottle neck, such as when a multicore VM is expected to communicate with
other VMs on the same host."
and what should the user do with this information. Can this knowledge help him to configure the custom property more accurately?
Can it help him to decide whether or not it is relvant to configure the custom property in the first place?
3. Do you expect someone to configure this property immediately after installing the system, i.e. whenever they install the virtio-net driver we should immediately tell them to configure this property?
or
Is this something that they should only tweak if they are experiencing performance issues?
If the latter is the case, what indication would they have that their performance issues could be mitigated by configuring this property?
Thanks!
Emma
This feature has now been replaced by a check box in the UI that automatically sets the value to 4. Dan, is still necessary to explain how to change the value manually? The updated documentation is available on the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/virtual_machine_management_guide/index#Virtual_Machine_Resource_Allocation_settings_explained |