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 02:14:50 -0400 [thread overview]
Message-ID: <4BB82E5A.4030400@triad.rr.com> (raw)
In-Reply-To: <CB8BCF9C-52DE-4608-A46D-2253463536CE@xs4all.nl>
Mark Hurenkamp wrote:
> Hi,
>
>
>> I'm not a subscriber to xen-devel yet, but did see your post about
>> the evo and iommu not working. Within the last week I have
>> installed a xen 4.0rc8 and xen/stable clone kernel 2.6.32.10 and boot
>> ok with iommu=1 and have also successfully passed through a tv tuner
>> card tonight which modules did load for. I did have one weird quirk
>> though. I haven't tested the card in the domu yet. Anyway if you
>> want to discuss this further then reply back.
>
> Are you sure you are using VT-d here (are you using hvm loader)? I'd
> be very interested to know what Bios version you are using, what your
> 'xm dmesg' and 'xm info' output is (after boot), and the xen
> configuration file for your VM.
> Cause although my system can boot fine with enabled iommu now, it is
> simply switched off by xen at boottime... Did you do something special
> to force it to on? Do you have any patches installed?
> Btw, passthrough of a tuner device to a pvm domU is not a problem
> here, but that does not require VT-d (nor VT-x).
> Did you manage to passthrough a device to Windows?
> My ultimate goal is to passthrough a (secondary) usb card, and a
> (secondary) graphics card, to a Windows hvm.
>
>
> Mark.
>
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)
next prev parent reply other threads:[~2010-04-04 6:14 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 [this message]
2010-04-04 11:28 ` Mark Hurenkamp
2010-04-04 14:33 ` listmail
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=4BB82E5A.4030400@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).