Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1535393

Summary: [PPC] Failed to run VM, unsupported configuration: setting ACPI S3 not supported.
Product: [oVirt] ovirt-engine Reporter: Israel Pinto <ipinto>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED CURRENTRELEASE QA Contact: Israel Pinto <ipinto>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.2.1CC: bugs, cshao, dguo, huzhao, jiaczhan, michal.skrivanek, qiyuan, weiwang, yaniwang, ycui, yzhao
Target Milestone: ovirt-4.2.1Keywords: AutomationBlocker, Regression
Target Release: ---Flags: rule-engine: ovirt-4.2?
ykaul: blocker?
ipinto: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+
Hardware: ppc64   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.1.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 11:58:51 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:
Attachments:
Description Flags
engine_logs none

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 1 Israel Pinto 2018-01-17 10:00:07 UTC 
Failing automation runs:
https://rhv-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/rhv-4.2-ge-runner-tier1/72/testReport/
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.