on windows host, move the vm window to the desktop border, so half of the vm
window is hidden, then click the mouse inside vm
you will find won't be able to move the mouse to some area of the vm
seems some kind of coordinate calculation bugs___
vbox-
On Sun, Oct 18, 2009 at 14:03, Huihong Luo wrote:
>
> some VMs always run on 100% cpu. this was not the case before
If someone knows what the deal is with this, I've been ripping my hair
out for the last few versions of VirualBox. There is some discussion
about this at: http://forums.virtualbox
On 10/17/2009 02:11 PM, walt wrote:
> The latest revision is 23759, and I'm seeing corruption of the
> my-virtual-machine-name.xml files after discarding snapshots.
Well, I'm mystified. I spent hours today making and discarding
snapshots without any problems.
Yesterday I sent a follow-up post de
some VMs always run on 100% cpu. this was not the case before___
vbox-dev mailing list
vbox-dev@virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-dev
Chris Smowton writes:
> > IDs sharing/quessing is really another issue. Some of those are not that
easy
> > to separate, for example texture ids...it's valid to use *any* id which
> > application chooses, it might be a value returned by glGenTextures but not
> > necessary. So 1 client could reall
Might add some checks or switch to a nop dispatch table in such cases or make
sure default window is never visible, anyway that's really a minor issue as we
don't want to behave exactly like a real gpu drivers here, for ex. like the
segfaults you've observed when a bound window was destroyed.
Chris Smowton writes:
> I just finished coding a similar solution, I'll see how our changes
> compare :)
>
> In the course of doing so, I got to know the render SPU's "default
> window," which it creates at startup and uses to perform real-libGL
> MakeCurrents when the client hasn't sent us a Wi
Thanks for the insights.
I checked the vhdWrite() function, it has several seeks for a write, and disk
head moves back and forth, so it should be optimized.
For large one direction write, vhd/vdi is about a factor of 2 slower.
I will try and see if the performance can be improved.
- hl
-
