From: Valtteri Kiviniemi <valtteri.kiviniemi@dataproof.fi>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Suspend/save wont work with the newer dom0 kernels
Date: Thu, 16 Jul 2009 18:14:53 +0300 [thread overview]
Message-ID: <4A5F43ED.3050605@dataproof.fi> (raw)
Hi,
I am running the 2.6.30 dom0 kernel (suse patched) and everyting else is
working except suspend:
When I try to run "xm save" the domU will shutdown and in xend.log I can
see following:
2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:110) [xc_save]:
/usr/lib64/xen/bin/xc_save 57 6 0 0 0
[2009-07-16 18:09:34 2559] INFO (XendCheckpoint:417) ERROR Internal
error: Can't create lock file for suspend event channel
[2009-07-16 18:09:34 2559] INFO (XendCheckpoint:417)
[2009-07-16 18:09:34 2559] INFO (XendCheckpoint:417) xc_save: suspend
event channel initialization failedusing slow path
[2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:388) suspend
[2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:113) In
saveInputHandler suspend
[2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:115) Suspending 6 ...
[2009-07-16 18:09:34 2559] DEBUG (XendDomainInfo:511)
XendDomainInfo.shutdown(suspend)
[2009-07-16 18:09:34 2559] DEBUG (XendDomainInfo:1709)
XendDomainInfo.handleShutdownWatch
[2009-07-16 18:09:34 2559] DEBUG (XendDomainInfo:1709)
XendDomainInfo.handleShutdownWatch
And then I just have to restart the domU. The only kernel that I have
tested with working suspend is the defaul 2.6.18.8. pv_ops, suse patched
and the novell 2.6.27 all fail the same way.
What could be the problem?
--
Ystävällisin terveisin,
Dataproof
Aleksanterinkatu 7 A 14
15110 LAHTI
puh. 0405166397
Valtteri Kiviniemi
reply other threads:[~2009-07-16 15:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A5F43ED.3050605@dataproof.fi \
--to=valtteri.kiviniemi@dataproof.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.