From: Sheng Yang <sheng@linux.intel.com>
To: kvm@vger.kernel.org
Cc: "Erez Shitrit" <erezsh@mellanox.co.il>, "Avi Kivity" <avi@redhat.com>
Subject: Re: unable to assign devices with VT-d in KVM
Date: Tue, 29 Dec 2009 13:30:09 +0800 [thread overview]
Message-ID: <200912291330.09939.sheng@linux.intel.com> (raw)
In-Reply-To: <2ED289D4E09FBD4D92D911E869B97FDD022E0136@mtlexch01.mtl.com>
On Monday 28 December 2009 00:42:37 Erez Shitrit wrote:
> [I hope I didn't duplicate my response]
> I tried it, still have kernel-panic,
> Currently the message is:
> "
> ....
> MP-BIOS bug: 8254 timer not connected to IO-APIC
> Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the
> 'noapic' kernel parameter
> "
BTW, maybe you give --no-hpet a try in qemu command line.
--
regards
Yang, Sheng
>
> Thanks, Erez
>
> -----Original Message-----
> From: Avi Kivity [mailto:avi@redhat.com]
> Sent: Sunday, December 27, 2009 4:36 PM
> To: Erez Shitrit
> Cc: kvm@vger.kernel.org
> Subject: Re: unable to assign devices with VT-d in KVM
>
> On 12/27/2009 03:51 PM, Avi Kivity wrote:
> > Can you try adding -cpu qemu64,vendorid=GenuineIntel?
>
> Sorry, the correct option is -cpu qemu64,vendor=GenuineIntel.
>
> --
> error compiling committee.c: too many arguments to function
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-12-29 5:31 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
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 [this message]
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=200912291330.09939.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=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.