From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?EUC-KR?B?udrAurq0?= Subject: Re: [pvops dom0 xm save failed] Date: Tue, 23 Mar 2010 20:27:46 +0900 Message-ID: References: <20100323090737.GC1878@reaktio.net> <20100323110728.GG1878@reaktio.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1919221860==" Return-path: In-Reply-To: <20100323110728.GG1878@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1919221860== Content-Type: multipart/alternative; boundary=0016e647572253ea810482761a2f --0016e647572253ea810482761a2f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable this is my domU config file there is nothing special.... =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D kernel =3D "/boot/vmlinuz-2.6.32.10-domU" ramdisk =3D "/boot/initrd.img-2.6.32.10-domU" memory =3D 1024 name =3D "ubuntu1" vcpus =3D 1 vif =3D [ 'mac=3D00:16:3e:48:ef:5c, bridge=3Deth0' ] disk =3D [ 'file:/root/xen/domainU/ubuntu1/ubuntu1.img,xvda1,w','file:/root/xen/domain= U/ubuntu1/ubuntu1_swap.img,xvda2,w' ] hostname=3D "ubuntu1" root =3D "/dev/xvda1 ro" extra =3D "console=3Dhvc0 earlyprintk=3Dxen" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D and I also used Ubuntu distribution .config file which was created at Ubunt= u install time for domU build 2010/3/23 Pasi K=E4rkk=E4inen > 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?? > > > > For PV guests it is _usually_ a domU kernel problem. > > > Is there specific kernel configuration related to save/restore?? > > any other comments?? > > > > I tested using 2.6.32.9 in the domU 1 month ago (or so), > 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? > > -- Pasi > > > 2010/3/23 Pasi K=E4rkk=E4inen <[1]pasik@iki.fi> > > > > On Tue, Mar 23, 2010 at 05:04:59PM +0900, ?????? wrote: > > > when I command 'xm save [domainU] [filename]', save process > does > > 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 > ubuntu1 > > (3) > > > unpaused. > > > [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:110) > [xc_save]: > > > /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) > Suspending 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 > failed > > 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) > Destroying > > device > > > model > > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2214) > Releasing > > 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 > device > > model > > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2214) > Releasing > > 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?? > > > > > > > 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 > necessary > > save/restore fixes. > > > > -- Pasi > > > > -- > > Eunbyung Park > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > --=20 Eunbyung Park --0016e647572253ea810482761a2f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable this is my domU config file
there is nothing special....

=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
kernel =3D "/boot/vmlinuz-2.6.32.10-= domU"
ramdisk =3D "/boot/initrd.img-2.6.32.10-domU"
memory =3D 1024
name =3D "ubuntu1"
vcpus =3D 1
vif =3D [= 'mac=3D00:16:3e:48:ef:5c, bridge=3Deth0' ]
disk =3D [ 'file= :/root/xen/domainU/ubuntu1/ubuntu1.img,xvda1,w','file:/root/xen/dom= ainU/ubuntu1/ubuntu1_swap.img,xvda2,w' ]
hostname=3D "ubuntu1"
root =3D "/dev/xvda1 ro"
ex= tra =3D "console=3Dhvc0 earlyprintk=3Dxen"
=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D

and I also used Ubuntu distribution .config file = which was created at Ubuntu install time for domU build

2010/3/23 Pasi K=E4rkk=E4inen <pasik@iki.fi>
On Tue, Mar 23, 2010 at 08:01:42PM +0900, ?????? wrote: > =A0 =A02.6.32.10 domU also failed with same error log..
> =A0 =A0Is it exactly domU problem??
>

For PV guests it is _usually_ a domU kernel problem.

> =A0 =A0Is there specific kernel configuration related to save/restore?= ?
> =A0 =A0any other comments??
>

I tested using 2.6.32.9 in the domU 1 month ago (or so),
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/<guest> cfgfile?

-- Pasi

