I would expect that it should only attempt to use the communicator type you have configured. In your example, which communicator type are you using, SSH or WinRM?
On Monday, June 2, 2014 3:12:22 PM UTC-7, Ben Hines wrote: > > When using 'vagrant package' to package a windows vm which is running in > Virtualbox vagrant force > shuts down the VM. > > It should check for/ try to use WinRM to shut down the vm (as well as ssh) > if it detects a windows vm. > > This is a vm which was spun up by vagrant, and i'm attempting to repackage > it as a basebox: > > [bhines@sm-bhines-764:[~/ > Documents/Code/sms/vagrant] [0]$ vagrant package --base > vagrant_recap_1401745583866_68047 > ==> vagrant_recap_1401745583866_68047: Attempting graceful shutdown of > VM... > vagrant_recap_1401745583866_68047: Guest communication could not be > established! This is usually because > vagrant_recap_1401745583866_68047: SSH is not running, the > authentication information was changed, > vagrant_recap_1401745583866_68047: or some other networking issue. > Vagrant will force halt, if > vagrant_recap_1401745583866_68047: capable. > ==> vagrant_recap_1401745583866_68047: Forcing shutdown of VM... > ==> vagrant_recap_1401745583866_68047: Clearing any previously set > forwarded ports... > ==> vagrant_recap_1401745583866_68047: Exporting VM... > > -Ben > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
