Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chocolatey-test-environment broken with VirtualBox 5.2.22 #31

Open
basictheprogram opened this issue Nov 26, 2018 · 2 comments
Open

chocolatey-test-environment broken with VirtualBox 5.2.22 #31

basictheprogram opened this issue Nov 26, 2018 · 2 comments

Comments

@basictheprogram
Copy link

basictheprogram commented Nov 26, 2018

Upgraded to VirtualBox Version 5.2.22 r126460 (Qt5.6.3) on macOS 10.12.6 and the VM networking does not work. In fact, the 2012 VM does not even detect a network interface.

menubar_and_chocolatey-test-environment_default_1543249167931_27622__running__and_new_issue_ _chocolatey_chocolatey-test-environment

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Cloning VM...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ferventcoder/win2012r2-x64-nocm' is up to date...
==> default: Setting the name of the VM: chocolatey-test-environment_default_1543249167931_27622
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 5985 (guest) => 5985 (host) (adapter 1)
    default: 3389 (guest) => 3389 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
    default: 5986 (guest) => 55986 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: WinRM address: 127.0.0.1:5985
    default: WinRM username: vagrant
    default: WinRM execution_time_limit: PT2H
    default: WinRM transport: negotiate
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
$ vagrant box outdated
Checking if box 'ferventcoder/win2012r2-x64-nocm' is up to date...
$ vagrant box update
==> default: Checking for updates to 'ferventcoder/win2012r2-x64-nocm'
    default: Latest installed version: 1.0.0
    default: Version constraints:
    default: Provider: virtualbox
==> default: Box 'ferventcoder/win2012r2-x64-nocm' (v1.0.0) is running the latest version.
$ git pull upstream master
From https://github.com/chocolatey/chocolatey-test-environment
 * branch            master     -> FETCH_HEAD
Already up to date.
$ vagrant --version
Vagrant 2.2.1
@basictheprogram
Copy link
Author

basictheprogram commented Nov 26, 2018

I notice the base image has Adapter Type: Intel PRO/1000 MT Desktop (82540EM0

But the clone has Adapter Type: Paravirtualized Network (virtio-net)

And the adapter is not working properly.

chocolatey-test-environment_default_1543250201610_86129__running_

https://www.virtualbox.org/wiki/Guest_OSes
Windows Server 2012 (also R2) | Works, with Additions

Using opentable/win-2012r2-standard-amd64-nocm as VM and it also doesn't get a Network Interfaces.

Opened a ticket at Virtualbox too: https://www.virtualbox.org/ticket/18152

@basictheprogram
Copy link
Author

Maybe it's a vagrant issue?

Navigating to

~/.vagrant.d/boxes/ferventcoder-VAGRANTSLASH-win2012r2-x64-nocm/1.0.0/virtualbox

and importing the box.ovf directly into VirtualBox things work as expected

win2012r2x64__running_

basictheprogram added a commit to basictheprogram/chocolatey-test-environment that referenced this issue Nov 29, 2018
basictheprogram added a commit to basictheprogram/chocolatey-test-environment that referenced this issue Nov 29, 2018
Windows Server 2016

WIP chocolatey-community#31 but for
Windows Server 2016
c-luu pushed a commit to c-luu/chocolatey-test-environment that referenced this issue Apr 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant