Thank you for looking into this, Gerd. Your recent patch now correctly
identifies my keyboard and everything seems to be working well.
On Tue, Apr 12, 2016 at 2:03 AM, Gerd Hoffmann wrote:
> On Di, 2016-04-12 at 00:33 -0700, William Green wrote:
> > Using latest git:
> >
> >
I confirm that the vendor_id works great with libvirt, however all the
other options included in that commit does not.
Virsh will fail to start the host with runtime, vpindex and reset (though
it does work with qemu command-line).
Should that deserve a bug report?
2016-04-15 7:45 GMT+02:00
That depends on where you want to define your network connection. Both is
possible.
Bronek Kozicki schrieb am Sa., 16. Apr. 2016 um
15:51 Uhr:
> On 16/04/2016 14:00, Garland Key wrote:
> > Thanks. Does this have to be listed in a particular part of the virsh
> XML?
> >
> > On
On 16/04/2016 14:00, Garland Key wrote:
Thanks. Does this have to be listed in a particular part of the virsh XML?
On Sat, Apr 16, 2016 at 8:34 AM, Philip Abernethy > wrote:
I've done the same. Bridge created with NM and used by the VM.
On 16/04/2016 13:34, Philip Abernethy wrote:
I've done the same. Bridge created with NM and used by the VM. You
should be able to just select the bridge device. That's the resulting
XML for me:
default
278badf4-d33e-493e-b604-083b3dcc2804
Here is xml of my VM, using "br0" bridge
I've done the same. Bridge created with NM and used by the VM. You should
be able to just select the bridge device. That's the resulting XML for me:
default
278badf4-d33e-493e-b604-083b3dcc2804
Garland Key schrieb am Sa., 16. Apr. 2016 um
14:30 Uhr:
>
I'm running Arch with Plasma 5 and Network Manager. AFAIK, the
virt-manager package on Arch has broken networking. I've successfully
created a bridge using Network Manager, but I can't seem to add the bridge
in virt-manager or via virsh.
Is this possibe? I need it for Synergy. My mobo has two