The startup time for virtual machines with large memory is slow on IBM POWER8 hosts. Therefore the default maximum memory was decreased to 1TB so the delay in the start up time was not noticeable. To change the default value, use the engine configuration tool with the VM64BitMaxMemorySizeInMB key.
Created attachment 1073913[details]
Logs
Description of problem:
I tested memory hot plug on PPC with VM64BitMaxMemorySizeInMB:
512GB,510GB and 256BG
Setup:
Results:
1. With 512GB and 510GB: The VM failed to run:
"VM golden_env_mixed_virtio_0 is down with error. Exit message: Lost connection with qemu process."
2. With 256GB: test PASSSED
Attached engine, vdsm, qeum logs
Version-Release number of selected component (if applicable):
RHEVM 3.6.0.12 :
Red Hat Enterprise Virtualization Manager Version: 3.6.0-0.15.master.el6
VDSM: vdsm-4.17.6-1.el7ev
Libvirt: libvirt-1.2.17-8.el7
How reproducible:
All the time
Verify with rhevm on ppc env:
RHEVM Version: 3.6.0-0.18.el6
vdsm version: vdsm-4.17.8-1.el7ev
libvirt version: libvirt-1.2.17-12.el7
Scenario:
1. Create VM with 1G
2. hot plug memory 1G/2G/256M
3. Check in VM memory status with free
4. Migrate VM
All cases pass.
Created attachment 1073913 [details] Logs Description of problem: I tested memory hot plug on PPC with VM64BitMaxMemorySizeInMB: 512GB,510GB and 256BG Setup: Results: 1. With 512GB and 510GB: The VM failed to run: "VM golden_env_mixed_virtio_0 is down with error. Exit message: Lost connection with qemu process." 2. With 256GB: test PASSSED Attached engine, vdsm, qeum logs Version-Release number of selected component (if applicable): RHEVM 3.6.0.12 : Red Hat Enterprise Virtualization Manager Version: 3.6.0-0.15.master.el6 VDSM: vdsm-4.17.6-1.el7ev Libvirt: libvirt-1.2.17-8.el7 How reproducible: All the time