subject:"\[ovirt\-users\] Re\: Cannot Increase Hosted Engine VM Memory"

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2020-02-16 Thread Serhiy Morhun

Hi, Can you explain your workaround a little more?
I cannot take a snapshot through UI. Get a message this VM is not managed
by the engine.
Also, do you edit the properties in Web UI? Every time I do that my "Memory
Size" always saves the old value.
And what do you mean by "cold reboot"? Is it "reboot" from hosted engine
session or "hosted-engine --vm-shutdown" followed by " hosted-engine
--vm-start" from node session?

Thank you. I would like to solve this issue. Just upgraded to 4.3.8 hoping
it was fixed but no luck.



On Thu, Dec 12, 2019 at 2:44 AM Michaël Couren  wrote:

>
>
> >
> > On Wed, 11 Dec 2019 at 09:36, Serhiy Morhun  >
> > wrote:
> >
> >> Hello, did anyone find a resolution for this issue? I'm having exactly
> the
> >> same problem:
>
> Hi, same issue for us, the solution was :
> Make a snappshot
> Edit the properties, putting 32768 MB for "Mem", 131072 MB for "Max" and
> 32768 MB for "Guaranteed"
> Then reboot the server (cold reboot)
>
> --
> Cordialement / Best regards, Michaël Couren,
> ABES, Montpellier, France.
>

-- 



*---***


*THE INFORMATION CONTAINED IN THIS MESSAGE (E-MAIL AND ANY ATTACHMENTS) IS 
INTENDED ONLY FOR THE INDIVIDUAL AND CONFIDENTIAL USE OF THE DESIGNATED 
RECIPIENT(S).*

If any reader of this message is not an intended recipient 
or any agent responsible for delivering it to an intended recipient, you 
are hereby notified that you have received this document in error, and that 
any review, dissemination, distribution, copying or other use of this 
message is prohibited.  If you have received this message in error, please 
notify us immediately by reply e-mail message or by telephone and delete 
the original message from your e-mail system and/or computer database.  
Thank you.


*---*


**NOTICE**:

*You are advised that e-mail correspondence and attachments 
between the public and the Ridgewood Board of Education are obtainable by 
any person who files a request under the NJ Open Public Records Act (OPRA) 
unless it is subject to a specific OPRA exception.  You should have no 
expectation that the content of e-mails sent to or from school district 
e-mail addresses, or between the public and school district officials and 
employees, will remain private.*


*---*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2VLAZCWVUAHSLEUWSAEVXDO5VJSO7Z5T/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-12-11 Thread Michaël Couren



> 
> On Wed, 11 Dec 2019 at 09:36, Serhiy Morhun 
> wrote:
> 
>> Hello, did anyone find a resolution for this issue? I'm having exactly the
>> same problem:

Hi, same issue for us, the solution was :
Make a snappshot
Edit the properties, putting 32768 MB for "Mem", 131072 MB for "Max" and 32768 
MB for "Guaranteed"
Then reboot the server (cold reboot)

-- 
Cordialement / Best regards, Michaël Couren,
ABES, Montpellier, France.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/S33OGCAO6KOSLFCVIKX5MNQ3M2UC3ZQ5/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-12-11 Thread Andrej Krejcir

Hi,

here is the bugzilla for this problem:
https://bugzilla.redhat.com/show_bug.cgi?id=1523835

There is no simple workaround, but I'm working on fixing it.


Best Regards,
Andrej


On Wed, 11 Dec 2019 at 09:36, Serhiy Morhun 
wrote:

