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

None of windows boxes are going through #47

Open
eliassal opened this issue Mar 1, 2025 · 1 comment
Open

None of windows boxes are going through #47

eliassal opened this issue Mar 1, 2025 · 1 comment

Comments

@eliassal
Copy link

eliassal commented Mar 1, 2025

I have vagrant on a fedora 41 VM with VB, running any linux based box works fine. I tried to run a windows server box using your boxes as follows:

config.vm.define "win2k16web" do |win2k16web|
    win2k16web.vm.box = "jborean93/WindowsServer2016"
    win2k16web.vm.box_version = "1809.0.2407"
    win2k1web.vm.hostname = "win2k16-web"
    win2k16web.vm.network "private_network", ip: "192.168.56.40"

or

config.vm.define("win2k19web") do |win2k19web|
    win2k19web.vm.box = "jborean93/WindowsServer2019"
    win2k19web.vm.box_version = "1.2.0"
    win2k19web.vm.hostname = "win2k19-web"
    win2k19web.vm.network "private_network", ip: "192.168.56.40"
  end

It starts to create the VM

Bringing machine ‘win2k19web’ up with ‘virtualbox’ provider…
==> win2k19web: Clearing any previously set forwarded ports…
==> win2k19web: Clearing any previously set network interfaces…
==> win2k19web: Preparing network interfaces based on configuration…
win2k19web: Adapter 1: nat
win2k19web: Adapter 2: hostonly
==> win2k19web: Forwarding ports…
win2k19web: 22 (guest) => 2222 (host) (adapter 1)
==> win2k19web: Booting VM…
==> win2k19web: Waiting for machine to boot. This may take a few minutes…
win2k19web: SSH address: 127.0.0.1:2222
win2k19web: SSH username: vagrant
win2k19web: SSH auth method: private key

then it gets stuck for 5-10 minutes then I have a timeout as follows

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.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you’re using a custom box, make sure that networking is properly
working and you’re able to connect to the machine. It is a common
problem that networking isn’t setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout (“config.vm.boot_timeout”) value.

When I fire VB GUI, click on the VM > show, I see a windows server interface with a circle that never ends

Image

Does this mean that I cant run win boxes in a linux vagrant environment?

@eliassal eliassal changed the title None of windows images are going through None of windows boxes are going through Mar 1, 2025
@jborean93
Copy link
Owner

I'm not sure sorry, I've not used VirtualBox in a while but they did work the last time I built these images. There's a good chance something is wrong but I probably don't have much time to debug this VirtualBox side right at this moment sorry.

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

2 participants