@realMaxA
Разработчик 1С

Что идёт не так при запуске virtualbox при помощи vagrant?

Добрый день.
Пытаюсь настроить VM для vagrant.
Host OS: Windows Server 2012R2
Guest OS: Windows 10 Pro
Выполняю по инструкции: huestones.co.uk/node/305
Всё работает до момента ```vagrant up```:
D:\Data\vagrant\test>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 3389 (guest) => 3389 (host) (adapter 1)
    default: 5985 (guest) => 5985 (host) (adapter 1)
    default: 5986 (guest) => 55986 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> 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
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
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.

D:\Data\vagrant\test>


Машина поднимается и работает:
D:\Data\vagrant\test>vagrant status
Current machine states:

default                   running (virtualbox)

The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.


Через gui виртуалбокса можно залогиниться, но управление через winrm, как видно, не работает. Также не работает и ```vagrant rdp```:
D:\Data\vagrant\test>vagrant rdp
An authorization error occurred while connecting to WinRM.

User: vagrant
Endpoint: http://127.0.0.1:5985/wsman
Message: WinRM::WinRMAuthorizationError


openssh установлен "из коробки" win10.
Пользователь "vagrant" с паролем "vagrant".

ssh с хост-машины в гостевую работает (```ssh -p 2222 -l vagrant localhost```)

Что идёт не так и что нужно сделать, чтобы работало как надо?
  • Вопрос задан
  • 446 просмотров
Пригласить эксперта
Ответы на вопрос 1
@realMaxA Автор вопроса
Разработчик 1С
Да, наверное надо привести сам Vagrantfile:
Vagrant.configure("2") do |config|
  config.vm.box = "windows10-rus"
end
Ответ написан
Комментировать
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы