+++ This bug was initially created as a clone of Bug #1101569 +++ Description of problem: Official support for Data Plane (was tech preview in RHEL7.0) Version-Release number of selected component (if applicable): RHEL7.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
FYI, a summary of the status of data-plane as being delivered with the RHEL7.1 package (rhev flavor): https://bugzilla.redhat.com/show_bug.cgi?id=1101569#c1
*** Bug 1181396 has been marked as a duplicate of this bug. ***
hai - any limitation from guest os support for either rhel or windows (need of guest driver?)
(In reply to Itamar Heim from comment #7) > hai - any limitation from guest os support for either rhel or windows (need > of guest driver?) No need for guest driver changes to enable dataplane, it's fully contained in QEMU. As a heads-up, the next logical step is to support virtio-{blk,scsi} multi-queue. This is already in RHEL6/7, not sure about virtio-win.
we would go with per-VM setting enabling the support, no pinning. not sure about making the number of threads configurable. Can we start with 1?
(In reply to Michal Skrivanek from comment #10) > we would go with per-VM setting enabling the support, no pinning. > not sure about making the number of threads configurable. Can we start with > 1? Yes, agree per VM setting to enable functionality. Let's start with 1 thread, but have an advanced option for customers to enable more threads.
advanced might be custom properties and a hook though when we introduce a new feature it's typically not much work to do it right at least at VDSM API level
Bugs found: 1. Migration bug: Migration failed libvirtError in migrateToURI3 (https://bugzilla.redhat.com/show_bug.cgi?id=1252099) 2. Failed to start VM if IO threads are bigger then 127: VM stuck in wait for launch after update vm IO Threads value (https://bugzilla.redhat.com/show_bug.cgi?id=1251899)
moving to on_qa, wait for storage and scale results.
There was nothing special to do from storage perspective but regression testing. Our regression is ongoing always and we saw nothing till now so looks like we are good
Verify with: RHEVM Version: 3.6.0-0.18.el6 vdsm: vdsm-4.17.8-1.el7ev libvirt: libvirt-1.2.17-5.el7
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0376.html