diff options
Diffstat (limited to 'results/classifier/118/device/1902306')
| -rw-r--r-- | results/classifier/118/device/1902306 | 73 |
1 files changed, 73 insertions, 0 deletions
diff --git a/results/classifier/118/device/1902306 b/results/classifier/118/device/1902306 new file mode 100644 index 00000000..1c4bb712 --- /dev/null +++ b/results/classifier/118/device/1902306 @@ -0,0 +1,73 @@ +device: 0.942 +virtual: 0.893 +PID: 0.875 +graphic: 0.845 +peripherals: 0.845 +ppc: 0.816 +performance: 0.802 +files: 0.793 +network: 0.765 +user-level: 0.765 +permissions: 0.749 +debug: 0.746 +vnc: 0.743 +risc-v: 0.741 +architecture: 0.741 +hypervisor: 0.699 +socket: 0.690 +boot: 0.685 +i386: 0.679 +VMM: 0.669 +kernel: 0.657 +x86: 0.644 +register: 0.641 +KVM: 0.630 +semantic: 0.623 +mistranslation: 0.612 +TCG: 0.597 +assembly: 0.592 +arm: 0.452 + +Allow setting usb storage device ID parameters + +Some stubborn software requires certain VID/PID/Serial to authenticate and refuses to start in emulation. This poses a problem with unsupported programs which often require keeping an ancient hardware praying that the USB stick will not die before the (often defunct) company making it. + +Virtualizing such environment is desired. However, QEMU doesn't allow setting VID/PID/Serial/Name of emulated USB devices, but instead uses hardcoded values: https://github.com/qemu/qemu/blob/c99fa56b95a72f6debd50a280561895d078ae020/hw/usb/dev-storage.c#L95 + +This request (including a patch) was already made in 2015 on the list but never got any response: https://lists.nongnu.org/archive/html/qemu-discuss/2015-07/msg00072.html + + +WDYT of adding such functionality? + +The QEMU project is currently moving its bug tracking to another system. +For this we need to know which bugs are still valid and which could be +closed already. Thus we are setting the bug state to "Incomplete" now. + +If the bug has already been fixed in the latest upstream version of QEMU, +then please close this ticket as "Fix released". + +If it is not fixed yet and you think that this bug report here is still +valid, then you have two options: + +1) If you already have an account on gitlab.com, please open a new ticket +for this problem in our new tracker here: + + https://gitlab.com/qemu-project/qemu/-/issues + +and then close this ticket here on Launchpad (or let it expire auto- +matically after 60 days). Please mention the URL of this bug ticket on +Launchpad in the new ticket on GitLab. + +2) If you don't have an account on gitlab.com and don't intend to get +one, but still would like to keep this ticket opened, then please switch +the state back to "New" or "Confirmed" within the next 60 days (other- +wise it will get closed as "Expired"). We will then eventually migrate +the ticket automatically to the new system (but you won't be the reporter +of the bug in the new system and thus you won't get notified on changes +anymore). + +Thank you and sorry for the inconvenience. + + +[Expired for QEMU because there has been no activity for 60 days.] + |