From owner-freebsd-emulation@freebsd.org Wed Oct 25 22:05:13 2017 Return-Path: Delivered-To: freebsd-emulation@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69DD2E55462 for ; Wed, 25 Oct 2017 22:05:13 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4727F840E6 for ; Wed, 25 Oct 2017 22:05:13 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 432BEE55461; Wed, 25 Oct 2017 22:05:13 +0000 (UTC) Delivered-To: emulation@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40C79E55460 for ; Wed, 25 Oct 2017 22:05:13 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E2EB4840E5 for ; Wed, 25 Oct 2017 22:05:12 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x22a.google.com with SMTP id t203so982725vke.0 for ; Wed, 25 Oct 2017 15:05:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=bjXEcuRmUVpEWDay2dzUMnkg7suuxrn2PzGwtMfYxlQ=; b=D+wPIfhhB0jo1aXZ/8V2EJn8pYykLE6bSIUAV9L195L7/Z63yyewpPvKgVFSHgQVMi /yTcIKBcyh8Yj0OnEiyWBXj1hai/eR55RSiMrEtGzPWqFYMnZA2zJjkeHj6GeV2D5N25 TxTdYq0jGBdqBZ/JWhSqM915QLZmOlzmubx8WYWc4HzcwbPm0A+xOXCbmGoL4346ck42 NZ4bHdtCteIEwxYy5ro0njtt2AeEacfvpLr4i8my+6SUGBdGn0qkQuYqyWZ6Aj4GT6YS 3hBdKAwODZVkiMVqUFs3KaD9fWaBAQrAw/Fbo46Gge+ineIn06eJbmIn+kk/A1PB6iTy 04nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=bjXEcuRmUVpEWDay2dzUMnkg7suuxrn2PzGwtMfYxlQ=; b=YUYqFSLphDpVdJUeqN7FT7Aqx3cAVl+w1HffW2d0qKMpcz0LCkbQu0GFYLcJfk+WOh 32aAgLfkm0Zur6e8zqfd2lGfYDIMoG/HsuVr1MWSmT+gDUTOMHP49gbw2mZvW+aiaVy+ 1UXTdWVlj4ZTOyZlxV7Msd7j7wqtIHXJPpXrbaCoGfP3G68Y9YgBukKWyr4jag/sh041 FAvcYNGUxQ93QMj8rAxcL+pSQ6auOOrw2ZEMZ0U/K1pm7/566jE7VhAHP+ewhx+5uU1T vysZkqXNg7+hyNIINoMxXP+mTRcWFtFhrbPGhgvUQ6h1JTwrjZpPWlJ1qM4BDtQKMbqq klSw== X-Gm-Message-State: AMCzsaXFdTNVFktmH2E5rGoX2nl/fEI5dSYyqFxgvcMJj9m4x2iOrwp4 EkjLjrPNtERFGDcnI7ot4OxY+3Ap+3aXi/oUgfjH6A== X-Google-Smtp-Source: ABhQp+SxP+tzesvBD5SSvORtzBt2py97W5MoAAo0wz3hBC6BSe3F6Pi0KtSBwomgbXN+mQCws/+3IFpEp5nNfm/NZbg= X-Received: by 10.31.212.134 with SMTP id l128mr2287093vkg.184.1508969111735; Wed, 25 Oct 2017 15:05:11 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.85.8 with HTTP; Wed, 25 Oct 2017 15:05:11 -0700 (PDT) From: Kevin Oberman Date: Wed, 25 Oct 2017 15:05:11 -0700 X-Google-Sender-Auth: zpShdkOm_EnRycwoMYxK4P9A5nA Message-ID: Subject: Critical to update vbox guest additions after update to 5.2 To: "freebsd-emulation@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2017 22:05:13 -0000 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 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: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683