> Hello, did anyone find a resolution for this issue? I'm having exactly the
> same problem:
>
> Hosted Engine VM is running with 5344MB of RAM, when trying to increase to
> 8192 it would not accept the change because the difference is not divisible
> by 256.
> When trying to increase to 8160 the change is accepted but log shows
> "Hotset memory: changed the amount of memory on VM HostedEngine from 5344
> to 5344" at the same time amount of guaranteed memory does increase to 8160
> which, in turn, starts generating error messages that VM does not have all
> the guaranteed RAM.
>
> Serhiy Morhun
>
>
>
>
>
>
> *---*
>
> *THE INFORMATION CONTAINED IN THIS MESSAGE (E-MAIL AND ANY ATTACHMENTS) IS
> INTENDED ONLY FOR THE INDIVIDUAL AND CONFIDENTIAL USE OF THE DESIGNATED
> RECIPIENT(S).*
>
> If any reader of this message is not an intended recipient or any agent
> responsible for delivering it to an intended recipient, you are hereby
> notified that you have received this document in error, and that any
> review, dissemination, distribution, copying or other use of this message
> is prohibited.  If you have received this message in error, please notify
> us immediately by reply e-mail message or by telephone and delete the
> original message from your e-mail system and/or computer database.  Thank
> you.
>
>
> *---*
>
> *NOTICE*:
>
> *You are advised that e-mail correspondence and attachments between the
> public and the Ridgewood Board of Education are obtainable by any person
> who files a request under the NJ Open Public Records Act (OPRA) unless it
> is subject to a specific OPRA exception.  You should have no expectation
> that the content of e-mails sent to or from school district e-mail
> addresses, or between the public and school district officials and
> employees, will remain private.*
>
>
> *---*
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/773L25E4XYM5MVRJ6Q7TSMFRSEPRDOGF/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JHCKHK2MOFV3G5YR5G4BWAABRSJXYXVI/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-12-11 Thread Serhiy Morhun

Hello, did anyone find a resolution for this issue? I'm having exactly the
same problem:

Hosted Engine VM is running with 5344MB of RAM, when trying to increase to
8192 it would not accept the change because the difference is not divisible
by 256.
When trying to increase to 8160 the change is accepted but log shows
"Hotset memory: changed the amount of memory on VM HostedEngine from 5344
to 5344" at the same time amount of guaranteed memory does increase to 8160
which, in turn, starts generating error messages that VM does not have all
the guaranteed RAM.

Serhiy Morhun

-- 



*---***


*THE INFORMATION CONTAINED IN THIS MESSAGE (E-MAIL AND ANY ATTACHMENTS) IS 
INTENDED ONLY FOR THE INDIVIDUAL AND CONFIDENTIAL USE OF THE DESIGNATED 
RECIPIENT(S).*

If any reader of this message is not an intended recipient 
or any agent responsible for delivering it to an intended recipient, you 
are hereby notified that you have received this document in error, and that 
any review, dissemination, distribution, copying or other use of this 
message is prohibited.  If you have received this message in error, please 
notify us immediately by reply e-mail message or by telephone and delete 
the original message from your e-mail system and/or computer database.  
Thank you.


*---*


**NOTICE**:

*You are advised that e-mail correspondence and attachments 
between the public and the Ridgewood Board of Education are obtainable by 
any person who files a request under the NJ Open Public Records Act (OPRA) 
unless it is subject to a specific OPRA exception.  You should have no 
expectation that the content of e-mails sent to or from school district 
e-mail addresses, or between the public and school district officials and 
employees, will remain private.*


*---*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/773L25E4XYM5MVRJ6Q7TSMFRSEPRDOGF/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-09-04 Thread Dionysis K

Now i noticed another strange i  deactivated the memory balloon option from
the VM hosted engine and tried to update the values again with the same
memory it still keeps the value of memory size at 5120 while the value of
physical memory guaranteed it changed to what we desire at the 8192 value
and then the error appears again in the vm engine

i ckecked the engine log file it shows the same errors!

is there are other logfile locations that can give us any clues ?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LFJAB6TY5CIY4B222JNIEZBHZPJMX7KA/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-09-04 Thread Dionysis K

Yes i have tried to to that as well update them both at the 8192 MB value it 
still reverts back to 5120 and transforms the guaranteed memory to 5461 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/U4HJO7L7SDXUMY67DRSUPLJVFJ66LB4A/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-09-04 Thread Simone Tiraboschi

On Wed, Sep 4, 2019 at 6:15 PM Dionysis K  wrote:

> if you see the engine zip log then
>
> i need to add that whatever value i am entering at the memory size field
> does not update it it still leaves it back to 5120 for some reason
>

And indeed in the logs I see that:
2019-09-04 18:04:56,535+03 INFO
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-8) [564cc40c] EVENT_ID: HOT_SET_MEMORY(2,039), Hotset memory:
changed the amount of memory on VM HostedEngine from 5120 to 5120
2019-09-04 18:04:56,585+03 INFO
 [org.ovirt.engine.core.bll.HotSetAmountOfMemoryCommand] (default task-8)
