Ok. So I followed the instructions in that link as far as I can tell. They didn't seem to affect anything. I did notice however that the vm's I made needed a service network restart before things like ping or yum would work as well as a change to eth0 to set onboot to yes if I didn't want to restart every time. I also noticed that even after the network restart, if I changed from the Default Switch that the vm wouldn't be connected. I tried to purposely set the json to use Default Switch, since the default behavior seems for the process to make a new switch, but it doesn't seem to like Default Switch being 2 words. Any advice?
On Monday, February 25, 2019 at 11:09:27 AM UTC-5, Megan Marsh wrote: > > Can your HyperV vm reach the internet? When I've had frustrating boot > failures with KS files it's because the vm can't find the files that Packer > is serving. Check out this resource on configuring the network: > https://www.groovypost.com/howto/share-an-ethernet-or-wireless-network-connection-with-hyper-v-in-windows-10/ > > . tl;dr is that you need to go to the control panel's network and sharing > center and make sure that the eth0 adpater is sharing internet with your > hyper-v adapter. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/453623dc-273c-4897-bf65-63cff52a11eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
