-
Notifications
You must be signed in to change notification settings - Fork 498
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
Error bringing up box with qemu:///session - Guest Specific Operations #1782
Comments
according to the logfile the virtual machine is defined and starting up. The vagrant-libvirt plugin itself seems to work correctly. It also detects that the virtual machine has been assigned an IP address and attempts to reach it via SSH, but fails to do so:
you should check if the virtual machine in fact did boot up correctly and is reachable via SSH (via VNC console |
When running vagrant up, I'm getting the following error:
Guest-specific operations were attempted on a machine that is not ready for guest communication. This should not happen and a bug should be reported.
This only happens when I set
libvirt.uri = "qemu:///session"
, not when I uselibvirt.uri = "qemu:///system"
To Reproduce
Steps to reproduce the behavior:
libvirt.uri = "qemu:///session"
vagrant up
I tried building and using the latest on development, still have the same issue. I'm not sure if it's vagrant-libvirt or something wrong with my environment.
Versions (please complete the following information)::
vagrant version
]: vagrant 2.3.7, also tried 2.3.6 and 2.3.0vagrant plugin list
]:Debug Log
vagrant.log
A Vagrantfile to reproduce the issue:
The text was updated successfully, but these errors were encountered: