<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Mar 29, 2018, 4:14 AM Colin Coe <<a href="mailto:colin.coe@gmail.com">colin.coe@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi all<div><br></div><div>I suspect one of our hypervisors is faulty but at this stage I can't prove it.</div><div><br></div><div>We're running RHV 4.1.7 (about to upgrade to v4.1.10 in a few days). </div><div><br></div><div>I'm planning on create a negative host affinity rule to prevent all current existing VMs from running on the suspect host. Afterwards I'll create a couple of test VMs and put them in a positive host affinity rule so they only run on the suspect host. </div><div><br></div><div>There are about 150 existing VMs, are there any known problems with host affinity rules and putting 150 or so VMs in the group?</div><div><br></div><div>This is production so I need to be careful.</div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Why not move it to maintenance, then create a new test cluster for it and use it for testing? </div><div dir="auto">Y. </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Thanks</div></div>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank" rel="noreferrer">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div></div></div>