8:07 a.m.
Sure, they're attached. In "first attempt" the error seems to be:
2019-01-17 07:49:24,795-05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-29)
[680f82b3-7612-4d91-afdc-43937aa298a2] EVENT_ID:
FAILED_HOT_SET_MEMORY_NOT_DIVIDABLE(2,048), Failed to hot plug memory to VM HostedEngine.
Amount of added memory (4000MiB) is not dividable by 256MiB.
Followed by:
2019-01-17 07:49:24,814-05 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand]
(default task-29) [26f5f3ed] Validation of action 'UpdateRngDevice' failed for
user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING
2019-01-17 07:49:24,815-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default
task-29) [26f5f3ed] Updating RNG device of VM HostedEngine
(adf14389-1563-4b1a-9af6-4b40370a825b) failed. Old RNG device =
VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89',
vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio',
type='RNG', specParams='[source=urandom]', address='',
managed='true', plugged='true', readOnly='false',
deviceAlias='', customProperties='null', snapshotId='null',
logicalName='null', hostDevice='null'}. New RNG device =
VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89',
vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio',
type='RNG', specParams='[source=urandom]', address='',
managed='true', plugged='true', readOnly='false',
deviceAlias='', customProperties='null', snapshotId='null',
logicalName='null', hostDevice='null'}.
In "second attempt" I used values that are dividable by 256 MiB so that's no
longer present. Though same error:
2019-01-17 07:56:59,795-05 INFO
[org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default task-22) [7059a48f]
START, SetAmountOfMemoryVDSCommand(HostName =
ovirt-hv1.med.cornell.edu<http://ovirt-hv1.med.cornell.edu>,
Params:{hostId='cdd5ffda-95c7-4ffa-ae40-be66f1d15c30',
vmId='adf14389-1563-4b1a-9af6-4b40370a825b',
memoryDevice='VmDevice:{id='VmDeviceId:{deviceId='7f7d97cc-c273-4033-af53-bc9033ea3abe',
vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='memory',
type='MEMORY', specParams='[node=0, size=2048]', address='',
managed='true', plugged='true', readOnly='false',
deviceAlias='', customProperties='null', snapshotId='null',
logicalName='null', hostDevice='null'}',
minAllocatedMem='6144'}), log id: 50873daa
2019-01-17 07:56:59,855-05 INFO
[org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default task-22) [7059a48f]
FINISH, SetAmountOfMemoryVDSCommand, log id: 50873daa
2019-01-17 07:56:59,862-05 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-22)
[7059a48f] EVENT_ID: HOT_SET_MEMORY(2,039), Hotset memory: changed the amount of memory on
VM HostedEngine from 4096 to 4096
2019-01-17 07:56:59,881-05 WARN [org.ovirt.engine.core.bll.UpdateRngDeviceCommand]
(default task-22) [28fd4c82] Validation of action 'UpdateRngDevice' failed for
user admin@internal-authz. Reasons: ACTION_TYPE_FAILED_VM_IS_RUNNING
2019-01-17 07:56:59,882-05 ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] (default
task-22) [28fd4c82] Updating RNG device of VM HostedEngine
(adf14389-1563-4b1a-9af6-4b40370a825b) failed. Old RNG device =
VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89',
vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio',
type='RNG', specParams='[source=urandom]', address='',
managed='true', plugged='true', readOnly='false',
deviceAlias='', customProperties='null', snapshotId='null',
logicalName='null', hostDevice='null'}. New RNG device =
VmRngDevice:{id='VmDeviceId:{deviceId='6435b2b5-163c-4f0c-934e-7994da60dc89',
vmId='adf14389-1563-4b1a-9af6-4b40370a825b'}', device='virtio',
type='RNG', specParams='[source=urandom]', address='',
managed='true', plugged='true', readOnly='false',
deviceAlias='', customProperties='null', snapshotId='null',
logicalName='null', hostDevice='null'}.
This message repeats throughout engine.log:
2019-01-17 07:55:43,270-05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engineScheduled-Thread-89) [] EVENT_ID:
VM_MEMORY_UNDER_GUARANTEED_VALUE(148), VM HostedEngine on host
ovirt-hv1.med.cornell.edu<http://ovirt-hv1.med.cornell.edu> was guaranteed 8192 MB
but currently has 4224 MB
As you can see attached the host has plenty of memory.
Thank you Simone!
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug@med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
On Thu, Jan 17, 2019 at 5:09 AM Simone Tiraboschi
<stirabos@redhat.com<mailto:stirabos@redhat.com>> wrote:
On Wed, Jan 16, 2019 at 8:22 PM Douglas Duckworth
<dod2014@med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote:
Sorry for accidental send.
Anyway I try to increase physical memory however it won't go above 4096MB. The
hypervisor has 64GB.
Do I need to modify this value with Hosted Engine offline?
No, it's not required.
Can you please attach your engine.log for the relevant time frame?
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug@med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
On Wed, Jan 16, 2019 at 1:58 PM Douglas Duckworth
<dod2014@med.cornell.edu<mailto:dod2014@med.cornell.edu>> wrote:
Hello
I am trying to increase Hosted Engine physical memory above 4GB
Thanks,
Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit<https://scu.med.cornell.edu>
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: doug@med.cornell.edu<mailto:doug@med.cornell.edu>
O: 212-746-6305
F: 212-746-8690
_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to
users-leave@ovirt.org<mailto:users-leave@ovirt.org>
Privacy Statement:
https://www.ovirt.org/site/privacy-policy/<https://urldefense.proofpoi...
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/<https://ur...
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WGSXQVVPJJ2...
2167
days inactive
2167
days old
0 comments
1 participants
participants (1)
-
Douglas Duckworth