Hello all, I did some tests with DomU live migration and it worked quite well :-) However, there remains one question: Is it possible to (reliably) get programatically aware of the DomU''s ID on the host it is migrated to? Could anybody give me a hint how the NIC frontends are created and configured after migration, e.g., are the network scripts called or is a different mechanism invoked? Regards, dla _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > mail4dla@googlemail.com > Sent: 13 June 2007 17:08 > To: xen-users@lists.xensource.com > Subject: [Xen-users] DomU after migration > > Hello all, > > I did some tests with DomU live migration and it worked quite well :-) > However, there remains one question: Is it possible to > (reliably) get programatically aware of the DomU''s ID on the > host it is migrated to?You mean besides logging into the Dom0 of the new machine and parsing the output of "xm list" or similar? Not sure that there is any easy way to do this.> Could anybody give me a hint how the NIC frontends are > created and configured after migration, e.g., are the network > scripts called or is a different mechanism invoked?As far as I know, in PV-domains, it works by sending some new ARP messages to the network, and that will make any switches/routers realize that there is a new location for the IP address of the migrated domain. Not entirely sure how it works on HVM domain. -- Mats> > Regards, > dla > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, that''s fast... On 6/13/07, Petersson, Mats <Mats.Petersson@amd.com> wrote:> > You mean besides logging into the Dom0 of the new machine and parsing > the output of "xm list" or similar? Not sure that there is any easy way > to do this.Exactly. Well, then I''ll have to resort to parsing. Shouldn''t be to bad as the domain name is guaranteed to be unique, isn''t it?> Could anybody give me a hint how the NIC frontends are > > created and configured after migration, e.g., are the network > > scripts called or is a different mechanism invoked? > > As far as I know, in PV-domains, it works by sending some new ARP > messages to the network, and that will make any switches/routers realize > that there is a new location for the IP address of the migrated domain. > > Not entirely sure how it works on HVM domain.Well, in my setup, this doesn''t work reliably, but this currently is no issue for me (so I did not dig into it yet to find out whether it is my fault or Xen''s). However, this is not what I am curious to know: How does Xen determine to which bridge the vifX.Y has to be connected and is there a way to influence this, e.g., if the bridges are named differently on the remote system? dla _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users