Bug 1678200 - Q35: Cloned VM with Q35 chipset, failed to run (PCI controller model is null instead of pcie-root).
Summary: Q35: Cloned VM with Q35 chipset, failed to run (PCI controller model is null ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.3.2
: ---
Assignee: Shmuel Melamud
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-18 09:57 UTC by Nisim Simsolo
Modified: 2019-03-26 07:20 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-03-26 07:20:49 UTC
oVirt Team: Virt
Embargoed:
aoconnor: ovirt-4.3+


Attachments (Terms of Use)
vdsm.log.xz (317.65 KB, application/x-xz)
2019-02-18 10:00 UTC, Nisim Simsolo
no flags Details
engine.log.xz (92.28 KB, application/x-xz)
2019-02-18 10:00 UTC, Nisim Simsolo
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 98196 0 master MERGED core: Copy spec params of PCI controllers 2020-06-17 07:20:04 UTC

Description Nisim Simsolo 2019-02-18 09:57:43 UTC
Description of problem:
Trying to run clone of VM with Q35 chipset, failed with the next vdsm.log ERROR:
 2019-02-18 11:50:01,444+0200 ERROR (vm/e86855af) [virt.vm] (vmId='e86855af-8a46-4f6a-bd4d-b4000d7dbdba') The vm start process failed (vm:937)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 866, in _startUnderlyingVm
    self._run()
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2852, in _run
    dom = self._connection.defineXML(self._domain.xml)
  File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94, in wrapper
    return func(inst, *args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3733, in defineXML
    if ret is None:raise libvirtError('virDomainDefineXML() failed', conn=self)
libvirtError: XML error: The PCI controller with index='0' must be model='pcie-root' for this machine type, but model='(null)' was found instead

Issue is relevant only for clones of VM with Q35 chipset with UEFI BIOS/secure boot.

Version-Release number of selected component (if applicable):
ovirt-engine-4.3.0.5-0.0.master.20190207124642.git415c7e8.el7.noarch
vdsm-4.30.8-58.git60c5a6d.el7.x86_64
qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64
libvirt-client-4.5.0-10.el7_6.4.x86_64

How reproducible:
100%

Steps to Reproduce:
1. create clone of VM with Q35 chipset and UEFI BIOS.
2. Try to run cloned VM.
3.

Actual results:
Cloned VM failed to start.

Expected results:
Cloned VM should run.

Additional info:
vdsm.log and engine.log attached.

Comment 1 Nisim Simsolo 2019-02-18 10:00:13 UTC
Created attachment 1535876 [details]
vdsm.log.xz

Comment 2 Nisim Simsolo 2019-02-18 10:00:30 UTC
Created attachment 1535877 [details]
engine.log.xz

Comment 3 Nisim Simsolo 2019-03-11 16:10:07 UTC
Verified upstream: 
ovirt-engine-4.3.2.1-0.0.master.20190310172919.git0b3fbad.el7
vdsm-4.40.0-59.git5533158.el7.x86_64
libvirt-client-4.5.0-10.el7_6.4.x86_64
qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64

Comment 4 Sandro Bonazzola 2019-03-13 15:45:40 UTC
Michal I see this has been already verified in 4.3.2, can you please check current target milestone and status of the bug?

Comment 5 Nisim Simsolo 2019-03-19 12:36:31 UTC
Verified:
ovirt-engine-4.4.0-0.0.master.20190318180517.git576124b.el7
vdsm-4.40.0-96.gite291014.el7.x86_64
libvirt-client-4.5.0-10.el7_6.6.x86_64
qemu-kvm-ev-2.12.0-18.el7_6.3.1.x86_64

Comment 6 Sandro Bonazzola 2019-03-26 07:20:49 UTC
This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.2 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.


Note You need to log in before you can comment on or make changes to this bug.