All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jan Frey <linux-vNYXhaxa7OiELgA04lAiVw@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: qemu-system-x86_64 locks hard when used with kvm
Date: Mon, 22 Oct 2007 10:50:15 +0200	[thread overview]
Message-ID: <471C6447.50607@qumranet.com> (raw)
In-Reply-To: <200710182246.37625.linux-vNYXhaxa7OiELgA04lAiVw@public.gmane.org>

Jan Frey wrote:
> On Tuesday 16 October 2007, Avi Kivity wrote:
>   
>> Jan Frey wrote:
>>     
>>>> Can you set up netconsole or serial console on that machine and grab
>>>> the kernel output?
>>>>         
>>> Currently I don't have really much time.. could you point me to some
>>> guide or manual about what to do exactly? I'll try to do so in a few
>>> days..
>>>       
>> Netconsole is easiest (no need for a special cable).  See
>> Documentation/networking/netconsole.txt.
>>     
>
> So... found the time for testing it.
> Unfortunately console stays silent.. machine crashes immediately (even 
> reset button won't work, I've got to poweroff hard..)
> I checked network config, my second machine reports some other kernel 
> messages, but there is nothing coming related to qemu befor crashing.
>
>   

Can you post the log anyway?  Maybe there's a hint there.

Is your host compiled with preemption enabled?


-- 
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/

  parent reply	other threads:[~2007-10-22  8:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 20:24 qemu-system-x86_64 locks hard when used with kvm Jan Frey
     [not found] ` <200710142224.04143.linux-vNYXhaxa7OiELgA04lAiVw@public.gmane.org>
2007-10-15  9:13   ` Avi Kivity
     [not found]     ` <47132F1C.4010100-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-15 17:52       ` Jan Frey
     [not found]         ` <200710151952.49328.linux-vNYXhaxa7OiELgA04lAiVw@public.gmane.org>
2007-10-16 10:42           ` Avi Kivity
     [not found]             ` <47149595.5020900-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-18 20:46               ` Jan Frey
     [not found]                 ` <200710182246.37625.linux-vNYXhaxa7OiELgA04lAiVw@public.gmane.org>
2007-10-22  8:50                   ` Avi Kivity [this message]
2007-10-24 13:33   ` Amit Shah
     [not found]     ` <200710241903.37306.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-24 17:36       ` Jan Frey

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=471C6447.50607@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-vNYXhaxa7OiELgA04lAiVw@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.