On Jan 19, 2010, at 11:26 AM, David Edmondson wrote: > * [email protected] [2010-01-19 15:43:58] >> I created a DomU with a dedicated network connection >> >> script path='/usr/lib/xen/scripts/vif-dedicated' >> >> Having run the virtual machine I now destroy the domain, undefine it, >> change the script to >> >> script path='/usr/lib/xen/scripts/vif-vnic' >> >> define the domain and try to start it. This fails. If I change the >> assigned MAC address the newly defined virtual machine works. >> >> Bit of a b****r though as our central IT guys keep a MAC/IP register and >> I get annoying e-mails because the new MAC/IP relationship isn't logged. >> >> Any way to flush what is obviously a cached MAC address from Dom0 without >> a reboot? > > I'd guess that the MAC address you used has been set as the primary > address of the physical NIC that you dedicated (dladm show-phys -m). If > you change the primary address of the physical NIC (using 'ifconfig foo0 > ether xx:xx:xx:xx:xx:xx') it should be possible to create a VNIC which > uses that address.
I contend that you should *not* assign a "physical" mac address to a virtual nic. It will cause you problems later. For a very temporary hack, its possible, but I really don't recommend it. Chalk it up to experience, always use vnic, always. You can put one vnic per physical interface if you want "dedicated" and you can always track and assign your "virtual" mac address (starts virtual prefix 0000 0010), no matter what physical machine you happen to use. You can assign a mac address, but at least start it with "2:" Tommy > >> I'd like to keep the old MAC address as we use the last 2 numbers >> of the IP address to form the last 4 digits of the MAC. > > dme. > -- > David Edmondson, Sun Microsystems, http://dme.org > _______________________________________________ > xen-discuss mailing list > [email protected] _______________________________________________ xen-discuss mailing list [email protected]
