From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Yang, Sheng" Subject: Re: KVM Migration fails Date: Thu, 25 Sep 2008 14:23:49 +0800 Message-ID: <200809251423.49931.sheng.yang@intel.com> References: <192897.95216.qm@web35803.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org, "jdsw2002@yahoo.com" Return-path: Received: from mga03.intel.com ([143.182.124.21]:43214 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751401AbYIYGXL (ORCPT ); Thu, 25 Sep 2008 02:23:11 -0400 In-Reply-To: <192897.95216.qm@web35803.mail.mud.yahoo.com> Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: On Thursday 25 September 2008 12:22:42 jd wrote: > Hi > I have a setup using shared nfs disks. When migration is attempted, it > fails... any ideas on how to debug this..? It's a regression bug recently. Please refer to https://sourceforge.net/tracker/index.php?func=detail&aid=2106661&group_id=180599&atid=893831 I think a git bisect can also help. -- regards Yang, Sheng > > /Jd > > Details > ======= > > migration: write failed (Connection reset by peer)^M > Migration failed! ret=0 error=9 > > Source : KVM-73, Cent OS 5.2, 64 bit. > > qemu-system-x86_64 -net nic,vlan=0,macaddr=00:16:3e:16:f4:f0 -net > user,vlan=0 -hda /mnt/nfs/vmdisks/XPSP2-KVM.disk.xm -boot c -m 1024 > -no-acpi -vnc :22 -name XPSP2-KVM -smp 2 -monitor > unix:/var/run/kvm/monitors/XPSP2-KVM,server,nowait -pidfile > /var/run/kvm/pids/XPSP2-KVM -daemonize > > > > Dest : KVM-70, Fedora 8, 64bit > > qemu-system-x86_64 -net nic,vlan=0,macaddr=00:16:3e:16:f4:f0 -net > user,vlan=0 -hda /mnt/nfs/vmdisks/XPSP2-KVM.disk.xm -boot c -m 1024 > -no-acpi -vnc :23 -incoming tcp://0:8002 -name XPSP2-KVM -smp 2 -monitor > unix:/var/run/kvm/monitors/XPSP2-KVM,server,nowait -pidfile > /var/run/kvm/pids/XPSP2-KVM -daemonize > > > > > > > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html