Hello, Can someone please verify if my understanding is correct. In regards to live migration of a domain across systems with different networking devices, for example, if I have a source dom0 with e1000g0 on 192.9.100.0/24 LAN e1000g1 on 192.9.101.0/24 LAN And I have a domain I want to migrate to a dom0 that perhaps has nge0 on 192.9.100.0/24 LAN nge1 on 192.9.101.0/24 LAN I cannot expect simply doing a "virsh migrate --live domain xen:/// xenmigr://target" to do the right thing and assign the bridges to the right interfaces. Instead, I am assuming I would have to do something like dump the domain config manually (with virsh dumpxml domain), tweak the bridge configs manually to reference nge0 and nge1 instead of e1000g1 and e1000g1, then import the config into the target, before issuing the "virsh migrate ..." command. Is this correct? --joe
Joseph Mocker wrote:> Hello, > > Can someone please verify if my understanding is correct. > > In regards to live migration of a domain across systems with different > networking devices, for example, if I have a source dom0 with > > e1000g0 on 192.9.100.0/24 LAN > e1000g1 on 192.9.101.0/24 LAN > > And I have a domain I want to migrate to a dom0 that perhaps has > > nge0 on 192.9.100.0/24 LAN > nge1 on 192.9.101.0/24 LAN > > I cannot expect simply doing a "virsh migrate --live domain xen:/// > xenmigr://target" to do the right thing and assign the bridges to the > right interfaces.depends :-) If you have something simple where you always want to go from xend property ''config/default-nic'' to ''config/default-nic'' then yes it will work. If you have multiple guests which use different nics then no.> Instead, I am assuming I would have to do something like dump the domain > config manually (with virsh dumpxml domain), tweak the bridge configs > manually to reference nge0 and nge1 instead of e1000g1 and e1000g1, then > import the config into the target, before issuing the "virsh migrate > ..." command. > > Is this correct?No, there are better ways... One is if you have a relatively current version of solaris, you can use vanity naming.. e.g. dladm rename-link e1000g0 lan100 dladm rename-link e1000g1 lan101 dladm rename-link nge0 lan100 dladm rename-link nge1 lan101 MRJ
Mark Johnson wrote:> > depends :-) > > If you have something simple where you always want to > go from xend property ''config/default-nic'' to > ''config/default-nic'' then yes it will work. > > If you have multiple guests which use different > nics then no. > > > >> Instead, I am assuming I would have to do something like dump the >> domain config manually (with virsh dumpxml domain), tweak the bridge >> configs manually to reference nge0 and nge1 instead of e1000g1 and >> e1000g1, then import the config into the target, before issuing the >> "virsh migrate ..." command. >> >> Is this correct? > > No, there are better ways... One is if you have a > relatively current version of solaris, you can use > vanity naming.. e.g. > > dladm rename-link e1000g0 lan100 > dladm rename-link e1000g1 lan101 > > dladm rename-link nge0 lan100 > dladm rename-link nge1 lan101Sweet stuff. Very handy. God I love Solaris! Thanks. --joe