From: Avi Kivity <avi@redhat.com>
To: Kasper Sandberg <lkml@metanurb.dk>
Cc: kvm@vger.kernel.org
Subject: Re: kvm kernel backtrace 2.6.27.3 using kvm 78 userspace
Date: Sun, 23 Nov 2008 10:49:08 +0200 [thread overview]
Message-ID: <49291904.5000607@redhat.com> (raw)
In-Reply-To: <1227386974.19624.103.camel@localhost>
Kasper Sandberg wrote:
> Hello.
>
> I just noticed that my dmesg had been flooded with backtraces, appearing
> to be of KVM origin. I realize that my kernel is tainted, and slightly
> outdated, however, i just wanted to drop the log here in case it might
> be useful, but feel free to completely ignore it :)
>
> i am not subscribed to the kvm list, so please cc me in case you need
> further info..
>
> my entire dmesg was flooded with backtraces looking practically
> identical to this one, so i will only paste a few of them, however,
> should you want more(though from a quick look they appear identical), i
> can put online the complete log
>
What guest are you running?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-11-23 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 20:49 kvm kernel backtrace 2.6.27.3 using kvm 78 userspace Kasper Sandberg
2008-11-23 8:49 ` Avi Kivity [this message]
2008-11-23 14:23 ` Kasper Sandberg
2008-11-23 14:27 ` Avi Kivity
2008-11-23 16:16 ` Kasper Sandberg
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=49291904.5000607@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lkml@metanurb.dk \
/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