similar to: GVT-g - suboptimal user experience

Hello. All features are about usability and simple user experience. 1. Its about local display / dmabuf feature. Currently user needs to use virt-viewer tool. But virt-manager already incorporates graphical console. It would be nice if it could support accelerated gvt-g local display. Preferably with minimum performance overhead. Also virt-manager should allow to use mdev videocard alone,

Could you elaborate a bit more about the first two features? On UEFI VMs support (Windows guest), do you mean enabling Windows VM display on UEFI? Thanks. > -----Original Message----- > From: iGVT-g [mailto:igvt-g-bounces@lists.01.org] On Behalf Of Alex Ivanov > Sent: Friday, April 19, 2019 2:51 AM > To: libvirt-users@redhat.com; igvt-g@lists.01.org; virt-tools-list@redhat.com >

> -----Original Message----- > From: Gerd Hoffmann [mailto:gerd@kraxel.org] > Sent: Thursday, May 9, 2019 3:28 PM > To: Alex Ivanov <gnidorah@ya.ru> > Cc: Yuan, Hang <hang.yuan@intel.com>; libvirt-users@redhat.com; igvt- > g@lists.01.org; virt-tools-list@redhat.com > Subject: Re: [iGVT-g] GVT-g - suboptimal user experience > > Hi, > > > 1. Its

So it looks like this solution is currently not very user friendly. Perhaps Intel could get Red Hat help to make first-class support of gvt feature in virt-manager? 09.05.2019, 10:28, "Gerd Hoffmann" <gerd@kraxel.org>: >   Hi, > >>  1. Its about local display / dmabuf feature. Currently user needs to >>  use virt-viewer tool. But virt-manager already incorporates

Hi, > 1. Its about local display / dmabuf feature. Currently user needs to > use virt-viewer tool. But virt-manager already incorporates graphical > console. It would be nice if it could support accelerated gvt-g local > display. virt-manager and virt-viewer essentially run the same code spice client code: both are using the spice-gtk widget. So, if that isn't working

Use the proper API instead. Fixes: f440c8a572d7 ("drm/i915/gvt/kvmgt: read/write GPA via KVM API") Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gvt/kvmgt.c b/drivers/gpu/drm/i915/gvt/kvmgt.c index 074c4efb58eb..5848400620b4 100644 ---

> Linux migration document. > > * To: samba at sambadotorg, samba-technical at sambadotorg > * Subject: Linux migration document. > * From: Jeremy Allison <jra at sambadotorg> > * Date: Tue, 21 Oct 2003 23:20:58 +0000 > * Cc: jra at sambadotorg > > Hi all, > > If you're looking at a Windows server to Linux & Samba migration

Currently, the Kbuild core manipulates header search paths in a crazy way [1]. To fix this mess, I want all Makefiles to add explicit $(srctree)/ to the search paths in the srctree. Some Makefiles are already written in that way, but not all. The goal of this work is to make the notation consistent, and finally get rid of the gross hacks. Having whitespaces after -I does not matter since commit

> From: Jason Wang > Sent: Thursday, September 12, 2019 5:40 PM > > Mdev bus only support vfio driver right now, so it doesn't implement > match method. But in the future, we may add drivers other than vfio, > one example is virtio-mdev[1] driver. This means we need to add device > id support in bus match method to pair the mdev device and mdev driver > correctly.

Currently, the Kbuild core manipulates header search paths in a crazy way [1]. To fix this mess, I want all Makefiles to add explicit $(srctree)/ to the search paths in the srctree. Some Makefiles are already written in that way, but not all. The goal of this work is to make the notation consistent, and finally get rid of the gross hacks. Having whitespaces after -I does not matter since commit

On Mon, 23 Sep 2019 21:03:26 +0800 Jason Wang <jasowang at redhat.com> wrote: > Mdev bus only supports vfio driver right now, so it doesn't implement > match method. But in the future, we may add drivers other than vfio, > one example is virtio-mdev[1] driver. This means we need to add device > class id support in bus match method to pair the mdev device and mdev > driver

> From: Jason Wang > Sent: Tuesday, September 24, 2019 9:53 PM > > Mdev bus only supports vfio driver right now, so it doesn't implement > match method. But in the future, we may add drivers other than vfio, > the first driver could be virtio-mdev. This means we need to add > device class id support in bus match method to pair the mdev device > and mdev driver

On Thu, 24 Oct 2019 11:27:36 +0800 Jason Wang <jasowang at redhat.com> wrote: > On 2019/10/24 ??5:42, Alex Williamson wrote: > > On Wed, 23 Oct 2019 21:07:47 +0800 > > Jason Wang <jasowang at redhat.com> wrote: > > > >> Mdev bus only supports vfio driver right now, so it doesn't implement > >> match method. But in the future, we may add

On Thu, 24 Oct 2019 11:27:36 +0800 Jason Wang <jasowang at redhat.com> wrote: > On 2019/10/24 ??5:42, Alex Williamson wrote: > > On Wed, 23 Oct 2019 21:07:47 +0800 > > Jason Wang <jasowang at redhat.com> wrote: > > > >> Mdev bus only supports vfio driver right now, so it doesn't implement > >> match method. But in the future, we may add

On Mon, 4 Nov 2019 20:39:47 +0800 Jason Wang <jasowang at redhat.com> wrote: > Mdev bus only supports vfio driver right now, so it doesn't implement > match method. But in the future, we may add drivers other than vfio, > the first driver could be virtio-mdev. This means we need to add > device class id support in bus match method to pair the mdev device > and mdev

Hi list! I?m connecting a Brasilian voip (- gvt.com.br -) provider through my asterisk box and using the register command from sip.conf. What I can?t understand is why my unit sends a new registration message every minute! And every time my asterisk box sends a registration, it gots a sucessful response, and shows de message: "Oct 14 16:48:22 NOTICE[4090]: chan_sip.c:8742

On Wed, 23 Oct 2019 21:07:47 +0800 Jason Wang <jasowang at redhat.com> wrote: > Mdev bus only supports vfio driver right now, so it doesn't implement > match method. But in the future, we may add drivers other than vfio, > the first driver could be virtio-mdev. This means we need to add > device class id support in bus match method to pair the mdev device > and mdev

On Wed, 23 Oct 2019 21:07:47 +0800 Jason Wang <jasowang at redhat.com> wrote: > Mdev bus only supports vfio driver right now, so it doesn't implement > match method. But in the future, we may add drivers other than vfio, > the first driver could be virtio-mdev. This means we need to add > device class id support in bus match method to pair the mdev device > and mdev

On Tue, 24 Sep 2019 21:53:26 +0800 Jason Wang <jasowang at redhat.com> wrote: > Mdev bus only supports vfio driver right now, so it doesn't implement > match method. But in the future, we may add drivers other than vfio, > the first driver could be virtio-mdev. This means we need to add > device class id support in bus match method to pair the mdev device > and mdev

> From: Jason Wang > Sent: Thursday, September 12, 2019 5:40 PM > > Currently, except for the crate and remove. The rest fields of > mdev_parent_ops is just designed for vfio-mdev driver and may not help > for kernel mdev driver. So follow the device id support by previous > patch, this patch introduces device specific ops which points to > device specific ops (e.g vfio