Hi all,
I''m trying to automate my xen setup by scripts. For my xen setup I have
two prerequisites:
1. I can''t determine the sequence the domUs are started
2. I need network reconfiguration on the fly
So, if I wanna reconfigre domU_a on the fly I have to:
1. edit domU_a''s config file and change the network stuff
(at next reboot the network stuff is set up correctly)
2. reconfigure some tap and/or bridge device(s)
(to avoid a unnecessary reboot)
Ok, as I defined my prerequisites I''ve checked Xen''s
behaviour:
xm create domU_a => tap0 created in dom0
xm create domU_b => tap1 created in dom0
xm shutdown domU_a
xm shutdown domU_b
xm create domU_b => tap0 created in dom0
xm create domU_a => tap1 created in dom0
As you can see, the tap devices swapped their names. What should be done
to avoid this naming convention?
Goran
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Sun, Jun 28, 2009 at 7:51 PM, Goran<xen-list@arcor.de> wrote:> xm create domU_b => tap0 created in dom0 > xm create domU_a => tap1 created in dom0 > > As you can see, the tap devices swapped their names. What should be done > to avoid this naming convention?That''s the thing with tap. The bad news, there''s no method that I know of that can easily make HVM domU''s tap names "persistent". The good news, depending on how you use domU, that might not matter. You see, if you use PV drivers (like GPLPV for Windows domU) traffic will go through the vif. And you can change vif name easily. Try "xm create --help_config | grep vif" -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users