-
Notifications
You must be signed in to change notification settings - Fork 1.1k
VirtualBox 4.3.8 r92456 Guest Additions Issues and Windows 2012R2 #40
Comments
I'm a little unclear what the issue is with the tools. Can you clarify? |
Apparently the tools are not installed correctly. $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'win2012R2_virtualbox'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Fixed port collision for 22 => 2222. Now on port 2200.
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2200 (adapter 1)
[default] -- 3389 => 3389 (adapter 1)
[default] -- 5985 => 5985 (adapter 1)
[default] Running 'pre-boot' VM customizations...
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
[default] Machine booted and ready!
[default] No guest additions were detected on the base box for this VM! Guest
additions are required for forwarded ports, shared folders, host only
networking, and more. If SSH fails on this machine, please install
the guest additions and repackage the box to continue.
This is not an error message; everything may continue to work properly,
in which case you may ignore this message. |
a rollback to virtualbox 4.3.6 confirms it. |
There may be a problem with the driver certification as mentioned here https://forums.virtualbox.org/viewtopic.php?f=1&t=60108 Am 07.03.2014 um 00:41 schrieb Luis Mayorga notifications@github.com:
|
Uhmmmm. It works in 4.3.6. Need to check details |
The 4.3.6 is signed with an older timestamp. The oracle-cert seems to be valid until February 2014, and that would be fine to install 4.3.6 even now. |
Fixed in #41. |
This might be a VirtualBox issue with their latest version of the Guest Additions for Windows on 2012R2. Seems that are not installed properly.
Going back to 4.3.7.
The text was updated successfully, but these errors were encountered: