Ping? Any information about this bug? (see also the initial bug, #645337)
On 29.01.2012 19:58, Michael Tokarev wrote: > tags 645336 + moreinfo > thanks > > On 14.10.2011 19:26, martin f krafft wrote: >> Package: qemu-kvm >> Version: 1:0.14.1+dfsg-4 >> Severity: normal >> >> Instead of the classic command line switches like -serial and >> -usbdevice, libvirt invokes kvm with the more generic syntax, e.g. >> >> -device serial,… >> -device usb_host,… > > Do you have a reference on this - I mean from libvirt side, > not from qemu[-kvm] side? > > Libvirt usually does it the other way around: it adopts its > code based on changes in qemu. So new devices/syntaxes > appears in qemu first, and only after that they're being > used in libvirt. > > In particular, -device serial does not exist and never did, > but instead the right device is isa-serial, and that one > existed for a very long time. > > For -device usb-host (correct spelling is usb-host not usb_host), > this option exists and works. In order to use it, you have > to declare usb bus first. I verfied it in 0.14 -- > > kvm -usb -device usb-host,vendorid=xx,productid=yy > > works just fine. > >> Unfortunately, kvm does not seem to support those, and the device is >> not made available to the guest. If I manually influence the command >> line and use the classic command line switches, then it works, >> however. > > I'm not sure if I understand what you're saying here. > >> The reason why libvirt uses those generic -device lines is due to >> hotplug support. Apparently -device … is hotpluggable, while >> -usbdevice is not. > > Hot-UN-pluggable you mean? Because you can't hot-plug something > which is already plugged. > > Anyway, all usb devices - regardless if you specified them as > -device usb-foo or -usbfoo or used usb_add at runtime -- all of > them are hot-unpluggable. Ditto for almost all pci devices. > But devices like isa-serial (and anything on isa bus) is not > hot-(un-)pluggable, by definition, because ISA bus does not > support this feature and so there's no way for a guest to > handle it even if it'll be supported by qemu itself. > >> It would be good if kvm would support those generic device >> specifications, not only because it advertises them in its manpage, >> but mostly because libvirt makes use of them already. > > It does already, it looks like. > > Can you provide some more background for all this? > > Thanks! > > /mjt > > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
