Eric
2012-Nov-01 21:26 UTC
xm migrate - Error: can''t connect: [Errno 111] Connection refused
When I attempt to migrate a VM from one host to another (sles-xen-2 -> sles-xen-1) I get the error message:> sles-xen-2:~ # xm migrate --live SLES-11-SP2-1 192.168.1.3 > Error: can''t connect: [Errno 111] Connection refused > ...What might be the problem? FWIW: I''ve already verified that iptables rules have been cleared and that xend does not have any ports open on the recieving host:> sles-xen-1:~ # ifconfig bond0 > bond0 Link encap:Ethernet HWaddr 00:30:48:87:22:C8 > inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 > ...> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 > > sles-xen-1:~ # iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination >> sles-xen-1:~ # netstat -tanp | grep xen >Eric Pretorious Truckee, CA
Alexandre
2012-Nov-02 11:44 UTC
Re: xm migrate - Error: can''t connect: [Errno 111] Connection refused
I think by default xend only binds the relocation service on the loopback interface. You can check this using netstat on the target dom0. regrads. 2012/11/1 Eric <epretorious@yahoo.com>> When I attempt to migrate a VM from one host to another (sles-xen-2 -> > sles-xen-1) I get the error message: > > > > sles-xen-2:~ # xm migrate --live SLES-11-SP2-1 192.168.1.3 > > Error: can''t connect: [Errno 111] Connection refused > > ... > > What might be the problem? FWIW: I''ve already verified that iptables rules > have been cleared and that xend does not have any ports open on the > recieving host: > > > sles-xen-1:~ # ifconfig bond0 > > bond0 Link encap:Ethernet HWaddr 00:30:48:87:22:C8 > > inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 > > ... > > > UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 > > > > sles-xen-1:~ # iptables -L > > Chain INPUT (policy ACCEPT) > > target prot opt source destination > > > > Chain FORWARD (policy ACCEPT) > > target prot opt source destination > > > > Chain OUTPUT (policy ACCEPT) > > target prot opt source destination > > > > > sles-xen-1:~ # netstat -tanp | grep xen > > > > Eric Pretorious > Truckee, CA > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Wardzinski, Todd
2012-Nov-02 13:56 UTC
Re: xm migrate - Error: can''t connect: [Errno 111] Connection refused
I believe this has to deal with the exchange of SSH keys, or, configuring Xen to accept connections on specific ports. As for configuring Xen, here''s a good reference: http://www.virtuatopia.com/index.php/Migrating_Xen_domainU_Guests_Between_Host_Systems. -----Original Message----- From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Eric Sent: Thursday, November 01, 2012 5:27 PM To: xen-users@lists.xen.org Subject: [Xen-users] xm migrate - Error: can''t connect: [Errno 111] Connection refused When I attempt to migrate a VM from one host to another (sles-xen-2 -> sles-xen-1) I get the error message:> sles-xen-2:~ # xm migrate --live SLES-11-SP2-1 192.168.1.3 > Error: can''t connect: [Errno 111] Connection refused ...What might be the problem? FWIW: I''ve already verified that iptables rules have been cleared and that xend does not have any ports open on the recieving host:> sles-xen-1:~ # ifconfig bond0 > bond0 Link encap:Ethernet HWaddr 00:30:48:87:22:C8 > inet addr:192.168.1.3 Bcast:192.168.1.255 >Mask:255.255.255.0 > ...> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 > > sles-xen-1:~ # iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination >> sles-xen-1:~ # netstat -tanp | grep xen >Eric Pretorious Truckee, CA _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Eric
2012-Nov-19 06:36 UTC
Re: xm migrate - Error: can''t connect: [Errno 111] Connection refused
Thanks, Todd: Ultimately, I found the answer in Section 9.3 of the the SLES 11 Virtualization with Xen Administration Guide (i.e., setting the configuration options [correctly] in /etc/xen/xend-config.sxp resolved the problem). Eric Pretorious Truckee, CA>________________________________ > From: "Wardzinski, Todd" <todd.wardzinski@progeny.net> >To: Eric <epretorious@yahoo.com>; "xen-users@lists.xen.org" <xen-users@lists.xen.org> >Sent: Friday, November 2, 2012 6:56 AM >Subject: RE: [Xen-users] xm migrate - Error: can''t connect: [Errno 111] Connection refused > >I believe this has to deal with the exchange of SSH keys, or, configuring Xen to accept connections on specific ports. > >As for configuring Xen, here''s a good reference: http://www.virtuatopia.com/index.php/Migrating_Xen_domainU_Guests_Between_Host_Systems. > > >-----Original Message----- >From: xen-users-bounces@lists.xen.org [mailto:xen-users-bounces@lists.xen.org] On Behalf Of Eric >Sent: Thursday, November 01, 2012 5:27 PM >To: xen-users@lists.xen.org >Subject: [Xen-users] xm migrate - Error: can''t connect: [Errno 111] Connection refused > >When I attempt to migrate a VM from one host to another (sles-xen-2 -> sles-xen-1) I get the error message: > > >> sles-xen-2:~ # xm migrate --live SLES-11-SP2-1 192.168.1.3 >> Error: can''t connect: [Errno 111] Connection refused ... > >What might be the problem? FWIW: I''ve already verified that iptables rules have been cleared and that xend does not have any ports open on the recieving host: > >> sles-xen-1:~ # ifconfig bond0 >> bond0 Link encap:Ethernet HWaddr 00:30:48:87:22:C8 >> inet addr:192.168.1.3 Bcast:192.168.1.255 >>Mask:255.255.255.0 >> ... > >> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 >> >> sles-xen-1:~ # iptables -L >> Chain INPUT (policy ACCEPT) >> target prot opt source destination >> >> Chain FORWARD (policy ACCEPT) >> target prot opt source destination >> >> Chain OUTPUT (policy ACCEPT) >> target prot opt source destination >> > >> sles-xen-1:~ # netstat -tanp | grep xen >> > >Eric Pretorious >Truckee, CA > > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xen.org >http://lists.xen.org/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users