public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Marco Menardi <mmenaz-O5WfVfzUwx8@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: AsteriskNOWbeta6 kernel panic at boot
Date: Sun, 09 Sep 2007 11:00:06 +0300	[thread overview]
Message-ID: <46E3A806.9090307@qumranet.com> (raw)
In-Reply-To: <46DF1AC9.2040500-O5WfVfzUwx8@public.gmane.org>

Marco Menardi wrote:
> * cpu model: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+.
> * kvm version: 36-0.1 from Debian64 Sid
> * host kernel version: 2.6.22-1-amd64
> * host kernel arch: x86_64
> * guest: AsteriskNOW_beta6.5, Linux 32bit,  kernel version
> * command line:
>   kvm -boot d -cdrom asterisk_11599_asterisk-0.9.6.5-x86-disc1.iso -m 
> 1024 -no-acpi
> * with the -no-kvm switch it runs just fine
>
> Call Trace:
>   [<c0111c25>] setup_apic_nmi_watchdog+0x51/0xb2
>   [<c0110fae>] setup_local_APIC+0x21a/0x224
>   [<c0100329>] init+0x0/0x147
>   [<c0100329>] init+0x0/0x147
>   [<c0100329>] init+0x0/0x147
>   [<c03cd554>] APIC_init_uniprocessor+0x9c/0xca
>   [<c010035b>] init+0x32/0x147
>   [<c0104687>] kernel_thread_helper+0x7/0x10
>   

Try adding 'nmi_watchdog=0' to the guest kernel command line (when it is 
running isolinux).

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

      parent reply	other threads:[~2007-09-09  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 21:08 AsteriskNOWbeta6 kernel panic at boot Marco Menardi
     [not found] ` <46DF1AC9.2040500-O5WfVfzUwx8@public.gmane.org>
2007-09-09  8:00   ` Avi Kivity [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=46E3A806.9090307@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=mmenaz-O5WfVfzUwx8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox