Hello, I'm wondering if any of u encountered the problem. When I'm putting: vif = [ ' bridge=xenbr0' ] in the config file, every restart of the virtual machine, the mac address is changed. Because of that, I get, eth0 after first run, then eth1 (with no eth0), then eth2... and so on. That is not good. The problem is solvable via setting the MAC explicitly in the vif syntax, but that is not comfortable while doing a lot of new machines often. So, any help on the first solution? Thanks! -- Radosław Antoniuk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Apr 05, 2007 at 11:11:48AM +0200, Radek Antoniuk wrote:> When I''m putting: > vif = [ '' bridge=xenbr0'' ] > in the config file, every restart of the virtual machine, the mac > address is changed. Because of that, I get, eth0 after first run, then > eth1 (with no eth0), then eth2... and so on. > That is not good.It''s because of udev, creating persistent device names based on MAC address. And the solution is:> The problem is solvable via setting the MAC explicitly in the vif > syntax, but that is not comfortable while doing a lot of new machines > often.Why are you not comfortable with this? I generally find it essential for management purposes that each domain has a stable MAC address that is used by it and only it. Cheers, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andy Smith wrote:> On Thu, Apr 05, 2007 at 11:11:48AM +0200, Radek Antoniuk wrote: > >> When I''m putting: >> vif = [ '' bridge=xenbr0'' ] >> in the config file, every restart of the virtual machine, the mac >> address is changed. Because of that, I get, eth0 after first run, then >> eth1 (with no eth0), then eth2... and so on. >> That is not good. >> > > It''s because of udev, creating persistent device names based on > MAC address. > > And the solution is: > >> The problem is solvable via setting the MAC explicitly in the vif >> syntax, but that is not comfortable while doing a lot of new machines >> often. >> > > Why are you not comfortable with this? I generally find it > essential for management purposes that each domain has a stable MAC > address that is used by it and only it. > > Cheers, > Andy >Agreed. And it''s easy to assing a MAC address range to each Xen Dom0 server to allocate for its DomU''s, so when you see some spewiing cient in the logs or on a switch you have some idea what the heck it is. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users