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

Guest Additions, should we be concerned about version differences? #511

Open
blue928 opened this issue Nov 13, 2022 · 0 comments
Open

Guest Additions, should we be concerned about version differences? #511

blue928 opened this issue Nov 13, 2022 · 0 comments

Comments

@blue928
Copy link

blue928 commented Nov 13, 2022

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
}
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