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

On Fri, Jul 20, 2018 at 04:56:15AM +, Yuan, Hang wrote: > Hi Gerd, > > Can I know your status on the boot display support work? I'm interested to > try it in some real use cases. https://git.kraxel.org/cgit/qemu/log/?h=sirius/ramfb-vfio Most of the bits needed (general ramfb support) is

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

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? &g

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

On Thu, 10 May 2018 13:00:29 +0200 Erik Skultety wrote: > ... > > > > Now, if we (theoretically) can settle on easing the restrictions Alex > > > has mentioned, we in fact could introduce a QMP command to probe > > > these devices and provide libvirt with useful information

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

... > > Now, if we (theoretically) can settle on easing the restrictions Alex > > has mentioned, we in fact could introduce a QMP command to probe > > these devices and provide libvirt with useful information at that > > point in time. Of course, since the 3rd party vendor is "de-coupled" > >

Re: [libvirt] 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,

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

Hi, > Maybe some guiding questions: > > - Will dma-buf always require GL support? Yes. > - Does GL support limit our ability to have a display over a remote >connection? Currently yes, althrough the plan is to support gl display remotely in spice. The workflow will be completely

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

On Fri, 4 May 2018 10:16:09 +0100 Daniel P. Berrangé wrote: > On Thu, May 03, 2018 at 12:58:00PM -0600, Alex Williamson wrote: > > Hi, > > > > The previous discussion hasn't produced results, so let's start over. > > Here's the situation: > > > > - We currently have

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

On Fri, 4 May 2018 09:49:44 +0200 Erik Skultety wrote: > On Thu, May 03, 2018 at 12:58:00PM -0600, Alex Williamson wrote: > > Hi, > > > > The previous discussion hasn't produced results, so let's start over. > > Here's the situation: > > > > - We currently have kernel and

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

On Thu, May 03, 2018 at 12:58:00PM -0600, Alex Williamson wrote: > Hi, > > The previous discussion hasn't produced results, so let's start over. > Here's the situation: > > - We currently have kernel and QEMU support for the QEMU vfio-pci >display option. > > - The default for this option

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

On Thu, May 03, 2018 at 12:58:00PM -0600, Alex Williamson wrote: > Hi, > > The previous discussion hasn't produced results, so let's start over. > Here's the situation: > > - We currently have kernel and QEMU support for the QEMU vfio-pci >display option. > > - The default for this option is

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

Hi, The previous discussion hasn't produced results, so let's start over. Here's the situation: - We currently have kernel and QEMU support for the QEMU vfio-pci display option. - The default for this option is 'auto', so the device will attempt to generate a display if the underlying