Description of problem:
If I run vm under PPC cluster, with memory size not multiplier of 256(1000MB) I receive qemu error under engine log "2015-09-08 13:08:06,147 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-36)  Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM test is down with error. Exit message: internal error: early end of file from monitor: possible problem:
2015-09-08T10:07:41.489898Z qemu-kvm: Can't support memory configuration where RAM size 0x3e800000 or maxmem size 0x3e800000 isn't aligned to 256 MB."
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create vm with 1000MB on ppc hosts
2. Run vm
Create action success, but vm failed to run
If it qemu limitation, I want to validate memory size on create(update) action and give to user message, that under PPC cluster he can only have vms with memory size equal to multiplier of 256
I do not sure what a reason why we have such limitation from qemu for ppc, maybe it worth to check it will qemu dev team
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Verified with rhevm- 126.96.36.199-0.1.el7ev with hosts:
kernel version: 3.10.0 - 327.30.1.el7.ppc64le
IBM Power System S824
CPU Model Name:
POWER8E (raw), altivec supported
Cluster set to IBM POWER8 cluster.
Verified that trying to create/edit vm with 10000MB failed and the proper message appear when hovering above the memory field.
When editing/creating with a value which is multiplier of 256 action succeeds.