From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: remoted migration KVM-guest failed Date: Wed, 25 Jul 2007 08:35:12 -0500 Message-ID: <46A75190.7050904@codemonkey.ws> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0465367156==" Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: "Zhang, Jingke" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org --===============0465367156== Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Zhang, Jingke wrote: > Hi Anthony, > My KVM-version is: =20 > Kernel: b41e5014dd8712e8de2b656617f7a7a158cd992a > Userspace: 86e8eba8f8349d2e02e3b0ae0ce7c1993f4352fb > This is the latest commit which is built at 2007-07-24 by us. And t= here is no any extra patch. We can do remote migration successfully befor= e, but failed this time. I am sure that machine A and B can ping each oth= er successfully. > BTW, the method of migrate "exec://dd of=3Dfoo.img" is to save the = KVM-guest, and we restore it. I guess the live migration for KVM is diffe= rent from that. =20 > =20 It's almost exactly the same code path. If you can reproduce with an "exec://" URL, then that gives us an easy way to reproduce and we can examine the traffic by hand to see what went wrong. If you cannot reproduce with an exec:// URL, it suggests that the bug your seeing is part of the tcp:// URI handling code (and there's not a lot of that). Regards, Anthony Liguori > Thank you. > > > > > -----Original Message----- > From: Anthony Liguori [mailto:anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org]=20 > Sent: 2007=C4=EA7=D4=C225=C8=D5 11:20 > To: Zhang, Jingke > Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > Subject: Re: [kvm-devel] remoted migration KVM-guest failed > > Zhang, Jingke wrote: > =20 >> Hi all, >> >> I test the migration in KVM-ia32e (using two machines to do remote=20 >> migration), but it failed. >> >> But if I do it in the local host, it can pass. Does anyone meet the=20 >> same issue? Please give me some help, thank you very much! >> >> The command I used on the destination (machine B) point is: >> >> qemu-system-x86_64 . -m 512 -net=20 >> nic,macaddr=3D00:16:3e:3a:2d:56,model=3Drtl8139 -net=20 >> tap,script=3D/etc/kvm/qemu-ifup -hda /root/hvm/ia32e_fc6.img =A8Cincom= ing=20 >> tcp://0:4444 >> >> The command I used on the source (machine A) point is: >> >> qemu-system-x86_64 . -m 512 -net=20 >> nic,macaddr=3D00:16:3e:3a:2d:56,model=3Drtl8139 -net=20 >> tap,script=3D/etc/kvm/qemu-ifup -hda /root/hvm/ia32e_fc6.img and (qemu= )=20 >> migrate =A8Cd tcp://192.168.199.69:4444 >> >> Then the (machine B) shows errors: >> >> Migrate_incoming_fd failed (rc=3D233) >> >> Migration failed rc=3D233 >> >> =20 > > Curious, it indicates that the migration stream is corrupted. Can you d= o=20 > something like: > > On machine A: > > (qemu) migrate "exec://dd of=3Dfoo.img" > > And then on machine B: > > cat foo.img | qemu-system-x86_64 . -m 512 -net=20 > nic,macaddr=3D00:16:3e:3a:2d:56,model=3Drtl8139 -net=20 > tap,script=3D/etc/kvm/qemu-ifup -hda /root/hvm/ia32e_fc6.img =A8Cincomi= ng stdio > > What version of KVM is this? Are there any patches applied? > > Regards, > > Anthony Liguori > > =20 >> BTW, dmesg on machine B shows: >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >> sw0: port 2(tap0) entering disabled state >> >> device tap0 left promiscuous mode >> >> sw0: port 2(tap0) entering disabled state >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >> Thank you, Zhangjingke >> >> ----------------------------------------------------------------------= -- >> >> ----------------------------------------------------------------------= --- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser= . >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> ----------------------------------------------------------------------= -- >> >> _______________________________________________ >> kvm-devel mailing list >> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org >> https://lists.sourceforge.net/lists/listinfo/kvm-devel >> =20 >> =20 > > =20 --===============0465367156== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ --===============0465367156== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kvm-devel mailing list kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/kvm-devel --===============0465367156==--