xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>
To: Pavel Mateja <pavel@netsafe.cz>,
	"xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>
Subject: Re: [SUCCESS] Xen 4.2-unstable Changeset 25099: VGA Passthrough to Windows 8 Consumer Preview HVM domU
Date: Mon, 26 Mar 2012 20:40:49 +0800	[thread overview]
Message-ID: <4F7063D1.5090208@gmail.com> (raw)
In-Reply-To: <201203261423.56695.pavel@netsafe.cz>

On 26/03/2012 20:23, Pavel Mateja wrote:
>> On 26/03/2012 17:15, Pavel Mateja wrote:
>>>> Dear Xen users, developers and David Techer,
>>>>
>>>> I have just downloaded, compiled, and installed Xen 4.2-unstable
>>>> Changeset *_25099_* with Xen VGA Passthrough patches. Xen VGA
>>>> Passthrough to Windows 8 Consumer Preview HVM domU is successful. Or I
>>>> should say *PARTIALLY* successful. Why? Please see the screenshots
>>>> below.
>>> Hi,
>>> which CPU do you have? Intel E6300?
>>> Did you notice that CPU doesn't support VT-d?
>> Dear Pavel Mateja,
>>
>> My CPU is Intel Pentium Dual Core E6300 2.8 GHz which supports Intel
>> Virtualization Technology, i.e. VT-x, not VT-d.
>>
>> BUT, my Intel DQ45CB desktop motherboard supports Intel VT-d. The
>> motherboard BIOS also has VT-d option.
>>
>> Thank you very much.
> Hi again,
> I'm affraid you have to cross-reference
> http://processormatch.intel.com/CompDB/SearchResult.aspx?BoardName=DQ45CB
> and
> http://ark.intel.com/search/advanced?VTD=true
Dear Pavel Mateja,

I can confirm my Intel Pentium Dual Core E6300 2.8 GHz supports VT-x and 
my Intel DQ45CB desktop board and motherboard BIOS supports VT-d. Would 
you like to have a photo screenshot of the motherboard BIOS showing the 
VT-d option? This is concrete evidence showing that my hardware 
configuration supports VT-d. I can even post a video if you want it.

Thank you very much.

-- 
Yours sincerely,

Mr. Teo En Ming (Zhang Enming)
Singapore

  reply	other threads:[~2012-03-26 12:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25  3:06 [SUCCESS] Xen 4.2-unstable Changeset 25099: VGA Passthrough to Windows 8 Consumer Preview HVM domU Teo En Ming (Zhang Enming)
2012-03-25 13:42 ` Re : " David TECHER
2012-03-25 13:50   ` Teo En Ming (Zhang Enming)
2012-03-25 13:56     ` Teo En Ming (Zhang Enming)
2012-03-25 14:00       ` Re : " David TECHER
2012-03-25 13:59     ` David TECHER
2012-03-26  1:19       ` Teo En Ming (Zhang Enming)
2012-03-26  9:15 ` Pavel Mateja
2012-03-26 12:09   ` Teo En Ming (Zhang Enming)
2012-03-26 12:23     ` Pavel Mateja
2012-03-26 12:40       ` Teo En Ming (Zhang Enming) [this message]
     [not found]         ` <4F707A1C.5060207@adiumentum.com>
2012-03-26 15:00           ` [Xen-users] " Teo En Ming (Zhang Enming)
2012-03-26 15:49             ` Pasi Kärkkäinen
2012-03-26 16:40               ` Teo En Ming (Zhang Enming)

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=4F7063D1.5090208@gmail.com \
    --to=singapore.mr.teo.en.ming@gmail.com \
    --cc=pavel@netsafe.cz \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-users@lists.xen.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;
as well as URLs for NNTP newsgroup(s).