WinRM doesn't require SSH on the guest, they're both independent
communication channels. Windows guest drive mapping on VirtualBox, VMWare,
and Parallels uses their native shared folders implementation. For EC2
obviously this won't work.
I'd like to see EC2/Vagrant/WinRM work, but at this point I'm not sure how.
On Wednesday, June 18, 2014 1:33:13 AM UTC-7, Espen wrote:
>
> Using Vagrant 1.6.3, I am trying to provision software to a EC2 Windows
> 2012 R2, Amazon provided, guest OS. However this is proving to be quite an
> undertaking, mostly due to my inexperience with the technology I assume. My
> problem is that things stop working on the folder sync stage, and I am
> unsure what mechanisms are supposed to be providing this in my setup.
>
> Here is what I have (Vagrantfile):
>
> # Vagrantfile API/syntax version. Don't touch unless you know what you're
> doing!
> VAGRANTFILE_API_VERSION = "2"
>
>
> Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
> config.vm.box = "dummy"
> config.vm.communicator = "winrm"
> config.winrm.username = "Administrator"
> config.winrm.password = "-removed-"
>
> config.vm.provider :aws do |aws, override|
>
> aws.user_data = File.read("user_data.txt")
>
> aws.access_key_id = "-removed-"
> aws.secret_access_key = "-removed-"
> aws.keypair_name = "sml_qa_key"
>
> override.vm.communicator = "winrm"
>
> aws.ami = "ami-27539050"
> aws.region = "eu-west-1"
> aws.instance_type = "m3.medium"
> aws.security_groups = ["sml-qa"]
>
> end
>
> config.vm.provision "chef_solo" do |chef|
> chef.add_recipe "git"
> end
> end
>
> My user_data file handles the winrm setup and firewall settings, and adds
> chocolatey to the Guest OS (Windows). I am using Linux and Mac on my end.
> WinRM connects fine with the box. Hoever, folder syncing fails, and my
> vm.provisioning stage stops:
>
> Rsyncing folder: /exthome/etj/develop/source/slm/qa_environment/ =>
> /vagrant
> vagr...@xx.xx.71.1's password:
> There was an error when attempting to rsync a share folder.
> Please inspect the error message below for more info.
>
> Host path: /exthome/etj/develop/source/slm/qa_environment/
> Guest path: /vagrant
> Error: Warning: Permanently added 'XX.XX.71.1' (DSA) to the list of known
> hosts.
> Write failed: Broken pipe
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: unexplained error (code 255) at io.c(605) [sender=3.0.9]
>
> My questions are:
> 1. Do I need to have a SSHD (SSH server setup on the Windows Guest) in
> order to use Vagrant 1.6.3 with winrm (this is unclear in the
> documentation).
> 2. If yes, how should the ssh-key transfer be handled so that I can
> utilize SSH keys with my Administrator account that has already been
> created on Amazon EC2 (and reside in my local vagrant catalog (the one
> where Vagrantfile lives).
>
> Any insights would be very much appreciated.
>
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
