VirtualBox

Ticket #8801 (new defect)

Opened 3 years ago

Last modified 7 months ago

only printable Serial-Number allowed for the USB-filter

Reported by: BjoernC Owned by:
Priority: minor Component: USB
Version: VirtualBox 4.0.6 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description

Hi, when i want to make an permanent filter for an USB-Device, which has none-printable characters, the whole VM will crash at the next startup. The failure which is shown, said that in line X a wrong value has been readed. For a workaround, the serial-number could be deleted and the VM will start. The USB-device was an ST-Link from STMicroelectronics.

Attachments

VM.png Download (70.3 KB) - added by BjoernC 3 years ago.
in this screenshot you can see the none-printable characters an how i had added this device to the filter
usbhost.txt Download (1.8 KB) - added by BjoernC 3 years ago.
The output of the command VBoxManage list usbhost
Vboxversion.png Download (12.9 KB) - added by BjoernC 3 years ago.
VBoxversion (screenshot taken of the helpmenue -> About)
virtualBox.png Download (30.5 KB) - added by BjoernC 3 years ago.
Main error-message of VBox

Change History

Changed 3 years ago by BjoernC

in this screenshot you can see the none-printable characters an how i had added this device to the filter

comment:1 Changed 3 years ago by frank

Can you add the output of VBoxManage list usbhost?

Changed 3 years ago by BjoernC

The output of the command VBoxManage list usbhost

comment:2 Changed 3 years ago by BjoernC

the output of the command, is added in the file: usbhost.txt

comment:3 Changed 3 years ago by frank

Thanks. Are you sure that you are using VBox 4.0.6? Sorry for asking, but in 4.0.4 we fixed a related bug so I want to be sure.

Changed 3 years ago by BjoernC

VBoxversion (screenshot taken of the helpmenue -> About)

comment:4 Changed 3 years ago by frank

Thanks. When this crash happens, which process crashes, the VM process (VirtualBox) or the VBoxSVC daemon? Could you provide me a Core_dump?

Changed 3 years ago by BjoernC

Main error-message of VBox

comment:5 Changed 3 years ago by BjoernC

I've tried to generate the dumpfiles, but there are no entries. But the Problem ist not, that VBox crashes. The main Problem is, that VBox is not able to read the *.vbox file. The screenshot, which shows the error-message i will attach to this error report.

comment:6 Changed 3 years ago by Donuts

I am experiencing this problem with VirtualBox 4.0.12 on Xubuntu 9.10 x86 host.

I have a Compro VideoMate C200 USB video capture device, USB VID:PID 185B:0200. It seems to have garbage/binary/non-printable characters for its serial number. lsusb -vv shows a couple of garbage characters for the iSerial field.

The problem seems to be that VirtualBox writes the garbage/binary characters to the .vbox config file. Then when you next start the VirtualBox Manager, it refuses to start the VM. I got a similar error message to the original submitter, along with this text: "PCDATA invalid Char value 3."

Looking at the .vbox file for the VM, there is this line:

<DeviceFilter name="Compro VM C200 [0001]" active="true" vendorId="185b" productId="0200" revision="0001" manufacturer="Compro" product="VM C200" serialNumber="&#xF2; " remote="0"/>

(Note the serialNumber field contains garbage which may not reproduce properly. The invalid character shows as a little box with 00 03 in with the font I'm using here.)

After manually editing the .vbox file to remove the serialNumber field from that line, I could use the VM again.

comment:7 Changed 7 months ago by pavel12

I got the same error in VirtualBox v. 4.2.16 on Ubuntu after adding a USB device filter for an STLink/v2. There were strange looking character in the "serialNumber" field. After I manually deleted the affected lines from the .vbox file, the error would go away.

Last edited 7 months ago by pavel12 (previous) (diff)

comment:8 Changed 7 months ago by michael

If you can reproduce this, could you please post the relevant extract of the .vbox file like the commenter before you? Thanks.

comment:9 Changed 7 months ago by michael

And the error message you get from VirtualBox. Text is sufficient, screen shot not needed.

comment:10 Changed 7 months ago by michael

I have tried and failed to reproduce this by modifying the serial number string read from a USB device on my Ubuntu 13.04 host in the debugger. VirtualBox accepts the string, but simply strips the problematic character when it writes out the .vbox file. If I manually modify the .vbox file to contain a &#x3 character in the string I do prevent VirtualBox from loading it; furthermore the character dropped from the string obviously prevents the filter from being useful. Nonetheless I would be interested to be able to reproduce your error.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use