[6426f726] Running command: HotSetAmountOfMemoryCommand internal: true.
Entities affected :  ID: f058c188-43c5-4685-88e0-c88b3c9abd01 Type:
VMAction group EDIT_VM_PROPERTIES with role type USER
2019-09-04 18:04:56,587+03 INFO
 [org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default
task-8) [6426f726] START, SetAmountOfMemoryVDSCommand(HostName = Deimos,
Params:{hostId='0fafebe7-14e8-4e4f-916c-d56b7b5150f8',
vmId='f058c188-43c5-4685-88e0-c88b3c9abd01',
memoryDevice='VmDevice:{id='VmDeviceId:{deviceId='0c7de7ff-e68e-42d1-a807-4e3ee92201e8',
vmId='f058c188-43c5-4685-88e0-c88b3c9abd01'}', device='memory',
type='MEMORY', specParams='[node=0, size=2944]', address='',
managed='true', plugged='true', readOnly='false',
deviceAlias='ua-0c7de7ff-e68e-42d1-a807-4e3ee92201e8',
customProperties='null', snapshotId='null', logicalName='null',
hostDevice='null'}', minAllocatedMem='5461'}), log id: 4d62125f
2019-09-04 18:04:56,641+03 INFO
 [org.ovirt.engine.core.vdsbroker.SetAmountOfMemoryVDSCommand] (default
task-8) [6426f726] FINISH, SetAmountOfMemoryVDSCommand, return: , log id:
4d62125f
2019-09-04 18:04:56,669+03 INFO
 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-8) [6426f726] EVENT_ID: HOT_SET_MEMORY(2,039), Hotset memory:
changed the amount of memory on VM HostedEngine from 5120 to 5120

On the other side I also see:
2019-09-04 18:04:17,549+03 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engineScheduled-Thread-66) [] EVENT_ID:
VM_MEMORY_UNDER_GUARANTEED_VALUE(148), VM HostedEngine on host Deimos was
guaranteed 5461 MB but currently has 5120 MB

Can you please try updating also the guaranteed memory value in the UI?

> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WH253DT22NZL43KJAGMTDOUUCOGSSXEG/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/N42BQZMDOHIR425NNWNYVVQLPJIEMS5Y/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-09-04 Thread Dionysis K

if you see the engine zip log then  

i need to add that whatever value i am entering at the memory size field does 
not update it it still leaves it back to 5120 for some reason 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/WH253DT22NZL43KJAGMTDOUUCOGSSXEG/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-09-04 Thread Simone Tiraboschi

On Wed, Sep 4, 2019 at 4:30 PM Dionysis K  wrote:

> Hello I am having the same problem i cannot update the memory engine
> configuration
>
> i even updated the engine from 4.2.8 to 4.3.5 and the problem is still
> persisting!
>
> how we can find what its  going on ?
>

Hi,
can you please attach engine.log ?


> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/NDG22BXGTD2EPHVLTH7XNBBSTYRB7IML/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/Z4VGETHV2ZZKUGSPOYBBHXZURUGLOUHK/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-09-04 Thread Dionysis K

Hello I am having the same problem i cannot update the memory engine 
configuration 

i even updated the engine from 4.2.8 to 4.3.5 and the problem is still 
persisting!

how we can find what its  going on ?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NDG22BXGTD2EPHVLTH7XNBBSTYRB7IML/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-03-02 Thread Douglas Duckworth

Updating to 4.2.8 fixed this problem.  I can now hot add more RAM to hosted 
engine!

Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Fri, Feb 1, 2019 at 10:31 AM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Ok sounds good.

I will upgrade then hope this goes away.

On Thu, Jan 31, 2019, 12:09 PM Simone Tiraboschi 
mailto:stira...@redhat.com> wrote:


On Thu, Jan 31, 2019 at 4:20 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Hi Simone

Thanks again for your help!

Do you have some ideas on what I can try to resolve this issue?

Honestly I'm not able to reproduce this issue.
I can only suggest to try upgrading to 4.2.8 if still not there, and if still 
not working open a bug on bugzilla attaching engine.log.



Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Fri, Jan 25, 2019 at 3:15 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Yes, I do.  Gold crown indeed.

