<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On 2013-10-18, at 1:29 PM, Ferenc Holzhauser <<a href="mailto:ferenc.holzhauser@gmail.com">ferenc.holzhauser@gmail.com</a>> wrote:</div><div><br class="Apple-interchange-newline"><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> 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">https://www.virtualbox.org/ticket/9659</a>)</div><div><br></div><div><br></div><div><br></div><div><br></div><div>Tom</div></div><div><br></div></div><br></body></html>