Virtualbox and KVM/qemu cannot connect USB-devices

[vaxinf]

For my project I need to access an external USB-DVD-drive to my x86-OVMS system.

I've checked the connection with a virtual windows 11 system and I can access the DVD-drive without problems. So I'm sure that the x86-OVMS system is the problem. Are there any plan to add the USB-connectivity to the x86 version?

A not happy vms fan
Eberhard

[cct]

For my project I need to access an external USB-DVD-drive to my x86-OVMS system.

I've checked the connection with a virtual windows 11 system and I can access the DVD-drive without problems. So I'm sure that the x86-OVMS system is the problem. Are there any plan to add the USB-connectivity to the x86 version?

A not happy vms fan
Eberhard

Interesting, I am using KVM/QEMU and ity has no problem with a USB NIC as a bridged device.

In the past Virtual box on a desktop PC, ISR you could present any CD/DVD drive, certainly with Linux

[vaxinf]

Your solution is not what I need:

I have to passthrough the USB-connection to the virtual OVMS system.

[alexwong]

I configured a USB DVD on my OpenVMS guest vm in VB and I could see DKA100: in VMS, but when I tried to MOU/FOR a Windows DVD, the process hung and became really wasted (RWAST) when I tried to kill it. I will look for an ODS disk and try again but I suspect there is some emulation issue between VB-CDROM and VMS CD drivers.

[m_detommaso]

Environment: VirtualBox Version 7.0.14 r161095 (Qt5.15.2) + Mircrosoft Windows 10 Version 22H2 (OS Build 19045.4291):

I have always configured a physical USB DVD driver in the following way; I can mount the volume (file system 11) and access the data it contains from VMS without problems.

/Maurizio

[alexwong]

I found if it's the first time you plug in a USB DVD drive, VB does not see it until you refresh the device list. Select it, mark passthrough and OpenVMS will mount the drive properly.

$ mou/for dka300:
$ show dev/full dka300:
V922$DKA300: Mounted alloc 0 0 1 1
foreign wrtlck
$ dum/block=(start:1000,end:1000) dka300:
Dump of device DKA300: on 6-MAY-2024 09:06:42.56
Logical block number 1000 (000003E8), 512 (0200) bytes
C933F9F7 48484589 44C03345 99482056 V H.E3ÀD.EHHœù3É 000000
6B4CC18B 28568B48 3274D285 45D88B48 H.ØE.Òt2H.V(.ÁLk 000010

[vaxinf]

Yes! Now I see the drive as described but the dvd-writer of OVMS doesn't work:

$ copy/rec/format LD1.DSK dka100:
VSI OpenVMS CD-R/RW and DVD+R/RW Utility, V1.0-3
Copyright VMS Software, Inc.

Output device vendor: VBOX
Output device product name: CD-ROM
Output device revision: 1.0
%CDDVD-I-WRTMEDCAP, Writable medium capacity is 9180412 blocks
Commencing media format operation
%CDDVD-I-FMTMEDCAP, Formattable medium capacity is 9180416 blocks
Output medium format: DVD+RW
Synchronizing with output device cache
Unable to complete processing

%SYSTEM-F-MEDOFL, medium is offline

[alexwong]

I got the same error too writing a 2MB ISO9660 file, attached diag output. The failure looks like in SYNCHRONIZE_CACHE. Taking a wild guess but maybe the optical interface took too long or hung and VMS driver thinks device gone offline and timed out? Need VSI advice here I think.

[vaxinf]

I've checked the KVM/qemu environment.

It is only possible to connect a USB-DVD drive through a USB-passthrough connection. This works for Windows and for linux. I can successfully burn images in that virtual environment.

Only the Virtualbox environment supports direct windows drives.

I cannot understand why the OpenVMS x86 is unable to use a USB-connection!
USB works fine under Alpha- and IA64/Itanium-OpenVMS and USB is not a exotic device.

If it's true that the DK-solution is not appropriate for the burning process VSI should start the implementation
of the USB-connection for OVMS x86.

[sms]

Code: Select all

> I cannot understand why the OpenVMS x86 is unable to use a
> USB-connection!
> USB works fine under Alpha- and IA64/Itanium-OpenVMS and USB is not a
> exotic device.

   USB on Alpha and IA64 involved actual USB hardware (which would have
been tested on actual DEC/Compaq/HP[E] systems), not virtual USB
hardware.  I know nothing, but I can imagine that this difference might
be significant.