Vagrant up fails with `require': cannot load such file -- winrm (LoadError)

54 views
Skip to first unread message

Gaurav Talreja

unread,
Dec 18, 2019, 5:44:55 AM12/18/19
to Vagrant
Hi everyone,
When I try to `vagrant up --no-provision` a Windows Vagrant box I get the following error:

```
'2019-12-17 09:30:28,204     INFO  Executing: Process "vagrant up --no-provision --parallel"
2019-12-17 09:30:33,600    DEBUG  /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- winrm (LoadError)
2019-12-17 09:30:33,602    DEBUG  	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
2019-12-17 09:30:33,602    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/communicators/winrm/shell.rb:9:in `block in <top (required)>'
2019-12-17 09:30:33,602    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/util/silence_warnings.rb:8:in `silence!'
2019-12-17 09:30:33,602    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/communicators/winrm/shell.rb:8:in `<top (required)>'
2019-12-17 09:30:33,603    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/communicators/winrm/communicator.rb:6:in `require_relative'
2019-12-17 09:30:33,603    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/communicators/winrm/communicator.rb:6:in `<top (required)>'
2019-12-17 09:30:33,603    DEBUG  	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
2019-12-17 09:30:33,603    DEBUG  	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
2019-12-17 09:30:33,603    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/communicators/winrm/plugin.rb:15:in `block in <class:Plugin>'
2019-12-17 09:30:33,603    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/registry.rb:27:in `get'
2019-12-17 09:30:33,603    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/machine.rb:259:in `communicate'
2019-12-17 09:30:33,603    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/machine.rb:141:in `initialize'
2019-12-17 09:30:33,604    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/vagrantfile.rb:81:in `new'
2019-12-17 09:30:33,604    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/vagrantfile.rb:81:in `machine'
2019-12-17 09:30:33,604    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/environment.rb:715:in `machine'
2019-12-17 09:30:33,604    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/plugin/v2/command.rb:180:in `block in with_target_vms'
2019-12-17 09:30:33,604    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/plugin/v2/command.rb:204:in `block in with_target_vms'
2019-12-17 09:30:33,604    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/plugin/v2/command.rb:186:in `each'
2019-12-17 09:30:33,604    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/plugin/v2/command.rb:186:in `with_target_vms'
2019-12-17 09:30:33,605    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/plugins/commands/up/command.rb:87:in `execute'
2019-12-17 09:30:33,605    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/cli.rb:66:in `execute'
2019-12-17 09:30:33,605    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/lib/vagrant/environment.rb:290:in `cli'
2019-12-17 09:30:33,605    DEBUG  	from /usr/share/vagrant/gems/gems/vagrant-2.2.5/bin/vagrant:182:in `<top (required)>'
2019-12-17 09:30:33,605    DEBUG  	from /usr/share/vagrant/gems/bin/vagrant:23:in `load'
2019-12-17 09:30:33,605    DEBUG  	from /usr/share/vagrant/gems/bin/vagrant:23:in `<main>'
```

I'm using,
vagrant-2.2.5-1.fc30.noarch
vagrant-libvirt (0.0.45, system)
vagrant-sshfs (1.3.1, system)
also tried with vagrant-2.2.6

can anyone help me with this issue?

Alvaro Miranda Aguilera

unread,
Dec 24, 2019, 4:42:49 AM12/24/19
to vagra...@googlegroups.com
share the vagrantfile you are using the output of vagrant plugin list

if you are on fedora, then the vagrantfile seems to be trying to run parallels that is virtualization for macos

so please also confirm your host os.


alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/aa888df6-fc7b-43dd-b16b-e31c36068559%40googlegroups.com.


--
Alvaro

Reply all
Reply to author
Forward
0 new messages