From: Yasir Assam <mail@endlessvoid.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: "xm save" fails on kernel.org domU with Xen 3.4.1
Date: Sat, 31 Oct 2009 08:53:07 +1100 [thread overview]
Message-ID: <4AEB6043.5060404@endlessvoid.com> (raw)
In-Reply-To: <4AEB5AB5.8000900@goop.org>
[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]
Jeremy Fitzhardinge wrote:
> On 10/30/09 14:25, Yasir Assam wrote:
>
>> I sent this message to xen-users and it was suggested on that list
>> that I send it here (no one was able to help me there).
>>
>> I've installed Xen 3.4.1 from source. Some of my paravirt domUs use
>> the official XenLinux kernel (2.6.18) and some use the mainline
>> kernel.org.
>>
>> When I run "xm save" on the kernel.org guests, the "xm save" command
>> hangs where its run in dom0, and on the domU console I get an error:
>>
>> PM: Device rtc_cmos failed to suspend: error -22
>> xen suspend: dpm_suspend_start -22
>>
>> I'm using kernel version 2.6.31.4 for the domU (I've also tried
>> 2.6.31.5), which I've built from source (the XenLinux domUs suspend
>> without a problem).
>>
>> Is this a bug or am I doing something wrong?
>>
>
> Quite possibly a bug. Though I haven't seen those particular messages
> before, they do seem like the kind of messages that would pop up and
> spoil your suspend.
I got some other messages before from bits of of the kernel I didn't
need, and I kept switching those bits off until I got the rtc_cmos error
(I didn't know how to switch that bit off).
> Could you post a full kernel log of a suspending
> domain?
>
I'm not sure what you mean by a full kernel log. Do you mean the output
of dmesg? Or /var/log/syslog?
> Have you tried migration?
>
I haven't tried it - I only run Xen on a single host. If it can migrate
to itself I can give it a try.
Thanks,
Yasir
[-- Attachment #2.1: "AVG certification" --]
[-- Type: text/plain, Size: 159 bytes --]
No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.423 / Virus Database: 270.14.39/2468 - Release Date: 10/29/09 19:49:00
[-- Attachment #3: 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:[~2009-10-30 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 21:25 "xm save" fails on kernel.org domU with Xen 3.4.1 Yasir Assam
2009-10-30 21:29 ` Jeremy Fitzhardinge
2009-10-30 21:53 ` Yasir Assam [this message]
2009-11-02 21:30 ` Yasir Assam
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=4AEB6043.5060404@endlessvoid.com \
--to=mail@endlessvoid.com \
--cc=jeremy@goop.org \
--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.