This is a side-note for anyone that virtualizes windows guests on a linux host and provides the headless guests for remote access. For all previous 5.1 host updates, the headless guests would make use of the existing guest additions to allow normal login and update of guest additions within the guest itself. Apparently there is an incompatibility between 5.1.X guest additions and the new 5.2 guest additions that prevent guests from recognizing existing 5.1.x guest additions after the host is updated to 5.2. (meaning you have to start the windows guest normally on the host (or use VBoxManage on the host) to install the new 5.2 guest additions. This has the side effect of making win guests unavailable for remote access until 5.2 guest additions are installed. If accessed remotely before the guest addition update, the login screen will be visible, but there is no way to interact with it as neither keyboard or mouse can be captured (with or without use of the local host-key -- usually right-ctrl) I don't suspect too many people will fall into this issue unless you virtualize guests on a server and provide access via network (remote) access via rdesktop or the like. (but if you do, know you remote clients will have no way to login until you update their guest additions) The kicker is it requires host access to fix, where before remote clients could update their own guest additions following vbox version update on the host. Reported upstream ticket/17259 (also, there are a few other issues for headless guests like setvideomodehint color depth settings being lost, etc.. and there seems to be a bit of degraded video performance for headless guests) Hopefully these bumps will get ironed out before 5.2.1 comes out (or 5.2.2) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org