fails to handle a usb serial port with a specific vendorid
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
If I run qemu-system-i386 with arguments
-usb -usbdevice serial:
(this is what the documentation says about how I shoud add a usb device which has a serial port interface and which has a specific vendor id, I used the documentation located here:
http://
), it says
char device redirected to /dev/pts/
qemu-system-i386: -usbdevice serial:
Aborted
and exits. Moreover, if I try to add such a device to a running machine by typing usb_add serial:
char device redirected to /dev/pts/
Aborted
to the terminal where I run it from and exits. To the quest OS this looks like a power failure which causes all the programs inside the virtual machine to lose their unsaved data.
I have tested this with qemu-1.5.0-rc2, actually, the issue occured in a similar way since 1.0.1, but did not occur in 0.11.1.
The issue is reproducible always, even if I don't specify any hard disk in the command line, i. e.
$ qemu-system-i386 -usb -usbdevice serial:
, so I believe it is guest OS -independent.
Changed in qemu: | |
status: | Fix Committed → Fix Released |
Hi,
>> (this is what the documentation says about how I shoud add a usb device which has a serial port interface and which has a specific vendor id, I used the documentation located here: qemu.weilnetz. de/qemu- doc.html <something> (label usbserial0) vendorid= 1221:pty: Property '.vendorid' not found device- use.txt.
>> http://
>> ), it says
>> char device redirected to /dev/pts/
>> qemu-system-i386: -usbdevice serial:
>> Aborted
> [...]
>
> Regression; this definitely worked when I wrote docs/qdev-
> Not a release blocker, since it regressed a long time ago (v0.12).
Guess the docs should be updated, unless someone can come up with a
reasonable use case for the vendorid + deviceid properties.
cheers,
Gerd