Build 'virtualbox-iso' errored: Timeout waiting for WinRM #35
Comments
|
Yeah its a pretty terrible experience. Are you running with a gui? If it times out waiting for WinRM, it could be there was an error in the underlying box that you might be able t osee with the gui. However if you are like me, you may have gone to sleep only to wake up with that error message and a deleted VM. I believe there is a separate packer issue around preserving the VM when things go wrong. Another potential issue is that it just was not finished by the end of the timeout. The timeout is 8 hours which is usually adequate but may need to be extended if your host is extremely under resourced. I suspect its not bandwidth thats the issue but would be more likely RAM/Disk. The machine I run this on is my daughters old laptop with a busted monitor but works fine if I RDP to it. Its not that beefy (I5/6GB/HDD (not SSD)). |
|
currently im on an Ubuntu 14.04 host, which is an i7-something w/ 32GB of ram...I believe the VM is configured with 2 procs and 2GB of ram. SSD disk. I edited the packer json to extend the timeout to 16 hours. The error from last night did go away with packer's cleanup. The linux terminal said something about If it completes, I'll upload it to Azure. My ultimate plan is to apply a chef cookbook that installs vs2015 community and include a Vagrantfile in my OS project. |
|
Well thats certainly beefy enough :) I'd bet it didn't just timeout but there was an error in the setup but after 8 hours, packer timed out and it all went away. Extending the timeout is good since it should give you more time to see the real issue in the vbox gui. |
|
I am seeing the Timeout waiting for WinRM from my powershell session on my host. ==> virtualbox-iso: Downloading or copying Guest additions If I get on the virtualbox guest created with the vbox-2012r2.json file & type in winrm set winrm/config/service '@{AllowUnencrypted="True"}' it connects over winrm & progresses further. Is there anyway to inject this in somewhere along the packer build or in a config file somewhere that loads before needing WinRM |
|
The package script intentionally sets that property at the very end of the boxstarter run. If its done too early, packer will reboot the vm and then hands off the rest of the provisioning to the provisioner. When you see the above timeout, that usually means that either something went wrong in the boxstarter run or windows updates took too long. If you have a Virtualbox GUI up, you may be able to tell what is wrong by an error in the console or looking in the boxstarter log at |
|
Hi Matt Sorry . Iam facing the same issue of winrm getting timed out .Please suggest any solution in regards with this since I have been lingering on the step for nearly 2 days. I have also set the winrm timeout to 8 hrs but also the winrm is timing out. PS C:\Users\panugpr1\Desktop\chef-repo\packer-templates-master> .\packer.exe build -force -only virtualbox-iso vbox-2012r2.json ==> virtualbox-iso: Downloading or copying Guest additions ==> virtualbox-iso: Timeout waiting for WinRM. ==> Some builds didn't complete successfully and had errors: |
|
see my comment just above yours. If the run has been going over 8 hours and you have decent hardware, something went wrong and you need to check the boxstarter log or the vbox gui for errors. |
|
vbox gui doesnt show up any errors .I also cannot find the box starter.log file, is it present in the VM or my local worstation? |
|
its in the vm at $env:LocalAppData\boxstarter\boxstarter.log |
|
Hi Matt Below I am not able to see the log file.Below I am attaching my screenshot of the folder system check it once and guide me please |
|
you want c:\users\vagrant\appdata\local\boxstarter |
|
Hi Matt This is the screen shot of the last 20 line of the log.Can you please let me know the problem by looking at the log file. Because I am unable to diagnose the root cause or error |
|
Hi matt please reply to the above thread.Please let me know the problem |
|
looks like something went wrong further up. you could include a link to a gist of the whole thing. |
|
oh gosh My entire vm got deleted now. and I wont be able to trace out the boxstarter.log.Could you suggest me any other method for building a windowsr2012 box for setting up a test kitchen instance. |
|
oh...I know that pain. You can always use mwrock/Windows2012R2 which is built from this template and I keep it pretty current. |
|
fwiw, I set the timeout to 16 hours, ran the script on my laptop, and worked on other things, watching it. I got it to work, but i remember having to hit enter at a prompt for something. |
|
yeah. a prompt would definitely be a bug. |
|
Same here, 8h later it just killed everything off. I have the latest MacBook Pro machine with 16 cores and 16 GiB memory and the top-of-the-line SSD that I think can write 600 MiB/s. It's not about being underspecced. The my internet connection is 1000/1000 to the internet (and 300 mbps WiFi that caps out at 296 mbps in real life, because who wants cables to a MacBook Pro?). To the contrary, I think it's a lot about network latency to MSFT servers and how it chooses to install its security updates (staged download-install-then-download-again). Is it possible to use one of the batch security update ISOs, you think? |
|
Is there any way to get the boxstarter log when the VM is stuck at the following window?
|
|
The log can be found in Its likely not going to have anything helpful. The call to windows update and check updates, especially on a clean win 7 VM can take a very long time. |
|
Just a data point I am still getting this bug hashicorp/packer#3652 so hopefully next release of packer will address this |
|
This is what I'm seeing when I open up the GUI. Its going through a ton of updates. I'll increase the timeout and see if its done then.
|
Hi Matt,
Thanks for the awesome work on packer and boxstarter! I am running the packer-template for 2012r2 to get a current 90 day license. I left it running last night, but it errored out waiting on all the windows patching.
I'm in Seattle on Comcast 100mbps...is it possible to cache any of those window patches? Do I have any other options to get this to complete? I'm re-running now...
-Jimmy
The text was updated successfully, but these errors were encountered: