RE: Expose vfio device display/migration to libvirt and above, was Re: [PATCH 0/3] sample: vfio mdev display devices.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxxxx] On
> Behalf Of Gerd Hoffmann
> Sent: Monday, May 7, 2018 2:26 PM
> To: Alex Williamson <alex.williamson@xxxxxxxxxx>
> Cc: Neo Jia <cjia@xxxxxxxxxx>; kvm@xxxxxxxxxxxxxxx; Erik Skultety
> <eskultet@xxxxxxxxxx>; libvirt <libvir-list@xxxxxxxxxx>; Dr. David Alan
> Gilbert <dgilbert@xxxxxxxxxx>; Zhang, Tina <tina.zhang@xxxxxxxxx>; Kirti
> Wankhede <kwankhede@xxxxxxxxxx>; Laine Stump <laine@xxxxxxxxxx>;
> Daniel P. Berrange <berrange@xxxxxxxxxx>; Jiri Denemark
> <jdenemar@xxxxxxxxxx>; intel-gvt-dev@xxxxxxxxxxxxxxxxxxxxx
> 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




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux