All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Erez Shitrit <erezsh@mellanox.co.il>
Cc: kvm@vger.kernel.org
Subject: Re: unable to assign devices with VT-d in KVM
Date: Sun, 27 Dec 2009 15:36:54 +0200	[thread overview]
Message-ID: <4B3762F6.6070704@redhat.com> (raw)
In-Reply-To: <2ED289D4E09FBD4D92D911E869B97FDD0227E26B@mtlexch01.mtl.com>

On 12/27/2009 03:09 PM, Erez Shitrit wrote:
> Thanks,
> Now, it seams that I have a problem with the kvm, whenever I tried to
> create a new virtual machine and the kvm module is loaded I got kernel
> panic in the virtual machine.
>
> The panic:
>
> " ...
> Code: 0f 30 b8 76 00 13 00 89 d9 0f 30 48 c7 c6 17 41 2a 80 89 fa
> RIP [<ffffffff8007d43d>] setup_k7_watchdog+0x2d/0x7a
> RSP<ffff81003ffb7e50>
> <0>Kernel panic - not syncing: Fatal exception
> ...
> "
>
> (If I remove the kvm module it works)
>
> The kvm version:
> kvm-83-105.el5_4.13
>
> The KVM did not arrived with the RH5.4 distribution, I installed it
> manually.
>  From the package: kvm-83-105.el5_4.13.x86_64.rpm
>
> Do I need specific version of the kvm with that qemu ?
>
>    

What guest kernel are you running?  What qemu command line?

Looks like your guest thinks it's running on an Athlon.  What's your 
host cpu type?

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


  reply	other threads:[~2009-12-27 13:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-27 10:07 unable to assign devices with VT-d in KVM Erez Shitrit
2009-12-27 10:17 ` Thomas Mueller
2009-12-27 11:10 ` Avi Kivity
2009-12-27 13:09   ` Erez Shitrit
2009-12-27 13:36     ` Avi Kivity [this message]
2009-12-27 13:48       ` Erez Shitrit
2009-12-27 13:51         ` Avi Kivity
2009-12-27 14:36           ` Avi Kivity
2009-12-27 16:42             ` Erez Shitrit
2009-12-29  2:19               ` Sheng Yang
2009-12-29  5:30               ` Sheng Yang
2009-12-29 16:10                 ` Erez Shitrit
2009-12-30  1:17                   ` Sheng Yang
2009-12-30  7:08                     ` Erez Shitrit

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=4B3762F6.6070704@redhat.com \
    --to=avi@redhat.com \
    --cc=erezsh@mellanox.co.il \
    --cc=kvm@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 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.