forgot that "press 6 during boot" thingie
Just tried that and noticed:
there is an awful pause during boot right after I get some vbox "additions installed" loggings.
However, I can "click and focus" into the vm and get not only the keyboard mapped, but also can move the mouse again (resolution wizard). The issue with the lower part of the screen not available (the focus jumps back to the host) still exists, but I found a workaround:
Entering the guest window at different speeds and from different directions seems to generate different "focus boundaries" (where I jump back to the host). I even managed to achieve a working setup so I could use the screen setup wizard. However, sometimes I need to click two or three times until a button is finally activated.
Just set resolution to 1024x768 in the wizard to be on the safe side, logged in and checked "system settings, display and monitor". The "auto" entry is there once again, but resizing the vm window does not give any other resolutions as one may expect. "Host+G" does no resizing either, I just get a nice blank space around the vm ^^.
The mouse focus issue with the changing borders seems to be gone for now.
For testing purposes, I shut down the machine, resized the windows to something odd during the text based part of the boot process, again the vboxguest: loaded successfully log entry can be read for around 20 seconds, then network stuff, 30 secs waiting for default route if.
When the GUI login screen appears, the vm window is set to 1024x768 again, so I just resized it again before login (hopefully this would make the vbox additions grab another possible resolution).
And here we go, I now have 1713x932 (auto) as an option, the mouse seems to work ok.
If this is persistent, I can live with that, although the user experience is a bit on the annoying side
compared to what I see from the windows vms, but it is no showstopper anymore.
Let me know if I can provide something to improve that behaviour. If one of the goals of PCBSD is to make transitioning/upgrading from windows to a better OS nice and easy, my guess is that other people may try it via vbox too, so ironing out this weird issue would be a plus. If it´s only me, forget about the whole thing
but maybe this has something to do with vbox/vboxtools integration.
So far I used unices from CLI only, mainly servers and appliances, then switching to ssh asap, but I´m really keen on making a switch on the desktop as well, then run windows from within a vm when needed.