It's the "HostedEngine" as seen attached!


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Wed, Jan 23, 2019 at 12:02 PM Simone Tiraboschi 
mailto:stira...@redhat.com>> wrote:


On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Hi Simone

Can I get help with this issue?  Still cannot increase memory for Hosted Engine.

From the logs it seams that the engine is trying to hotplug memory to the 
engine VM which is something it should not happen.
The engine should simply update engine VM configuration in the OVF_STORE and 
require a reboot of the engine VM.
Quick question, in the VM panel do you see a gold crown symbol on the Engine VM?


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
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, 
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', hostDev

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-02-01 Thread Douglas Duckworth

Ok sounds good.

I will upgrade then hope this goes away.

On Thu, Jan 31, 2019, 12:09 PM Simone Tiraboschi 
mailto:stira...@redhat.com> wrote:


On Thu, Jan 31, 2019 at 4:20 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Hi Simone

Thanks again for your help!

Do you have some ideas on what I can try to resolve this issue?

Honestly I'm not able to reproduce this issue.
I can only suggest to try upgrading to 4.2.8 if still not there, and if still 
not working open a bug on bugzilla attaching engine.log.



Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Fri, Jan 25, 2019 at 3:15 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Yes, I do.  Gold crown indeed.

It's the "HostedEngine" as seen attached!


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Wed, Jan 23, 2019 at 12:02 PM Simone Tiraboschi 
mailto:stira...@redhat.com>> wrote:


On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Hi Simone

Can I get help with this issue?  Still cannot increase memory for Hosted Engine.

From the logs it seams that the engine is trying to hotplug memory to the 
engine VM which is something it should not happen.
The engine should simply update engine VM configuration in the OVF_STORE and 
require a reboot of the engine VM.
Quick question, in the VM panel do you see a gold crown symbol on the Engine VM?


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
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, 
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

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-01-31 Thread Simone Tiraboschi

On Thu, Jan 31, 2019 at 4:20 PM Douglas Duckworth 
wrote:

> Hi Simone
>
> Thanks again for your help!
>
> Do you have some ideas on what I can try to resolve this issue?
>

Honestly I'm not able to reproduce this issue.
I can only suggest to try upgrading to 4.2.8 if still not there, and if
still not working open a bug on bugzilla attaching engine.log.


>
>
> Thanks,
>
> Douglas Duckworth, MSc, LFCS
> HPC System Administrator
> Scientific Computing Unit 
> Weill Cornell Medicine
> 1300 York Avenue
> New York, NY 10065
> E: d...@med.cornell.edu
> O: 212-746-6305
> F: 212-746-8690
>
>
> On Fri, Jan 25, 2019 at 3:15 PM Douglas Duckworth 
> wrote:
>
>> Yes, I do.  Gold crown indeed.
>>
>> It's the "HostedEngine" as seen attached!
>>
>>
>> Thanks,
>>
>> Douglas Duckworth, MSc, LFCS
>> HPC System Administrator
>> Scientific Computing Unit 
>> Weill Cornell Medicine
>> 1300 York Avenue
>> New York, NY 10065
>> E: d...@med.cornell.edu
>> O: 212-746-6305
>> F: 212-746-8690
>>
>>
>> On Wed, Jan 23, 2019 at 12:02 PM Simone Tiraboschi 
>> wrote:
>>
>>>
>>>
>>> On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth <
>>> dod2...@med.cornell.edu> wrote:
>>>
 Hi Simone

 Can I get help with this issue?  Still cannot increase memory for
 Hosted Engine.

>>>
>>> From the logs it seams that the engine is trying to hotplug memory to
>>> the engine VM which is something it should not happen.
>>> The engine should simply update engine VM configuration in the OVF_STORE
>>> and require a reboot of the engine VM.
>>> Quick question, in the VM panel do you see a gold crown symbol on the
>>> Engine VM?
>>>
>>>

 Thanks,

 Douglas Duckworth, MSc, LFCS
 HPC System Administrator
 Scientific Computing Unit 
 Weill Cornell Medicine
 1300 York Avenue
 New York, NY 10065
 E: d...@med.cornell.edu
 O: 212-746-6305
 F: 212-746-8690


 On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth <
 dod2...@med.cornell.edu> wrote:

