Description of problem:
VM creation via Instancetype less performant than via Template.

Version-Release number of selected component (if applicable):
4.14.0

How reproducible:
100%

Steps to Reproduce (separately):
1. Create N (running: false) VMs using Template method
2. Create N (running: false) VMs using Instancetype method

Actual results:
Instancetype takes significantly longer to create N VM resources.

Expected results:
Instancetype method performs similarly to Template method

Additional info:
VM start is not required to test.
Increasing the kubevirt API rate limits significantly improves performance, with tuningProfile: highBurst being the most performant.

VM resource count query from attachment:

(count(kubevirt_vm_starting_status_last_transition_timestamp_seconds != 0) or vector(0)) +
(count(kubevirt_vm_running_status_last_transition_timestamp_seconds != 0) or vector(0)) +
(count(kubevirt_vm_migrating_status_last_transition_timestamp_seconds != 0) or vector(0)) +
(count(kubevirt_vm_non_running_status_last_transition_timestamp_seconds != 0) or vector(0)) +
(count(kubevirt_vm_error_status_last_transition_timestamp_seconds != 0) or vector(0))

If running: true, use below query alongside above query.
sum(kubevirt_vmi_phase_count

)