From: Jan Kiszka <jan.kiszka@siemens.com>
To: Katrina Austin <kaustin272@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Bug report for kvm-kmod-3.3!
Date: Wed, 28 Mar 2012 14:52:27 +0200 [thread overview]
Message-ID: <4F73098B.2050109@siemens.com> (raw)
In-Reply-To: <CACoo-csZrB=hiiHgqdMjm7cjsbv5oqsEj21myMtwaxaZvd31vA@mail.gmail.com>
On 2012-03-28 14:44, Katrina Austin wrote:
> Hi Jan,
> Now I wanna to locate the instruction in the guest OS that causes this problem. However, I dont know how to make it as the guest OS has not yet started up. I would be much appreicated if you can provide some suggestions.
Not sure if we discussed this already, but getting kvm-kmod from the
list of suspects would be good, ie. testing original kvm over a recent
kernel (3.3 or kvm.git). There is always the risk that some wrapping is
broken and causes such an error.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2012-03-28 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 8:19 [Qemu-devel] Bug report for kvm-kmod-3.3! Katrina Austin
2012-03-23 10:28 ` Jan Kiszka
2012-03-23 11:45 ` Katrina Austin
2012-03-23 12:13 ` Jan Kiszka
2012-03-23 12:21 ` Katrina Austin
2012-03-24 2:21 ` Katrina Austin
2012-03-28 12:44 ` Katrina Austin
2012-03-28 12:52 ` Jan Kiszka [this message]
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=4F73098B.2050109@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kaustin272@gmail.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).