> =A0 =A02010/3/23 Pasi K=E4rkk=E4inen <[1]pasik@iki.fi>
>
> =A0 =A0 =A0On Tue, Mar 23, 2010 at 05:04:59PM +0900, ?????? wrote:
> =A0 =A0 =A0> =A0 =A0when I command 'xm save [domainU] [filename= ]', save process does
> =A0 =A0 =A0not
> =A0 =A0 =A0> =A0 =A0complete with this error message
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0Error: /usr/lib/xen/bin/xc_save 34 2 0 0 0 fail= ed
> =A0 =A0 =A0> =A0 =A0Usage: xm save [-c] <Domain> <Checkpoi= ntFile>
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0Save a domain state to restore later.
> =A0 =A0 =A0> =A0 =A0 =A0-c, --checkpoint =A0 =A0 =A0 =A0 =A0 =A0 = =A0 Leave domain running after
> =A0 =A0 =A0> =A0 =A0creating
> =A0 =A0 =A0> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 snapshot
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0and /var/log/xen/xend.log produced below error = message.
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:07 1023] DEBUG (DevController= :643)
> =A0 =A0 =A0hotplugStatusCallback
> =A0 =A0 =A0> =A0 =A01.
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:07 1023] DEBUG (DevController= :139) Waiting for
> =A0 =A0 =A0devices
> =A0 =A0 =A0> =A0 =A0irq.
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:07 1023] DEBUG (DevController= :139) Waiting for
> =A0 =A0 =A0devices
> =A0 =A0 =A0> =A0 =A0vfb.
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:07 1023] DEBUG (DevController= :139) Waiting for
> =A0 =A0 =A0devices
> =A0 =A0 =A0> =A0 =A0pci.
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:07 1023] DEBUG (DevController= :139) Waiting for
> =A0 =A0 =A0devices
> =A0 =A0 =A0> =A0 =A0vtpm.
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:07 1023] INFO (XendDomain:118= 2) Domain ubuntu1
> =A0 =A0 =A0(3)
> =A0 =A0 =A0> =A0 =A0unpaused.
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] DEBUG (XendCheckpoin= t:110) [xc_save]:
> =A0 =A0 =A0> =A0 =A0/usr/lib/xen/bin/xc_save 34 3 0 0 0
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] INFO (XendCheckpoint= :417) xc_save:
> =A0 =A0 =A0failed to
> =A0 =A0 =A0> =A0 =A0get the suspend evtchn port
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] DEBUG (XendCheckpoin= t:388) suspend
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] INFO (XendCheckpoint= :417)
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] DEBUG (XendCheckpoin= t:113) In
> =A0 =A0 =A0saveInputHandler
> =A0 =A0 =A0> =A0 =A0suspend
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] DEBUG (XendCheckpoin= t:115) Suspending 3
> =A0 =A0 =A0...
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] DEBUG (XendDomainInf= o:511)
> =A0 =A0 =A0> =A0 =A0XendDomainInfo.shutdown(suspend)
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] DEBUG (XendDomainInf= o:1709)
> =A0 =A0 =A0> =A0 =A0XendDomainInfo.handleShutdownWatch
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] DEBUG (XendDomainInf= o:1709)
> =A0 =A0 =A0> =A0 =A0XendDomainInfo.handleShutdownWatch
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] INFO (XendDomainInfo= :1903) Domain has
> =A0 =A0 =A0shutdown:
> =A0 =A0 =A0> =A0 =A0name=3Dmigrating-ubuntu1 id=3D3 reason=3Dsuspen= d.
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] INFO (XendCheckpoint= :121) Domain 3
> =A0 =A0 =A0suspended.
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] DEBUG (XendCheckpoin= t:130) Written done
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] ERROR (XendCheckpoin= t:164) Save failed
> =A0 =A0 =A0on
> =A0 =A0 =A0> =A0 =A0domain ubuntu1 (3) - resuming.
> =A0 =A0 =A0> =A0 =A0Traceback (most recent call last):
> =A0 =A0 =A0> =A0 =A0 =A0File
> =A0 =A0 =A0"/usr/lib/python2.6/dist-packages/xen/xend/XendCheckpo= int.py", line
> =A0 =A0 =A0> =A0 =A0132, in save
> =A0 =A0 =A0> =A0 =A0 =A0 =A0forkHelper(cmd, fd, saveInputHandler, F= alse)
> =A0 =A0 =A0> =A0 =A0 =A0File
> =A0 =A0 =A0"/usr/lib/python2.6/dist-packages/xen/xend/XendCheckpo= int.py", line
> =A0 =A0 =A0> =A0 =A0405, in forkHelper
> =A0 =A0 =A0> =A0 =A0 =A0 =A0raise XendError("%s failed" %= string.join(cmd))
> =A0 =A0 =A0> =A0 =A0XendError: /usr/lib/xen/bin/xc_save 34 3 0 0 0 = failed
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] DEBUG (XendDomainInf= o:2788)
> =A0 =A0 =A0> =A0 =A0XendDomainInfo.resumeDomain(3)
> =A0 =A0 =A0> =A0 =A0[2010-03-23 16:58:42 1023] DEBUG (XendDomainInf= o:2829)
> =A0 =A0 =A0> =A0 =A0XendDomainInfo.resumeDomain: completed
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:10 1023] DEBUG (XendDomainInf= o:2732)
> =A0 =A0 =A0> =A0 =A0XendDomainInfo.destroy: domid=3D3
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:2207) Destroying
> =A0 =A0 =A0device
> =A0 =A0 =A0> =A0 =A0model
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:2214) Releasing
> =A0 =A0 =A0devices
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:2227) Removing
> =A0 =A0 =A0vif/0
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:1134)
> =A0 =A0 =A0> =A0 =A0XendDomainInfo.destroyDevice: deviceClass =3D v= if, device =3D vif/0
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:2227) Removing
> =A0 =A0 =A0console/0
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:1134)
> =A0 =A0 =A0> =A0 =A0XendDomainInfo.destroyDevice: deviceClass =3D c= onsole, device =3D
> =A0 =A0 =A0console/0
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:2227) Removing
> =A0 =A0 =A0vbd/51713
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:1134)
> =A0 =A0 =A0> =A0 =A0XendDomainInfo.destroyDevice: deviceClass =3D v= bd, device =3D vbd/51713
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:2227) Removing
> =A0 =A0 =A0vbd/51714
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:1134)
> =A0 =A0 =A0> =A0 =A0XendDomainInfo.destroyDevice: deviceClass =3D v= bd, device =3D vbd/51714
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:2212) No device
> =A0 =A0 =A0model
> =A0 =A0 =A0> =A0 =A0[2010-03-23 17:01:11 1023] DEBUG (XendDomainInf= o:2214) Releasing
> =A0 =A0 =A0devices
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0my system configuration ( 32bit machine )
> =A0 =A0 =A0> =A0 =A0xen 3.4.2, dom0( jeremy's pvops kernel 2.6.= 31.6), domU( vanilla
> =A0 =A0 =A0kernel
> =A0 =A0 =A0> =A0 =A02.6.32 with paravirt enabled), distribution( ub= untu 9.10 )
> =A0 =A0 =A0> =A0 =A0It does not work well
> =A0 =A0 =A0>
> =A0 =A0 =A0> =A0 =A0what is the problem??
> =A0 =A0 =A0> =A0 =A0I think current system is quite stable, newtork= , disk, and so on.
> =A0 =A0 =A0> =A0 =A0Is there anyone who know this or has experience= ??
> =A0 =A0 =A0>
>
> =A0 =A0 =A0You need to update your domU kernel to the latest stable up= date
> =A0 =A0 =A0(2.6.32.10),
> =A0 =A0 =A0and that'll fix the problem. 2.6.32(.0) doesn't yet= have the necessary
> =A0 =A0 =A0save/restore fixes.
>
> =A0 =A0 =A0-- Pasi
>
> =A0 =A0--
> =A0 =A0Eunbyung Park
>
> References
>
> =A0 =A0Visible links
> =A0 =A01. mailto:pasik@iki.fi



--
Eunbyung Park
--0016e647572253ea810482761a2f-- --===============1919221860== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1919221860==--