Hi,
> > Hmm, looking into this. Can't figure how this works. For virtio-net a
> > bunch of properties are defined for virtio-net-device. But they show up
> > (using -device $dev,?) on both virtio-net-device and virtio-net-pci.
> >
> > Trying to do the same for the (already merged) virtio-inp
On Thu, Jun 18, 2015 at 05:44:48PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > > +static Property virtio_input_host_pci_properties[] = {
> > > +DEFINE_VIRTIO_INPUT_PROPERTIES(VirtIOInputPCI, vdev.input),
> > > +DEFINE_PROP_STRING("evdev", VirtIOInputHostPCI, vdev.evdev),
> > > +DEFINE_PR
Hi,
> > +static Property virtio_input_host_pci_properties[] = {
> > +DEFINE_VIRTIO_INPUT_PROPERTIES(VirtIOInputPCI, vdev.input),
> > +DEFINE_PROP_STRING("evdev", VirtIOInputHostPCI, vdev.evdev),
> > +DEFINE_PROP_UINT32("vectors", VirtIOPCIProxy, nvectors, 2),
> > +DEFINE_PROP_END
On Thu, Jun 18, 2015 at 12:11:47PM +0100, Peter Maydell wrote:
> On 18 June 2015 at 10:39, Michael S. Tsirkin wrote:
> > On Thu, Jun 18, 2015 at 11:33:55AM +0200, Gerd Hoffmann wrote:
> >> +static Property virtio_input_host_pci_properties[] = {
> >> +DEFINE_VIRTIO_INPUT_PROPERTIES(VirtIOInputP
On 18 June 2015 at 10:39, Michael S. Tsirkin wrote:
> On Thu, Jun 18, 2015 at 11:33:55AM +0200, Gerd Hoffmann wrote:
>> +static Property virtio_input_host_pci_properties[] = {
>> +DEFINE_VIRTIO_INPUT_PROPERTIES(VirtIOInputPCI, vdev.input),
>> +DEFINE_PROP_STRING("evdev", VirtIOInputHostPCI
On Thu, Jun 18, 2015 at 11:33:55AM +0200, Gerd Hoffmann wrote:
> This allows to assign host input devices to the guest:
>
> qemu -device virtio-input-host-pci,evdev=/dev/input/event
>
> The guest gets exclusive access to the input device, so be careful
> with assigning the keyboard if you have on
This allows to assign host input devices to the guest:
qemu -device virtio-input-host-pci,evdev=/dev/input/event
The guest gets exclusive access to the input device, so be careful
with assigning the keyboard if you have only one connected to your
machine.
Signed-off-by: Gerd Hoffmann
---
hw/in
