Hide Forgot
Description of problem: When importing RHV OVA file with 4 virtual CPUs, 2 virtual sockets and 2 threads per core (2:1:2), the imported VM CPU topology is 4 virtual CPUs 4 virtual sockets, 1 core per virtual socket and 1 threads per core (4:1:1). In the exported OVA file, the parameters are correct: <rasd:Caption>4 virtual cpu</rasd:Caption> <rasd:Description>Number of virtual CPU</rasd:Description><rasd:InstanceId>1</rasd:InstanceId> <rasd:ResourceType>3</rasd:ResourceType><rasd:num_of_sockets>2</rasd:num_of_sockets><rasd:cpu_per_socket>1</rasd:cpu_per_socket><rasd:threads_per_cpu>2</rasd:threads_per_cpu><rasd:max_num_of_vcpus>32</rasd:max_num_of_vcpus> Version-Release number of selected component (if applicable): rhvm-4.2.2.4-0.1.el7 vdsm-4.20.22-1.el7ev.x86_64 libvirt-client-3.9.0-14.el7.x86_64 qemu-kvm-rhev-2.10.0-19.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Export VM as OVA with CPU topology of 2:1:2 2. Import this VM 3. Observe CPU topology Actual results: Imported VM CPU topology is 4:1:1 instead of 2:1:2 Expected results: CPU topology should be 2:1:2 Additional info: ovirt-query-ova-ansible.log, ovirt-import-ova-ansibl.log, vdsm.log and engine.log (import started at 2018-03-20 17:02:57,416+02) attached
Created attachment 1410617 [details] vdsm.log
Created attachment 1410620 [details] engine.log
Created attachment 1410632 [details] ovirt-export-ova-ansible log
Created attachment 1410633 [details] ovirt-export-ova-validate-ansible log
Created attachment 1410634 [details] ovirt-query-ova-ansible log
Created attachment 1410635 [details] ovirt-import-ova-ansible log
OvfReader::readCpuItem() vmBase.setCpuPerSocket(Integer.parseInt(selectSingleNode(node, "rasd:cpu_per_socket", _xmlNS).innerText)); vs vmBase.setThreadsPerCpu(parseNodeInteger(node, "rasd:threads_per_cpu", 1)) ?
Verified on: ovirt-engine-4.2.4.2-0.1.el7_3.noarch vdsm-4.20.30-1.el7ev.x86_64 Steps of verfication: 1. Export VM as OVA with CPU topology of 2:1:2 2. Import this VM 3. Observe CPU topology Actual results: Imported VM CPU topology is 2:1:2 as expected.
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.