As it stands today it’s getting a new MAC address from the host’s pool:
($vm | Get-VMNetworkAdapter).MacAddress 00155D16FCF Get-VMHost | fl Mac* MacAddressMaximum : 00155D016FFF MacAddressMinimum : 00155D016F00
Hyper-V does have a MAC parameter https://www.vagrantup.com/docs/hyperv/configuration.html#mac that could be used.
I added this to the Vagrantfile config.vm.provider "hyperv" do |hv| hv.mac = "52:54:00:f8:36:8f" hv.differencing_disk = true end
Once the VM boots, it still doesn’t get an IP. Ifconfig -a shows the right MAC address, but grepping dmesg for eth0 finds “udev: renamed network interface eth0 to eth1”. This is some time after hv_netvsc is loaded and has detected the right MAC.
Can you point me to the scripts used to build the boxes? I'd like to get an idea of what’s there so I can provide PRs or feedback as the Hyper-V provider improves.
Private networks & static IPs aren’t implemented yet in the Hyper-V provider. I’m hoping to implement it at some point but it will be a while before I’m able to get to it. https://github.com/mitchellh/vagrant/issues/8384#issuecomment-287570247
Cheers, Patrick
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Laurentiu Pancescumailto:lpancescu@gmail.com Sent: Tuesday, May 2, 2017 12:27 AM To: centos-devel@centos.orgmailto:centos-devel@centos.org Subject: Re: [CentOS-devel] Vagrant images for Hyper-V
On 01/05/17 05:37, Patrick Lang wrote:
Centos 6.1.1 - Vagrant didn't find an IP address upon bootup. I logged in via the console and the Hyper-V virtual NIC was on eth1 which didn't have dhclient configured. I ran dhclient manually, then vagrant ssh was able to find the IP
Patrick, would it be possible for you to check the MAC address of the NIC inside the Vagrant box? If you login in a console, "ip addr show dev eth1 scope link" should display it as "link/ether". It should be set to 52:54:00:f8:36:8f for our configuration to work properly. If the MAC happens to be another value like 00:15:5D:01:07:DC, which is the Image Factory default for MacAddress in the generated Hyper-V XML, eth0 would probably be renamed to eth1 - not 100% sure.
You could also try to add 'config.vm.base_mac = "5254008815b6"' to your Vagrantfile before booting the box for the first time (that's only documented for VirtualBox, no idea if it has any effect on Hyper-V boxes).
Thanks, Laurențiu _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel