On Wed, Apr 15, 2015 at 04:01:46PM +0100, Zeeshan Ali (Khattak) wrote: > I don't think the inconsistency is significant enough and is not > actually introduced by these patches themselves. Libosinfo is just > saying "these devices are supported by the OS" with these patches and > if Boxes or qemu (or other apps) add a slightly different device based > on this information, that is not a fault of libosinfo. Yes, this would be Boxes/qemu faults for not following what libosinfo told it to and adding a USB mouse when libosinfo never told it this specific mouse was supported. In this patch what you really are trying to say is that it's able to support any USB mouse, not the VMWare one. > > > So if we can do without because the bug is elsewhere, it's better imo. > > That would mean very slow keyboard and mouse in windows 8.1. > > The bug of XP installer crashing is not exactly somewhere else since > we at least know that it does not happen if you only remove USB mouse > and keyboard from Boxes generated domain configuration. As I said, its > likely a combination, USB mouse and keyboard being a part of that. Yes, but as Windows installs do not always crash with a USB mouse, it would be nice to narrow it down and report it against the right component (QEMU? something else?) rather than adding API in libosinfo to just paper over it. Christophe
Attachment:
pgpTSjzD6gX9b.pgp
Description: PGP signature
_______________________________________________ Libosinfo mailing list Libosinfo@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libosinfo
