Thanks for the quick responses guys! I had it set to 128 MB, cut down to 64 MB per your and Klaus's recommendations.
This fixes all issues on both Leopard and Vista on non-compositing window managers (ie Metacity.) Compiz is still misbehaving. I can't seem to repro Leopard's aborts even with changing the memory back to 128, so not sure what the hell that's about. Changed system settings to always leave core dumps, if I complain of an abort again it'll have a dump file with it. This leaves the full-screen issue: It turns out this issue occurs using Compiz, but not when using Metacity. No UI updates at all in fullscreen - if I type into a guest window the text does not show up. The cursor doesn't even blink in a terminal window. However, the mouse cursor still changes when hovering over 'interesting points' (eg for window resizing), and it appears that I can move a window - but the UI won't be updated. Two other notes on Compiz's behavior as a guest: 1. Guest running 'glxgears': The gears do not show up in the box. Once I got them to show up in the lower-left corner by toying around with the window, and once they showed up in the box after switching between Firefox and VirtualBox windows on the host. Thus far cannot reliably reproduce either. 2. Guest running Compiz: The menus appear an update or so behind - it honestly looks like it's somehow missed the last frame swap on a double-buffered visual. Screenshot: http://gk.dullcity.com/images/menu%20fade%20incomplete.jpg Opening the Applications menu causes the menu to show up, but the 'fade' effect does not complete - it is about 80% opaque, until I move the mouse over one of the menu entries. *Then* the fade effect completes. If I hover the mouse over menu entry 1, then move it over menu entry 2, menu entry 1 will usually be highlighted. The next move to menu entry 1 again will cause menu entry 2 to be highlighted. This behavior does not reproduce if glxgears is running in the background (even though the gears don't show up.) However, Metacity seems to work properly as a guest, and glxgears works fine when run under Metacity in the guest OS. Let me know if there's anything else I can provide to help out. Thanks, Greg On Jul 16, 2009, at 5:35 AM, Michael Thayer wrote: Common to both hosts: - User login screen is usually squashed to top ~60 pixels of guest window. Sometimes resizes correctly after login. This has been fixed in our code since 3.0.2 was released (see http://www.virtualbox.org/ticket/3095 ) and can be worked around by reducing the video RAM allocated to the guest. If you see it at all you are probably wasting host memory :) Leopard host: - Switching back and forth between full screen randomly causes guest to abort. - Attempting to shut down the guest via the "shutdown" command or the guest's shutdown button causes guest to abort. Abort as in a little red icon in the VM selector window? It would be very helpful if you could try to get a core dump for us (see http://www.virtualbox.org/wiki/Core_dump - MacOS is the second section, Windows the last) and open a bug report for it. Windows host: - Switching to full screen works, but the display is never updated once in full screen - it's frozen in place. I can kind of drag a window but I get no UI feedback. So fullscreen is useless. Does that mean no UI updates at all? E.g. if you type into a guest window, you will not see the text? And does exiting and re-entering full-screen mode update the display?
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
