xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Gordan Bobic <gordan@bobich.net>
To: singapore.mr.teo.en.ming@gmail.com
Cc: xen-users@lists.xen.org, Casey DeLorme <cdelorme@gmail.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: Is my Intel HD Graphics 4600 Xen VGA Passthrough to Windows 8 Enterprise HVM domU Considered Successful?
Date: Fri, 19 Jul 2013 13:12:07 +0100	[thread overview]
Message-ID: <4bea5b0b00d6302c924bc91c89f287a9@mail.shatteredsilicon.net> (raw)
In-Reply-To: <51E924EC.4060408@gmail.com>

 On Fri, 19 Jul 2013 19:37:16 +0800, "Singapore Citizen Mr. Teo En Ming 
 (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com> wrote:

>>>>>>> My Windows 8 Enterprise HVM domU configuration is as follows. I 
>>>>>>> have
>>>>>>> to *disable* gfx_passthru, that is, gfx_passthru=0. Please take 
>>>>>>> note.
>>>>>>
>>>>>> [...]
>>>>>>
>>>>>>> So is my Intel HD Graphics 4600 Xen VGA passthrough to Windows 
>>>>>>> 8
>>>>>>> Enterprise HVM domU considered successful?
>>>>>>
>>>>>> If it works, it's successful.
>>>>>>
>>>>>>> I cannot enable gfx_passthru, that is, gfx_passthru=1. If I 
>>>>>>> enable
>>>>>>> gfx_passthru, Windows 8 Enterprise HVM domU would start for a 
>>>>>>> few
>>>>>>> seconds, then the LCD monitor would go into power save mode 
>>>>>>> (blank
>>>>>>> screen) *forever*.
>>>>>>>
>>>>>>> Please advise me on how I can get VGA passthrough to work with
>>>>>>> gfx_passthru=1.
>>>>>>
>>>>>> Can you elaborate why exactly do you need to have that GPU 
>>>>>> passed
>>>>>> through as primary? Primary GPU passthrough has always been
>>>>>> problematic because domU has to re-post the card's BIOS which
>>>>>> has always been problematic.
>>>>>>
>>>>>> The only difference in the general case is that with 
>>>>>> gfx_passthru=1
>>>>>> you get to see the POST and boot information on the monitor
>>>>>> connected to the GPU. With gfx_passthry=0 you can only see this
>>>>>> in the VNC session connected to the virtual primary VGA card. In
>>>>>> the vast majority of cases seeing the POST and boot animation
>>>>>> isn't useful enough to be worth bothering with.
>>>>>>
>>>>>> I have a working setup with 2x Quadro cards, each passed through
>>>>>> as secondary (gfx_passthru=0) to different domUs, with separate
>>>>>> mice/keyboards passed through to each domU (multi-seat gaming
>>>>>> rig), and that works lovely (only limitation being 2GB of RAM
>>>>>> for each domU until I get around to upgrading to 4.3).
>>>>>>
>>>>>> Unless you have a very compelling reason to use gfx_passthru=1
>>>>>> I suggest you don't bother even trying.
>>>>>>
>>>>>> Gordan
>>>>>>
>>>>>
>>>>> Dear Gordan,
>>>>>
>>>>> I want to use the monitor connected to Intel HD Graphics 4600
>>>>> directly. I don't want to use a VNC session to connect to the 
>>>>> Windows
>>>>> 8 Enterprise HVM domU.
>>>>>
>>>>> Thank you very much.
>>>>
>>>> You only need VNC for the POST. Once Windows boots up you should 
>>>> be
>>>> be able to get all your display output on the physical screen.
>>>> Disable the virtual VGA interface in device manager if you have
>>>> to - I've found that is sometimes necessary to get the physical
>>>> GPU working properly.
>>>>
>>>> Gordan
>>>>
>>>
>>> Dear Gordan,
>>>
>>> How do I disable the virtual display adapter in Windows 8 
>>> Enterprise
>>> HVM domU? I see nothing on the physical screen at all.
>>
>> Have you tried going into your desktop/resolution settings and
>> extending your desktop to the physical monitor?
>>
> How do I do that? What are the steps? Please elaborate. Please show
> me any screenshots, if any.

 Sorry, that's a Windows question and that is outside of my area of
 expertise.

 Gordan

  parent reply	other threads:[~2013-07-19 12:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51E9147B.6040900@gmail.com>
2013-07-19 10:42 ` Is my Intel HD Graphics 4600 Xen VGA Passthrough to Windows 8 Enterprise HVM domU Considered Successful? Gordan Bobic
2013-07-19 10:56   ` Singapore Citizen Mr. Teo En Ming (Zhang Enming)
2013-07-19 11:02     ` Gordan Bobic
2013-07-19 11:15       ` Singapore Citizen Mr. Teo En Ming (Zhang Enming)
2013-07-19 11:31         ` Gordan Bobic
2013-07-19 11:37           ` Singapore Citizen Mr. Teo En Ming (Zhang Enming)
2013-07-19 11:58             ` Pasi Kärkkäinen
2013-07-19 12:12             ` Gordan Bobic [this message]
2013-07-19 12:31             ` Andrew Bobulsky
2013-07-19 13:16               ` Singapore Citizen Mr. Teo En Ming (Zhang Enming)
2013-07-19 14:19                 ` Singapore Citizen Mr. Teo En Ming (Zhang Enming)
2013-07-19 14:45                   ` Pasi Kärkkäinen
2013-07-19 16:43                     ` Singapore Citizen Mr. Teo En Ming (Zhang Enming)
2013-07-19 16:54                       ` Pasi Kärkkäinen
2013-07-19 17:02                         ` Singapore Citizen Mr. Teo En Ming (Zhang Enming)
2013-07-19 10:36 Singapore Citizen Mr. 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=4bea5b0b00d6302c924bc91c89f287a9@mail.shatteredsilicon.net \
    --to=gordan@bobich.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=cdelorme@gmail.com \
    --cc=singapore.mr.teo.en.ming@gmail.com \
    --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).