waiting forever on this message "==> hyperv-iso: Configuring ip address..."

[vvchik]

waiting forever on this message "==> hyperv-iso: Configuring ip address..."

[vvchik]

sorry not forever, after around 2 hours
received following messages:
Build 'hyperv-iso' errored: Error configuring ip address: IP address assigned to the adapter is empty

==> Some builds didn't complete successfully and had errors:
--> hyperv-iso: Error configuring ip address: IP address assigned to the adapter
is empty

==> Builds finished but no artifacts were created.

[pbolduc]

Sorry, about that. I had increased the hard coded timeout while troubleshooting a powershell remoting issue. What guest OS are you using? Older versions of Windows require an update of the Integration Services before they will report their IP address to the HyperV host. I have a step under development to update the integration services automatically, but I have been busy.

The current committed code should work properly with Windows 2012 R2 and Windows 8.1 Enterprise. In the mean time, you could comment out lines 251 - 258 in builder.go. You may need to uncomment 248-251 in builder.go to add a delay before packer starts provisioning.

[vvchik]

Yes, I try to build windows 2008r2,
and after manual install of integration services and reboot everything finished ok. will research to add this step to automated install? thanks.

[pbolduc]

I have a step to mount the integration services disk as a second dvd. With that, the user can run the silent version of the setup via a bat/cmd script. However, the step commented out cause it was crashing. It is the next thing on my to do list. I hope to get some time this weekend to resolve this.

Things on the backlog:

• mount Integration Services as 2nd DVD drive and remove dvd drive after install but before exporting VM
• add a cmd script to the examples that updates integration services
• be able to update autounattend.xml with product key if provided
• remove hard coded vagrant/vagrant username/password in steps (this should be configurable)
• support linux os - this will require optionally loading steps if linux, this will require adding an optional config value for guest os.

[vvchik]

Good list! It will be very useful.
I created script that take vmguest.iso unpack it via 7zip and install integration services. And for now everything works good for me. Absolutely automatically. Big thanks for your help!

[pbolduc]

I would be interested if you have any special use cases or requirements. I also what to be able to update windows using WSUS Offline Update. That tool can create an ISO with almost all the Windows Updates for each OS and install them fully unattended. This is a lot faster than downloading them!

[vvchik]

it is very great idea, because now i installing updates via Autounattend.xml as part of image creation and it takes a looong time

[pbolduc]

I have found that PowerShell remoting is tricky to get working. I was just testing with Windows Server 2008 R2 and the scripts I use to configure PowerShell remoting are causing problems. The reason I was looking at using PowerShell remoting is for the communicator. At this point there is two options for communicator:

1. Use PowerShell remoting
   • only works reliably with newer versions of Windows. Older versions of Windows would require updates to PowerShell version, etc
2. Use SSH like other providers
   • would require downloading or having an ISO with install media available
   • could be undesirable to have SSH installed in certain circumstances

I want to be able to support both via configuration. If no configuration specified, It could also use convention if Windows Version < X or non-Windows, use SSH, otherwise use PowerShell remoting.