From: listmail <listmail@triad.rr.com>
To: Mark Hurenkamp <mark.hurenkamp@xs4all.nl>
Cc: xen-devel@lists.xensource.com
Subject: Re: vt-d p7p55d evo
Date: Sun, 04 Apr 2010 10:33:42 -0400 [thread overview]
Message-ID: <4BB8A346.5020007@triad.rr.com> (raw)
In-Reply-To: <69A986FE-7EE1-48AD-9829-717094C9A49A@xs4all.nl>
Mark Hurenkamp wrote:
>> I'm still pretty new to Xen so it could very well be that I've
>> misunderstood the requirements for certain capabilities. I thought
>> one of the wiki's had stated that to pass through to an hvm guest you
>> have to have VT-d though. Is there something specific that I which
>> can indicate its status after boot?
>>
>> bios: 1207
>> cpu: i7 860
>> grub2: http://pastebin.ca/1856369
>> xm dmesg: http://pastebin.ca/1856370
>> xm info: http://pastebin.ca/1856372
>> hvm cfg: http://pastebin.ca/1856376
>> I think I compiled the linux kernel at xen/stable git commit
>> 221c4dbf86 given the timestamp in xm info (all done same time frame)
>
> From your earlier mail, it was not clear wether you were indeed using
> hvm, and that xen enabled vt-d properly.
> From your xm dmesg, and xm info, it is clear that iommu is indeed
> enabled for you, something which i've not been able to achieve with my
> board.
> Could the CPU make a difference here? I'm on a i5 750, and notice you
> are using an i7 860....
>
> I'll see if i can do some more experiments with my setup, perhaps
> switching back a few changesets to 4.0-rc8.
> I'm not sure if the kernel makes a difference, but i'll see if i can
> match your configuration as close as possible.
>
> Thanks for your input!
>
>
> Mark.
>
according to this chart (and thread) the i5 doesn't support VT-d,
http://i683.photobucket.com/albums/vv199/OvrClkr/i5_chart.png
link source: http://www.tomshardware.com/forum/274342-28-tomshardware
next prev parent reply other threads:[~2010-04-04 14:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BB6B79D.3070305@triad.rr.com>
2010-04-03 22:46 ` vt-d p7p55d evo Mark Hurenkamp
2010-04-04 6:14 ` listmail
2010-04-04 11:28 ` Mark Hurenkamp
2010-04-04 14:33 ` listmail [this message]
2010-04-04 18:26 ` Mark Hurenkamp
2010-04-05 21:24 ` Sander Eikelenboom
2010-04-08 23:57 ` Mark Hurenkamp
2010-04-11 1:30 ` Re: vt-d p7p55d evo: Success Mark Hurenkamp
2010-04-11 2:02 ` listmail
2010-04-11 11:18 ` Pasi Kärkkäinen
2010-04-11 13:50 ` Pasi Kärkkäinen
2010-04-11 18:50 ` listmail
2010-04-12 6:55 ` Dietmar Hahn
2010-04-12 7:54 ` Pasi Kärkkäinen
2010-04-12 8:34 ` Dietmar Hahn
2010-04-12 13:04 ` listmail
2010-04-12 13:24 ` Dietmar Hahn
2010-04-12 7:25 ` Pasi Kärkkäinen
2010-04-12 13:18 ` listmail
2010-04-16 0:57 ` listmail
2010-04-18 19:50 ` Mark Hurenkamp
2010-04-11 18:53 ` listmail
2010-04-12 7:01 ` Pasi Kärkkäinen
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=4BB8A346.5020007@triad.rr.com \
--to=listmail@triad.rr.com \
--cc=mark.hurenkamp@xs4all.nl \
--cc=xen-devel@lists.xensource.com \
/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.