Have you read KB927917? It describes the situation quite well; it's a more helpful error message than the “Operation aborted” we used to get, anyway. See this blog for more background on what it means.
It's not directly connected to virtual-machine or not; what you have is a race condition, where a script can load too early and try to manipulate elements that haven't been fully loaded by IE's HTML parser yet. Race conditions are inherently difficult to pin down as factors like being in a VM or how fast the server is responding can affect whether the error occurs or not.
You need to narrow down which script is responsible by commenting all the <script>
elements out and adding them back in one-by-one until you get the error. Then you need to delay the operation of whatever that script is doing, for example by moving it into a window.onload
event handler.