Description of problem:

After the creation of a template with VirtIO-SCSI Multi Queues set to Custom and any number of queues, in our case 3, and after the creation of a VM pool from that template with the number of queues set to 5, then, when extending the VM pool size, the created VMs are created with VirtIO-SCSI Multi Queues set to Disabled instead of Custom.

Version-Release number of selected component (if applicable):
    - Engine instance with RHV 4.5.0-8 (ovirt-engine-4.5.0.5-0.7.el8ev) and RHEL 8.6 installed.
    - 3 hosts with RHV 4.5.0-8 and RHEL 8.6 and with vdsm-4.50.0.13-1.el8ev.

How reproducible:
100%

Steps to Reproduce:
1. Create a 4.7 data center and a 4.7 cluster.
2. Install the hosts and create a new NFS storage domain.
3. Create an RHEL VM with VirtIO-SCSI Multi Queues set to Custom and 3 queues.
4. Create a template from the VM.
5. Create a VM pool from the latest version of the template with size: 1,  VirtIO-SCSI Multi Queues set to Custom, and 5 queues.
6. Edit the VM pool and change the field "Increase number of VMs in pool by" to 2.
7. Check for every created VM that VirtIO-SCSI Multi Queues set to Custom, and the number of queues is set to 5.

Actual results:
1. The 4.7 data center and the 4.7 cluster were created.
2. The hosts were installed and the NFS storage domain was created.
3. The VM was created with VirtIO-SCSI Multi Queues set to Custom and 3 queues.
4. The template was created.
5. The VM pool and 1 VM were created.
6. 2 new VMs were created.
7. The newly created VMs are set with VirtIO-SCSI Multi Queues set to Disabled.

Expected results:
Steps 1-6 results are as expected. 
In step 7, the newly created VMs (After extending the pool), should have VirtIO-SCSI Multi Queues set to Custom, and the number of queues should be set to 5.