Hi
Am 08.09.20 um 08:07 schrieb Gerd Hoffmann:
Also "info usb" just shows a single device. I just copied these lines
from a normal libvirt SCSI setup with two cdroms.
>>>
>>> That is normal, it actually is only one usb device after all ;)
>>
>> I was referring to the posted usb-bot
Am 07.09.20 um 13:48 schrieb Daniel P. Berrangé:
> On Mon, Sep 07, 2020 at 01:45:09PM +0200, Gerd Hoffmann wrote:
...
> Switching back to -drive is out of the question. We've worked very hard
> to eliminate its usage and get to an exclusively -blockdev based solution
> because supporting both
Hi
Am 07.09.20 um 13:45 schrieb Gerd Hoffmann:
>> -device nec-usb-xhci,id=xhci \
>> -device usb-bot,id=scsi0,bus=xhci.0 \
>> -device
>> scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,device_id=drive-scsi0-0-0-0,drive=libvirt-1-format,id=scsi0-0-0-0,bootindex=1
>> \
>> -device
>>
Am 07.09.20 um 08:04 schrieb Gerd Hoffmann:
>> USB disks. The main problem is, that -blockdev mechanism relies
>> on the device type to handle the media type, like ide-cd and
>> ide-hd. But there is just usb-storage.
>
> You can use -device usb-bot + -device scsi-cd ...
So I tried
-blockdev
f Box Experience" (OOBE) part of the
Windows configuration after the install. And the latest ISOs don't
even start in QEMU (5.1 and older) for me on Debian, so I used 1909
instead of the 2004 ISO "releases". I'm running the aarch64 system
QEMU on x86_64 Debian Buster with my current QE
this generates the old driver+device commandline arguments in
the case of USB cdrom devices to make the installer happy.
Signed-off-by: Jan-Marek Glogowski
---
src/qemu/qemu_command.c | 21 ++-
src/qemu/qemu_command.h | 1 +
src/qemu
