public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: KVM mailing list <kvm@vger.kernel.org>
Cc: mgoldish@redhat.com, ehabkost@redhat.com, nsprei@redhat.com,
	dlaor@redhat.com
Subject: qemu-kvm.git master suspend to RAM issues
Date: Mon, 08 Feb 2010 08:58:25 -0200	[thread overview]
Message-ID: <1265626705.2438.47.camel@localhost.localdomain> (raw)
In-Reply-To: <201002080210.o182Akln017619@int-mx08.intmail.prod.int.phx2.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]

Hi folks,

We've had consistent suspend to RAM issues on today's upstream job, for
qemu-kvm.git

kvm.qemu-kvm-git.1.hp.raw.smp2.Fedora.11.64.linux_s3
kvm.qemu-kvm-git.1.smp2.Fedora.11.32.linux_s3
kvm.qemu-kvm-git.2.hp.smp2.Fedora.11.64.linux_s3
kvm.qemu-kvm-git.2.smp2.Fedora.11.32.linux_s3

qemu-kvm.git commit and tag:

02/07 11:05:01 INFO | kvm_utils:0367| Commit hash for git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git is ed880109f74f0a4dd5b7ec09e6a2d9ba4903d9a5 (tag kvm-88-3361-ged88010)

All suspend to ram tests failed for qemu-kvm.git. Here is a relevant
snippet of a log, that shows when the failure happens:

02/07 14:41:36 INFO |kvm_test_u:0060| Logged into guest 'vm1'
02/07 14:41:36 INFO |  linux_s3:0017| Checking that VM supports S3
02/07 14:41:36 DEBUG|kvm_subpro:1119| Sending command: grep -q mem /sys/power/state
02/07 14:41:36 INFO |  linux_s3:0024| Waiting for a while for X to start
02/07 14:41:46 DEBUG|kvm_subpro:1119| Sending command: fgconsole
02/07 14:41:46 INFO |  linux_s3:0028| Current virtual terminal is 1
02/07 14:41:46 INFO |  linux_s3:0036| Putting VM into S3
02/07 14:41:46 DEBUG|kvm_subpro:1119| Sending command: chvt 2 && echo mem > /sys/power/state && chvt 1
02/07 14:41:58 DEBUG|kvm_subpro:0899| Timeout elapsed or process terminated. Output:
02/07 14:41:58 ERROR|       kvm:0061| Test failed: Suspend to mem failed

qemu.git didn't have such problems, on the very same job.

I am attaching a tarball with the full logs of one failed test. It
includes things like kvm_stat output during test execution. Let me know
whether you need more info to track down the issue.

Lucas

[-- Attachment #2: kvm.qemu-kvm-git.1.hp.raw.smp2.Fedora.11.64.linux_s3.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 38943 bytes --]

           reply	other threads:[~2010-02-08 10:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <201002080210.o182Akln017619@int-mx08.intmail.prod.int.phx2.redhat.com>]

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=1265626705.2438.47.camel@localhost.localdomain \
    --to=lmr@redhat.com \
    --cc=dlaor@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mgoldish@redhat.com \
    --cc=nsprei@redhat.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