Hi,
> > + * Sets the hardware (e.g. PCI) path of the graphics device
> > represented by this QXL interface instance.
>
> So, this comment suggests that the caller might be able to provide a
> path that is not a PCI path. But the implementation below (mostly the
> debug output, I suppose...)
Hey,
On Wed, Oct 10, 2018 at 09:57:39AM -0400, Cole Robinson wrote:
> On 10/09/2018 04:42 PM, Lars Kellogg-Stedman wrote:
> > I'm running libvirt under Fedora 28. I would like to attach a USB
> > device to a VM, but when I select "Redirect USB Device" from the
> > "Virtual Machine" menu in
Hello,
On Tue, Oct 09, 2018 at 02:13:59PM +, MK wrote:
> Hi devels!
>
> I'd like to disable drag and drop of files from Windows to a Linux guest. But
> I like to keep the clipboard sharing functionality.
>
> Is there any option to set this - as I have not found one.
You can disable it
Hi devels!
I'd like to disable drag and drop of files from Windows to a Linux guest. But I
like to keep the clipboard sharing functionality.
Is there any option to set this - as I have not found one.
Thanks.
Martin
___
Spice-devel mailing list
Hi,
> # ./get-xrandr-output :02:03.0 0
> sys path: /sys/class/drm/card0
> sys path device: /sys/class/drm/card0/device
> Device /dev/dri/card0 is at ../../../virtio2
> card addr 'virtio2' does not match requested addr ':02:03.0'
> no card exists
I think you should use this:
On 10/09/2018 04:42 PM, Lars Kellogg-Stedman wrote:
I'm running libvirt under Fedora 28. I would like to attach a USB
device to a VM, but when I select "Redirect USB Device" from the
"Virtual Machine" menu in virt-manager and then select the device, I
get the error:
USB redirection error
On Tue, 2018-10-09 at 14:33 -0500, Jonathon Jongsma wrote:
> On Tue, 2018-10-09 at 15:10 +0200, Lukáš Hrázký wrote:
> > Adds two functions to let QEMU provide information to identify
> > graphics
> > devices and their monitors in the guest:
> >
> > * device path - The path identifying the device
Hi,
> Also, can you respond to Frediano's comments below about e.g. HDMI-A,
> etc? As far as I can tell, libdrm doesn't really give us a canonical
> name for the output, it only gives us a connection type enumeration. I
> borrowed a function from your drminfo utility to construct an output
>
On Tue, 2018-10-09 at 17:14 -0400, Frediano Ziglio wrote:
> > On Tue, 2018-10-09 at 17:24 +0100, Frediano Ziglio wrote:
> > > The idea in version 1 of the protocol was to extend it using the
> > > minor version.
> > > However this was replaced by the usage of capabilities and the
> > > minor
> > >
