geerlingguy / geerlingguy/ansible-for-devops
Guest Additions, should we be concerned about version differences?
- Dominant language
- Python
- Stars
- 9.9k
- Forks
- 3.8k
- PR merge metrics
- No merged PRs in 30d
Description
I found an Intel based Mac and got by #510. Then I got it with #506. Now I'm getting the following errors. If guest additions matter, suggestions on how properly configure them? (or avoid them all together if that's my problem.)
Except for adding `virtualbox__intnet: true` to the end of each private network config line, I've only copied and pasted the Vagrantfile code from Ch3.
```
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 6.1.32
VBoxService inside the vm claims: 7.0.2
Going on, assuming VBoxService is correct...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 6.1.32
VBoxService inside the vm claims: 7.0.2
Going on, assuming VBoxService is correct...
Got different reports about installed GuestAdditions version:
Virtualbox on your host claims: 6.1.32
VBoxService inside the vm claims: 7.0.2
Going on, assuming VBoxService is correct...
Restarting VM to apply changes...
==> db: Attempting graceful shutdown of VM...
==> db: Booting VM...
==> db: Waiting for machine to boot. This may take a few minutes...
==> db: Machine booted and ready!
==> db: Checking for guest additions in VM...
db: No guest additions were detected on the base box for this VM! Guest
db: additions are required for forwarded ports, shared folders, host only
db: networking, and more. If SSH fails on this machine, please install
db: the guest additions and repackage the box to continue.
db:
db: This is not an error message; everything may continue to work properly,
db: in which case you may ignore this message.
==> db: Setting hostname...
==> db: Configuring and enabling network interfaces...
(base) name@C02NX7BWG3QD ch3 % ansible multi -a "hostname"
192.168.60.4 | UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh: ssh: connect to host 192.168.60.4 port 22: Operation timed out",
"unreachable": true
}
192.168.60.5 | UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh: ssh: connect to host 192.168.60.5 port 22: Operation timed out",
"unreachable": true
}
192.168.60.6 | UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh: ssh: connect to host 192.168.60.6 port 22: Operation timed out",
"unreachable": true
}
```
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.