Is kvmgt display support compatible with q35?

[Alex Williamson]

On Mon, 15 Oct 2018 10:28:31 +0800
Zhenyu Wang <zhenyuw at linux.intel.com> wrote:

> On 2018.10.12 16:22:56 -0600, Alex Williamson wrote:
> > Hi,
> > 
> > I've installed Windows 10 (1803 September 2018 update) into two
> > separate GVT-g VMs, one a 440FX/SeaBIOS configuration and the other a
> > Q35/OVMF configuration.  I've made the two VMs as similar as I possibly
> > can other than the machine and firmware settings.  XML for each is
> > attached.  I'm also testing Gerd's ramfb support, which explains the
> > driver override and additional hostdev ramfb option for each.
> > 
> > The 440FX/SeaBIOS VM works well, I installed the 15.40.41.5058 driver
> > (host is an i7-5600U with Intel HD Graphics 5500).  I'm able to get to
> > the Intel Graphics Properties and Graphics Options menus, and
> > everything behaves as I'd expect.
> > 
> > With the Q35/OVMF VM, the VM display goes blank as soon as Windows
> > updates the graphics driver after install, I need to swap to an
> > emulated graphics device and install TightVNC server in the VM for
> > access.  Installing the same driver as above does not resolve the
> > display issue.  On boot, the display via virt-manager/virt-viewer
> > is frozen with TianoCore boot graphic and halted Windows dots
> > animation.  Running a Unigine test in the VM suggests the vGPU is
> > working properly (connected via in-guest VNC server), but I don't get
> > the Graphics Properties and Graphics Options menus, and of course the
> > display option seemingly stops working.  Do I have a configuration
> > issue preventing display from working properly or is there something
> > about a Q35/OVMF configuration that prevents the display from working?
> > Thanks,
> >   
> 
> AFAIK, windows display still has problem with OVMF that our previous
> proposal to fix this was not taken. Cc Henry & Tina to double check.

Oh right, the opregion support is still SeaBIOS only.  Is that the only
known barrier I'm hitting here?  Thanks,

Alex