On 04/25/11 11:30, Alex Williamson wrote: > So yes, it does change. However, if I set the VF mac instead of using a > randomly generated one, I get: > > # modprobe -r igbvf > # ip link set eth2 vf 6 mac 02:00:10:91:73:01 > # modprobe igbvf > # dmesg | grep "igbvf 0000\:01\:11.5\: Address\:" > igbvf 0000:01:11.5: Address: d2:c8:17:d6:97:f7 > igbvf 0000:01:11.5: Address: 4e:ee:2a:d8:12:7c > igbvf 0000:01:11.5: Address: 02:00:10:91:73:01 > # modprobe -r igbvf > # echo 1 > /sys/bus/pci/devices/0000:01:11.5/reset > # modprobe igbvf > # dmesg | grep "igbvf 0000\:01\:11.5\: Address\:" > igbvf 0000:01:11.5: Address: d2:c8:17:d6:97:f7 > igbvf 0000:01:11.5: Address: 4e:ee:2a:d8:12:7c > igbvf 0000:01:11.5: Address: 02:00:10:91:73:01 > igbvf 0000:01:11.5: Address: 02:00:10:91:73:01 > > So now it sticks. You're going to get random mac addresses on the VFs > every time you reload the igb driver (ie. ever boot) anyway (at least > with these sr-iov cards), so if you need consistent macs, they probably > need to be set before launching the VM anyway. Thanks, You lost me on this. I do not have the igbvf driver loaded in the host, only the guest. I am setting the MAC address for the VF in the host before launching the VM. The host's igb driver gets loaded at boot only. David > > Alex > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
