Bug 1535393 - [PPC] Failed to run VM, unsupported configuration: setting ACPI S3 not supported.
Summary: [PPC] Failed to run VM, unsupported configuration: setting ACPI S3 not suppor...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.2.1
Hardware: ppc64
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-4.2.1
: ---
Assignee: Michal Skrivanek
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-17 09:59 UTC by Israel Pinto
Modified: 2019-04-28 14:23 UTC (History)
11 users (show)

Fixed In Version: ovirt-engine-4.2.1.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-12 11:58:51 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2?
ykaul: blocker?
ipinto: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)
engine_logs (175.52 KB, application/x-xz)
2018-01-17 10:01 UTC, Israel Pinto
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 86577 0 master MERGED core: do not configure Power Management features on non-x86 VMs 2020-02-28 00:49:04 UTC

Description Israel Pinto 2018-01-17 09:59:18 UTC
Description of problem:
On PPC environment, failed to start VM with error:
unsupported configuration: setting ACPI S3 not supported


Version-Release number of selected component (if applicable):
Software Version:4.2.1.1-0.1.el7


How reproducible:
100 %

Steps to Reproduce:
1. Create VM (with disk, or with Nic and set boot from PXE)
2. Start VM


Actual results:
VM failed to run.

Additional info:
From engine log:
2018-01-17 11:35:43,833+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-8) [] EVENT_ID: VM_DOWN_ERROR(119), VM test is down with error. Exit message: unsupported configuration: setting ACPI S3 not supported.

Comment 2 Israel Pinto 2018-01-17 10:01:59 UTC
Created attachment 1382326 [details]
engine_logs

Comment 3 Yaniv Kaul 2018-02-10 10:49:54 UTC
Please fill in target milestone. Is it in 4.2.1?

Comment 4 Israel Pinto 2018-02-11 09:57:14 UTC
Verify with:
Software Version:4.2.1.6-0.1.el7
Host:
OS Version:RHEL - 7.5 - 3.el7
OS Description:Red Hat Enterprise Linux Server 7.5 Beta (Maipo)
Kernel Version:3.10.0 - 830.el7.ppc64le
KVM Version:2.10.0 - 20.el7
LIBVIRT Version:libvirt-3.9.0-7.el7
VDSM Version:vdsm-4.20.17-1.el7ev

Steps:
Start VM with os type "other os" or "Red Hat Enterprise Linux 7.x"
Results:
VM is up and running

Comment 5 Sandro Bonazzola 2018-02-12 11:58:51 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

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