From: 박은병 <peb1611@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: [pvops dom0 xm save failed]
Date: Tue, 23 Mar 2010 20:27:46 +0900 [thread overview]
Message-ID: <ebf0d9031003230427q7d68d48eo984899bfc0d7e889@mail.gmail.com> (raw)
In-Reply-To: <20100323110728.GG1878@reaktio.net>
[-- Attachment #1.1: Type: text/plain, Size: 7473 bytes --]
this is my domU config file
there is nothing special....
==============================================================
kernel = "/boot/vmlinuz-2.6.32.10-domU"
ramdisk = "/boot/initrd.img-2.6.32.10-domU"
memory = 1024
name = "ubuntu1"
vcpus = 1
vif = [ 'mac=00:16:3e:48:ef:5c, bridge=eth0' ]
disk = [
'file:/root/xen/domainU/ubuntu1/ubuntu1.img,xvda1,w','file:/root/xen/domainU/ubuntu1/ubuntu1_swap.img,xvda2,w'
]
hostname= "ubuntu1"
root = "/dev/xvda1 ro"
extra = "console=hvc0 earlyprintk=xen"
==============================================================
and I also used Ubuntu distribution .config file which was created at Ubuntu
install time for domU build
2010/3/23 Pasi Kärkkäinen <pasik@iki.fi>
> 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/<guest> cfgfile?
>
> -- Pasi
>
> > 2010/3/23 Pasi Kärkkäinen <[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] <Domain> <CheckpointFile>
> > >
> > > 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=migrating-ubuntu1 id=3 reason=suspend.
> > > [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", line
> > > 132, in save
> > > forkHelper(cmd, fd, saveInputHandler, False)
> > > File
> > "/usr/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line
> > > 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=3
> > > [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) Removing
> > vif/0
> > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134)
> > > XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removing
> > console/0
> > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134)
> > > XendDomainInfo.destroyDevice: deviceClass = console, device =
> > console/0
> > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removing
> > vbd/51713
> > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134)
> > > XendDomainInfo.destroyDevice: deviceClass = vbd, device =
> vbd/51713
> > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removing
> > vbd/51714
> > > [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134)
> > > XendDomainInfo.destroyDevice: deviceClass = vbd, device =
> 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( vanilla
> > 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
>
--
Eunbyung Park
[-- Attachment #1.2: Type: text/html, Size: 9007 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-23 11:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 8:04 [pvops dom0 xm save failed] 박은병
2010-03-23 9:07 ` Pasi Kärkkäinen
2010-03-23 11:01 ` 박은병
2010-03-23 11:07 ` Pasi Kärkkäinen
2010-03-23 11:27 ` 박은병 [this message]
2010-03-23 11:30 ` Pasi Kärkkäinen
2010-03-23 11:32 ` 박은병
2010-03-23 11:37 ` Pasi Kärkkäinen
2010-03-23 13:25 ` 박은병
2010-03-23 13:45 ` Pasi Kärkkäinen
2010-03-23 13:47 ` 박은병
2010-03-23 13:53 ` Pasi Kärkkäinen
2010-03-23 14:06 ` 박은병
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ebf0d9031003230427q7d68d48eo984899bfc0d7e889@mail.gmail.com \
--to=peb1611@gmail.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).