From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: [pvops dom0 xm save failed] Date: Tue, 23 Mar 2010 13:07:28 +0200 Message-ID: <20100323110728.GG1878@reaktio.net> References: <20100323090737.GC1878@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: ?????? Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Tue, Mar 23, 2010 at 08:01:42PM +0900, ?????? wrote: > 2.6.32.10 domU also failed with same error log.. > Is it exactly domU problem?? >=20 For PV guests it is _usually_ a domU kernel problem. > Is there specific kernel configuration related to save/restore?? > any other comments?? >=20 I tested using 2.6.32.9 in the domU 1 month ago (or so),=20 and I could save/restore just fine. I tried both 32bit and 64bit guests, and both single-vcpu and multi-vcpu. my .config was based on Fedora kernel .config. Please paste your /etc/xen/ cfgfile?=20 -- Pasi > 2010/3/23 Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> >=20 > On Tue, Mar 23, 2010 at 05:04:59PM +0900, ?????? wrote: > > when I command 'xm save [domainU] [filename]', save process d= oes > not > > complete with this error message > > > > Error: /usr/lib/xen/bin/xc_save 34 2 0 0 0 failed > > Usage: xm save [-c] > > > > Save a domain state to restore later. > > -c, --checkpoint Leave domain running after > > creating > > snapshot > > > > and /var/log/xen/xend.log produced below error message. > > > > [2010-03-23 16:58:07 1023] DEBUG (DevController:643) > hotplugStatusCallback > > 1. > > [2010-03-23 16:58:07 1023] DEBUG (DevController:139) Waiting = for > devices > > irq. > > [2010-03-23 16:58:07 1023] DEBUG (DevController:139) Waiting = for > devices > > vfb. > > [2010-03-23 16:58:07 1023] DEBUG (DevController:139) Waiting = for > devices > > pci. > > [2010-03-23 16:58:07 1023] DEBUG (DevController:139) Waiting = for > devices > > vtpm. > > [2010-03-23 16:58:07 1023] INFO (XendDomain:1182) Domain ubun= tu1 > (3) > > unpaused. > > [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:110) [xc_sav= e]: > > /usr/lib/xen/bin/xc_save 34 3 0 0 0 > > [2010-03-23 16:58:42 1023] INFO (XendCheckpoint:417) xc_save: > failed to > > get the suspend evtchn port > > [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:388) suspend > > [2010-03-23 16:58:42 1023] INFO (XendCheckpoint:417) > > [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:113) In > saveInputHandler > > suspend > > [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:115) Suspend= ing 3 > ... > > [2010-03-23 16:58:42 1023] DEBUG (XendDomainInfo:511) > > XendDomainInfo.shutdown(suspend) > > [2010-03-23 16:58:42 1023] DEBUG (XendDomainInfo:1709) > > XendDomainInfo.handleShutdownWatch > > [2010-03-23 16:58:42 1023] DEBUG (XendDomainInfo:1709) > > XendDomainInfo.handleShutdownWatch > > [2010-03-23 16:58:42 1023] INFO (XendDomainInfo:1903) Domain = has > shutdown: > > name=3Dmigrating-ubuntu1 id=3D3 reason=3Dsuspend. > > [2010-03-23 16:58:42 1023] INFO (XendCheckpoint:121) Domain 3 > suspended. > > [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:130) Written= done > > [2010-03-23 16:58:42 1023] ERROR (XendCheckpoint:164) Save fa= iled > on > > domain ubuntu1 (3) - resuming. > > Traceback (most recent call last): > > File > "/usr/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", lin= e > > 132, in save > > forkHelper(cmd, fd, saveInputHandler, False) > > File > "/usr/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", lin= e > > 405, in forkHelper > > raise XendError("%s failed" % string.join(cmd)) > > XendError: /usr/lib/xen/bin/xc_save 34 3 0 0 0 failed > > [2010-03-23 16:58:42 1023] DEBUG (XendDomainInfo:2788) > > XendDomainInfo.resumeDomain(3) > > [2010-03-23 16:58:42 1023] DEBUG (XendDomainInfo:2829) > > XendDomainInfo.resumeDomain: completed > > [2010-03-23 17:01:10 1023] DEBUG (XendDomainInfo:2732) > > XendDomainInfo.destroy: domid=3D3 > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2207) Destro= ying > device > > model > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2214) Releas= ing > devices > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removi= ng > vif/0 > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134) > > XendDomainInfo.destroyDevice: deviceClass =3D vif, device =3D= vif/0 > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removi= ng > console/0 > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134) > > XendDomainInfo.destroyDevice: deviceClass =3D console, device= =3D > console/0 > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removi= ng > vbd/51713 > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134) > > XendDomainInfo.destroyDevice: deviceClass =3D vbd, device =3D= vbd/51713 > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removi= ng > vbd/51714 > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134) > > XendDomainInfo.destroyDevice: deviceClass =3D vbd, device =3D= vbd/51714 > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2212) No dev= ice > model > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2214) Releas= ing > devices > > > > my system configuration ( 32bit machine ) > > xen 3.4.2, dom0( jeremy's pvops kernel 2.6.31.6), domU( vanil= la > kernel > > 2.6.32 with paravirt enabled), distribution( ubuntu 9.10 ) > > It does not work well > > > > what is the problem?? > > I think current system is quite stable, newtork, disk, and so= on. > > Is there anyone who know this or has experience?? > > >=20 > You need to update your domU kernel to the latest stable update > (2.6.32.10), > and that'll fix the problem. 2.6.32(.0) doesn't yet have the neces= sary > save/restore fixes. >=20 > -- Pasi >=20 > -- > Eunbyung Park >=20 > References >=20 > Visible links > 1. mailto:pasik@iki.fi