<div dir="ltr"><div>Hi,</div><div><br></div><div>Thank you all for the help.</div><div><br></div>Updated to Virtualbox 4.3.0 and added the "keepalive" loop to my app. <div>The VM is running very stable now.<div><div>
<br></div><div>Regards,</div><div>Ferenc</div><div><br></div><div><br></div><div><br></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 23 October 2013 03:56, Tom Samplonius <span dir="ltr"><<a href="mailto:tom@samplonius.org" target="_blank">tom@samplonius.org</a>></span> wrote:<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"><div class="im"><div>On 2013-10-18, at 1:29 PM, Ferenc Holzhauser <<a href="mailto:ferenc.holzhauser@gmail.com" target="_blank">ferenc.holzhauser@gmail.com</a>> wrote:</div>
</div><div><div class="im"><br><blockquote type="cite"><p>Hi Anthony,</p><p>That must be it: it is running in virtualbox indeed. Are you aware of any workaround/fix to try? I'm quite attached to this VM setup. Would be great if I could make it work reliably. </p>
<p>Ferenc</p></blockquote><div><br></div></div><div><div> You may want to try Virtualbox 4.3.0, released a few days. This is listed in the release notes for 4.30:</div><div><br></div><div>* VMM: major rewrite of the VT-x code and the AMD-V code including many bug fixes and performance improvements (for example <a href="https://www.virtualbox.org/ticket/9659" target="_blank">https://www.virtualbox.org/ticket/9659</a>)</div>
<span class="HOEnZb"><font color="#888888"><div><br></div><div><br></div><div><br></div><div><br></div><div>Tom</div></font></span></div><div><br></div></div><br></div></blockquote></div><br></div>