From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jun Koi <junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: kvm-33 crash
Date: Thu, 26 Jul 2007 10:53:25 +0300 [thread overview]
Message-ID: <46A852F5.5000408@qumranet.com> (raw)
In-Reply-To: <fdaac4d50707260025y585ac78cjc250298473f34ae6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Jun Koi wrote:
> On 7/26/07, Jun Koi <junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>> On 7/26/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>>
>>> Jun Koi wrote:
>>>
>>>> Hi,
>>>>
>>>> kvm-33 crashes on my Linux box. It happens after booting for few
>>>> seconds, ie not reached the prompt yet. And that never happens before
>>>> with previous versions on the same qemu image.
>>>>
>>>> I want to post the boot log here, but dont know how to configure qemu
>>>> to do that. Any pointer?
>>>>
>>>>
>>>>
>>> What crashes? The guest or the host? What kernel versions?
>>>
>>>
>>>
>> The guest crashed. Host kernel is 2.6.21, and same for guest.
>>
>>
>
> I figure it out why it crashes: my guest (Linux 2.6.21) is compiled
> with SMP kernel. If I run qemu without -smp option, it crashes. But
> with -smp option, it is fine.
>
> So this is a bug, and should be fixed.
>
>
Yes. I updated http://kvm.qumranet.com/kvmwiki/Bugs to include
information on extracting a serial log. Also, please post your .config
along with the guest log.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-07-26 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 4:36 kvm-33 crash Jun Koi
[not found] ` <fdaac4d50707252136t63d08fb4h5f138caf27a8b1c3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-26 5:21 ` Avi Kivity
[not found] ` <46A82F55.9020506-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-26 5:32 ` Jun Koi
[not found] ` <fdaac4d50707252232j6b59fd7bt18318bd1d48cbc3a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-26 7:25 ` Jun Koi
[not found] ` <fdaac4d50707260025y585ac78cjc250298473f34ae6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-26 7:53 ` Avi Kivity [this message]
[not found] ` <46A852F5.5000408-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-26 10:00 ` Jun Koi
[not found] ` <fdaac4d50707260300r1abc6a97i4f2b94eb4b62c597-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-26 10:07 ` Avi Kivity
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=46A852F5.5000408@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 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.