From: Avi Kivity <avi@qumranet.com>
To: Luca <kronos.it@gmail.com>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [BUG] Oops with KVM-27
Date: Mon, 11 Jun 2007 10:44:45 +0300 [thread overview]
Message-ID: <466CFD6D.2080201@qumranet.com> (raw)
In-Reply-To: <68676e00706101354n5fe7e1a9y12cb690cae2924e3@mail.gmail.com>
Luca wrote:
>>
>> I've managed to reproduce this on kvm-21 (it takes many boots for this
>> to happen, but it does eventually).
>
> Hum, any clue on the cause?
From what I've seen, it's the new Linux clocksource code.
> Should I test older versions?
They're unlikely to be better. Instead, it would be best to see what
the guest is doing.
I suggest downloading the source rpm for the kernel, building it, and
sprinkling printk()s until we know exactly what source the guest is
executing at the time of the hang.
Use of the qemu -kernel, -append, and -serial can redirect the console
to the command line so that it's easy to capture all debug output.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-06-11 7:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 21:34 [BUG] Oops with KVM-27 Luca Tettamanti
2007-06-04 9:35 ` [kvm-devel] " Avi Kivity
2007-06-04 20:22 ` Luca Tettamanti
2007-06-04 20:51 ` Avi Kivity
2007-06-04 21:22 ` Luca Tettamanti
2007-06-05 7:27 ` Avi Kivity
2007-06-07 19:16 ` Luca
2007-06-10 12:22 ` Avi Kivity
2007-06-10 20:54 ` Luca
2007-06-11 7:44 ` Avi Kivity [this message]
2007-06-11 21:06 ` Luca
2007-06-12 6:44 ` Avi Kivity
2007-06-12 17:52 ` Luca Tettamanti
2007-06-13 8:59 ` Avi Kivity
2007-06-13 20:49 ` Luca Tettamanti
2007-06-14 8:26 ` Avi Kivity
2007-06-14 22:33 ` Luca Tettamanti
2007-06-14 22:53 ` Luca Tettamanti
2007-06-14 23:13 ` Luca Tettamanti
2007-06-14 23:27 ` Luca
2007-06-15 9:06 ` Avi Kivity
2007-06-15 21:49 ` Luca Tettamanti
2007-06-16 7:43 ` Avi Kivity
2007-06-17 15:14 ` Luca Tettamanti
2007-06-17 15:24 ` Avi Kivity
2007-06-17 16:52 ` [PATCH 1/2] kvm: Fix x86 emulator writeback Luca Tettamanti
2007-06-17 16:58 ` Avi Kivity
2007-06-18 10:07 ` Avi Kivity
2007-06-18 11:32 ` Avi Kivity
2007-06-19 20:25 ` Luca Tettamanti
2007-06-19 20:41 ` Luca Tettamanti
2007-06-20 7:47 ` Avi Kivity
2007-06-19 20:41 ` [PATCH 2/2] kvm: avoid useless memory write when possible Luca Tettamanti
2007-06-17 16:52 ` Luca Tettamanti
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=466CFD6D.2080201@qumranet.com \
--to=avi@qumranet.com \
--cc=kronos.it@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).