From: Alexander Graf <agraf@suse.de>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Joerg Roedel <joerg.roedel@amd.com>,
Sheng Yang <sheng@linux.intel.com>
Subject: KVM guest crashes
Date: Tue, 20 Jan 2009 16:49:01 +0100 [thread overview]
Message-ID: <4975F26D.707@suse.de> (raw)
Hi list,
recently I've been hitting some KVM bugs others seem to have reported as
well, including
- CIFS timeouts
- Stuck ?? errors
- Random segmentation faults in the guest
so I figured, I'll put together a stress test that can be used to
reproduce these issues. This is done by using a CIFS mount on the host
and unpacking data from that mount to the mount. I have been able to
bring kvm down to its knees a lot just by doing this.
Simply run the test in an endless-loop. FWIW enabling NPT helps
triggering the issue.
The guest kernels included here are openSUSE 11.0 (2.6.25) and 11.1
(2.6.27) kernels.
Find the tests here: http://alex.csgraf.de/kvm-tests.tar.bz2
And some logs here (NPT enabled): http://alex.csgraf.de/kvm-logs.tar.bz2
I'm somewhat lost on the reason for these failures, so if you do have
some time on your hands, please give me a hand debugging this! If I'd
had to guess, I'd say it's either an APIC issue and/or guest memory
corruption.
Alex
next reply other threads:[~2009-01-20 15:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 15:49 Alexander Graf [this message]
2009-01-20 20:07 ` KVM guest crashes Avi Kivity
2009-01-20 20:20 ` Alexander Graf
2009-01-21 8:14 ` Alexander Graf
2009-01-21 9:05 ` Avi Kivity
2009-01-21 9:36 ` Avi Kivity
2009-01-21 10:44 ` Alexander Graf
2009-01-22 20:29 ` Alexander Graf
2009-01-22 20:36 ` Alexander Graf
2009-01-22 20:55 ` Alexander Graf
2009-01-23 16:36 ` Alexander Graf
2009-01-23 22:36 ` Marcelo Tosatti
2009-01-24 7:42 ` Alexander Graf
2009-01-24 13:06 ` Marcelo Tosatti
2009-01-24 14:30 ` Alexander Graf
2009-01-26 15:53 ` Alexander Graf
2009-01-26 16:21 ` Marcelo Tosatti
2009-01-26 16:33 ` Alexander Graf
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=4975F26D.707@suse.de \
--to=agraf@suse.de \
--cc=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.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.