Re: [libvirt] Expose vfio device display/migration to libvirt and above, was Re: [PATCH 0/3] sample: vfio mdev display devices.
Hi Gerd,
Can I know your status on the boot display support work? I'm interested to try it in
some real use cases.
Thanks,
Henry
-----Original Message-----
From: intel-gvt-dev [mailto:intel-gvt-dev-bounces@lists.freedesktop.org] On
Behalf Of Gerd Hoffmann
Sent: Monday, May 7, 2018 2:26 PM
To: Alex Williamson <alex.williamson(a)redhat.com>
Cc: Neo Jia <cjia(a)nvidia.com>; kvm(a)vger.kernel.org; Erik Skultety
<eskultet(a)redhat.com>; libvirt <libvir-list(a)redhat.com>; Dr. David Alan
Gilbert <dgilbert(a)redhat.com>; Zhang, Tina <tina.zhang(a)intel.com>; Kirti
Wankhede <kwankhede(a)nvidia.com>; Laine Stump <laine(a)redhat.com>;
Daniel P. Berrange <berrange(a)redhat.com>; Jiri Denemark
<jdenemar(a)redhat.com>; intel-gvt-dev(a)lists.freedesktop.org
Subject: Re: Expose vfio device display/migration to libvirt and above, was Re:
[PATCH 0/3] sample: vfio mdev display devices.
Hi,
> This raises another question, is the configuration of the emulated
> graphics a factor in the handling the mdev device's display option?
> AFAIK, neither vGPU vendor provides a VBIOS for boot graphics, so even
> with a display option, we're mostly targeting a secondary graphics
> head, otherwise the user will be running headless until the guest OS
> drivers initialize.
Right now yes, no boot display for vgpu devices. I'm trying to fix that with
ramfb. There are a bunch of rough edges still and details to hashed out. It'll
probably be uefi only.
cheers,
Gerd