<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2016-09-30 15:35 GMT+02:00 Michal Skrivanek <span dir="ltr"><<a href="mailto:michal.skrivanek@redhat.com" target="_blank">michal.skrivanek@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><br><div>that is a very low level error really pointing at HW issues. It may or may not be detected by memtest…but I would give it a try</div><div><span class=""><br></span></div></div></blockquote><div><br></div><div>I left memtest86 running for 2 days and no error detected :(<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><span class=""><blockquote type="cite"><div><div dir="ltr"><div>The only difference that this host (vmhost01) has is that it was the first host installed in my self-hosted engine installation. But I have already reinstalled it from GUI and menawhile I've upgraded to 4.0.4 from 4.0.3.<br></div></div></div></blockquote><div><br></div></span><div>does it happen only for the big 96GB VM? The others which you said are working, are they all small?</div>Might be worth trying other system stability tests, playing with safer/slower settings in BIOS, use lower CPU cluster, etc</div><div><div class="h5"><br></div></div></div></blockquote><div><br></div><div>Yep, it happens only for the 96GB VM. Other VMs with fewer RAM (16GB for example) can be created on or migrated to that host flawlessly. I'll try to play a little with BIOS settings but otherwise I'll have the HW replaced. I was only trying to rule out possible oVirt SW problems due to that host being the first I deployed (from CLI) when I installed the cluster.<br><br></div><div>Thanks!<br></div></div><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Davide Ferrari<br></div>Senior Systems Engineer<br></div></div>
</div></div>