Bug 1649847
| Summary: | OVMF: VM Custom emulated machine value is incorrect when selecting Q35 chipset with UEFI BIOS. | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Nisim Simsolo <nsimsolo> | ||||||||||||||
| Component: | BLL.Virt | Assignee: | Shmuel Melamud <smelamud> | ||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | meital avital <mavital> | ||||||||||||||
| Severity: | low | Docs Contact: | |||||||||||||||
| Priority: | medium | ||||||||||||||||
| Version: | 4.3.0 | CC: | bugs, guillaume.pavese, nsimsolo, rbarry, srosenbe | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | Unspecified | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2020-03-17 12:49:46 UTC | Type: | Bug | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Embargoed: | |||||||||||||||||
| Bug Depends On: | |||||||||||||||||
| Bug Blocks: | 1527889 | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
Created attachment 1505720 [details]
engine.log
Created attachment 1505721 [details]
vdsm.log
Created attachment 1505722 [details]
edit VM screenshot
I do not understand how/where did you set Custom emulated machine? oh, or you mean just the message in the box. that's really just cosmetic Created attachment 1505965 [details]
set emulated machine, screenshot
Edit VM -> system -> expand advanced parameters, under BIOS type dropbox there is a custom emulated machine dropbox. Screenshot example attached. (In reply to Michal Skrivanek from comment #5) > oh, or you mean just the message in the box. > that's really just cosmetic It's not that cosmetic, because the default in my case is "pc-i440fx-rhel" and when selecting Q35 with UEFI BIOS and leaving this field with pc-i440fx, the VM failed to run with libvirtError: unsupported configuration: bus must be 0 for ide controller. Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both Still reproducible? sort of... Using rhvm-4.3.3.7-0.1.el7: - Now it's possible to run new VM with Q35 chipset with UEFI BIOS. - but run once VM with PXE or CD-ROM failed with the next engine.log: 2019-05-15 13:52:03,840+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-0) [] EVENT_ID: VM_DOWN_ERROR(119), VM new is down with error. Exit message: XML error: The P CI controller with index='0' must be model='pci-root' for this machine type, but model='pcie-root' was found instead. engine.log attached. Should I report a new bug on the issue? Created attachment 1568954 [details]
engine.log, see 2019-05-15 13:54:47,786+03 ERROR
Same bug works, since it's still a problem with the properties Still relevant? Created attachment 1663571 [details]
Q 35 with bios emulation set to Q35
As per the snapshot, the VM named VMLinux was set to "Q35 chipset with UEFI Bios" and the emulation was set automatically to "Cluster default(pc-q35-rhel7.6.0)". Please not that the emulation drop down is disabled so that the user cannot change it. As per the left side of the screenshot, after saving the setting, the VMLinux VM runs fine. The VM edit was reopened to exhibit the settings.
Please retest this issue with the current master branch accordingly.
(In reply to Steven Rosenberg from comment #15) > Created attachment 1663571 [details] > Q 35 with bios emulation set to Q35 > > As per the snapshot, the VM named VMLinux was set to "Q35 chipset with UEFI > Bios" and the emulation was set automatically to "Cluster > default(pc-q35-rhel7.6.0)". Please not that the emulation drop down is > disabled so that the user cannot change it. As per the left side of the > screenshot, after saving the setting, the VMLinux VM runs fine. The VM edit > was reopened to exhibit the settings. > > Please retest this issue with the current master branch accordingly. (In reply to Steven Rosenberg from comment #16) > (In reply to Steven Rosenberg from comment #15) > > Created attachment 1663571 [details] > > Q 35 with bios emulation set to Q35 > > > > As per the snapshot, the VM named VMLinux was set to "Q35 chipset with UEFI > > Bios" and the emulation was set automatically to "Cluster > > default(pc-q35-rhel7.6.0)". Please not that the emulation drop down is > > disabled so that the user cannot change it. As per the left side of the > > screenshot, after saving the setting, the VMLinux VM runs fine. The VM edit > > was reopened to exhibit the settings. > > > > Please retest this issue with the current master branch accordingly. Clarification, please note: the emulation machine type is grey, but not disabled so the user can change it. The Emulation Machine Type's default was previously changed to the Q35 default which should resolve some of the related scenarios. Being that the setting of the Bios Type and the Custom Emulation Machine Type are advanced features, it is the responsibility of the user to set the appropriate settings accordingly. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of problem: When selecting BIOS type = Q35 chipset with UEFI BIOS, the Custom emulated machine remains cluster default value (in my case pc-i440fx). Trying to run such VM failed with the next vdsm ERROR: 2018-11-14 17:41:03,402+0200 ERROR (vm/07c11848) [virt.vm] (vmId='07c11848-4854-49fa-b417-c081f079968e') The vm start process failed (vm:934) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 863, in _startUnderlyingVm self._run() . . . libvirtError: unsupported configuration: bus must be 0 for ide controller Although in the future it will be able to allow setting q35 on the whole cluster, the custom emulated machine should be changed automatically to Q35 in case the cluster is not set with Q35. Version-Release number of selected component (if applicable): ovirt-engine-4.3.0-0.0.master.20181101091940.git61310aa.el7 libvirt-client-4.5.0-10.el7.x86_64 vdsm-4.30.1-52.git5426c0c.el7.x86_64 qemu-kvm-ev-2.10.0-21.el7_5.7.1.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create new VM, undde edit VM -> system -> advanced parameters, select BIOS type = "Q35 chipset with UEFI BIOS". don't change custom emulated machine value. 2. Run VM 3. Actual results: VM failed to run. Expected results: Custom emulated machine type should be changed to Q35 automatically when selecting Q35 with UEFI BIOS. Additional info: edit VM Screenshot, engine.log and vdsm.log attached.