Created attachment 797858 [details] engine.log Description of problem: When cluster policy with pintohost is active. Then when vm which is not pinned to any host is migrated with 'auto selected host', this vm fails to migrated and is shuted down. Version-Release number of selected component (if applicable): is13 How reproducible: always Steps to Reproduce: 1. Create two hosts. in cluster which use policy with only pin to host filter. 2. Create vm which is not pinned to any host and run it. 3. Try to migrate this vm with option 'select host automatically'. Actual results: Vm fail to migrate and is shut down. Expected results: Vm will migrate. Additional info:
Happend also when other filters are active, not only pin-to-host.
Hi Ondra, I'm missing the log parts from the scheduling process. Can you please add them? Also, what is your cluster policy optimization (servers? desktops?) There are several options that allow overcommitment, such as ksm, ballooning etc so we really need you to specify all these settings to evaluate the memory calculations.
Please ignore previous comment. Are you using one of the existing policies or did you create your own?
I used only pin-to-host internal filter.
(In reply to Ondra Machacek from comment #4) > I used only pin-to-host internal filter. What about actual memory availability? ie- optimization, etc? Relevant logs?
I didn't use any optiomizations. no page sharing, ksm and ballooning This problem also appers when I do: Using RAM filter, overload RAM of host1 create vm and run it on host2. try to migrate this vm to host1, migration also fails and vm is going down. When I add to RAM filter also migration filter, then the problem don't appear again.
tested on is17
Closing - RHEV 3.3 Released