> 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,
> 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.o

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-01-31 Thread Douglas Duckworth

Hi Simone

Thanks again for your help!

Do you have some ideas on what I can try to resolve this issue?


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Fri, Jan 25, 2019 at 3:15 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Yes, I do.  Gold crown indeed.

It's the "HostedEngine" as seen attached!


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Wed, Jan 23, 2019 at 12:02 PM Simone Tiraboschi 
mailto:stira...@redhat.com>> wrote:


On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Hi Simone

Can I get help with this issue?  Still cannot increase memory for Hosted Engine.

From the logs it seams that the engine is trying to hotplug memory to the 
engine VM which is something it should not happen.
The engine should simply update engine VM configuration in the OVF_STORE and 
require a reboot of the engine VM.
Quick question, in the VM panel do you see a gold crown symbol on the Engine VM?


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
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, 
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 HostedE

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-01-25 Thread Douglas Duckworth

Yes, I do.  Gold crown indeed.

It's the "HostedEngine" as seen attached!


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Wed, Jan 23, 2019 at 12:02 PM Simone Tiraboschi 
mailto:stira...@redhat.com>> wrote:


On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
Hi Simone

Can I get help with this issue?  Still cannot increase memory for Hosted Engine.

From the logs it seams that the engine is trying to hotplug memory to the 
engine VM which is something it should not happen.
The engine should simply update engine VM configuration in the OVF_STORE and 
require a reboot of the engine VM.
Quick question, in the VM panel do you see a gold crown symbol on the Engine VM?


Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
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, 
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='VmD

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-01-23 Thread Simone Tiraboschi

On Wed, Jan 23, 2019 at 5:51 PM Douglas Duckworth 
wrote:

> Hi Simone
>
> Can I get help with this issue?  Still cannot increase memory for Hosted
> Engine.
>

>From the logs it seams that the engine is trying to hotplug memory to the
engine VM which is something it should not happen.
The engine should simply update engine VM configuration in the OVF_STORE
and require a reboot of the engine VM.
Quick question, in the VM panel do you see a gold crown symbol on the
Engine VM?


>
> Thanks,
>
> Douglas Duckworth, MSc, LFCS
> HPC System Administrator
> Scientific Computing Unit 
> Weill Cornell Medicine
> 1300 York Avenue
> New York, NY 10065
> E: d...@med.cornell.edu
> O: 212-746-6305
> F: 212-746-8690
>
>
> On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth 
> wrote:
>
>> 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,
>> 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 throu

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-01-23 Thread Douglas Duckworth

Hi Simone

Can I get help with this issue?  Still cannot increase memory for Hosted Engine.

Thanks,

Douglas Duckworth, MSc, LFCS
HPC System Administrator
Scientific Computing Unit
Weill Cornell Medicine
1300 York Avenue
New York, NY 10065
E: d...@med.cornell.edu
O: 212-746-6305
F: 212-746-8690


On Thu, Jan 17, 2019 at 8:08 AM Douglas Duckworth 
mailto:dod2...@med.cornell.edu>> wrote:
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, 
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 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 Sy

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

2019-01-17 Thread Simone Tiraboschi

On Wed, Jan 16, 2019 at 8:22 PM Douglas Duckworth 
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 
> Weill Cornell Medicine
> 1300 York Avenue
> New York, NY 10065
> E: d...@med.cornell.edu
> O: 212-746-6305
> F: 212-746-8690
>
>
> On Wed, Jan 16, 2019 at 1:58 PM Douglas Duckworth 
> wrote:
>
>> Hello
>>
>> I am trying to increase Hosted Engine physical memory above 4GB
>> Thanks,
>>
>> Douglas Duckworth, MSc, LFCS
>> HPC System Administrator
>> Scientific Computing Unit 
>> Weill Cornell Medicine
>> 1300 York Avenue
>> New York, NY 10065
>> E: d...@med.cornell.edu
>> O: 212-746-6305
>> F: 212-746-8690
>>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/WGSXQVVPJJ2CRF3QH7N2SAQ2B3S7PBLO/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/F2SRPF6MEK7QTPIB5RKAMVGO7RCBJJSG/

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

[ovirt-users] Re: Cannot Increase Hosted Engine VM Memory

18 matches

Site Navigation

Mail list logo

Footer information