Jim, That was it! I didn't realize there was some significance of certain bits within the address. Changing that first byte resolved the issue. Should I be setting the 2nd bit in the LSB to 1? I started logging into all the systems I have access to and realized all of them have 00 as the first byte in the address. Should I just stick to 00 on all mine? Or by making that 2nd bit 1, does that force the card to inherit an address from libvirt or somewhere else instead of the VM configuration? I'll play around with it some more, but at least that mystery is solved. BTW, was the first time posting on this list and love it! Quickest response I've ever gotten on a mailing list. :) Thanks! Ken On Wed, Mar 11, 2009 at 11:28 PM, Jim Paris <jim@xxxxxxxx> wrote: > Ken Robertson wrote: >> Hoping someone can help me track down an issue I'm experiencing on a >> KVM machine I built recently. > ... >> SIOCSIFFLAGS: Cannot assign requested address >> >> The address isn't in use or anything, so no reason I can think of why >> it can't assign it. It recognizes the device, however can't bring it >> up. All the VMs have unique MAC addresses, randomly generated. One >> of the ones that doesn't work is using 93:01:dc:a0:f0:57. > > That MAC address is not valid. The LSB of the first byte should be 0 to > indicate unicast, and the second LSB of the first byte should be 1 to > indicate a locally-assigned address. e.g. 92:01:dc:a0:f0:57 should > work. > > -jim > > > > -- 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
