I have discovered that incompatibilities between 5.1 and 5.2, at least for Windows7 guests, may leave virtualbox in an state where the pointer is non-operative and the keyboard is locked to the vbox guest. I tried everything I could think of, but could not restore access to the host system. This only happened after working within the guest and then trying to switch back to using FreeBSD.
I tried <Rt. CTRL> and got a pop-up that the pointer could be connected to the guest by clicking in the guest window or selecting the "Connect" button. Neither worked. The pointer would not work on either host or guest. The keyboard worked on the guest (Windows7), but could not be returned to the host (FreeBSD 11.1). Eventually I switched to a vty and killed vbox. I then rebooted the guest and immediately update the guest additions. Since then I have had no problems. Bottom line is to update the guest additions immediately after updating virtualbox-ose to 5.2. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 _______________________________________________ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
