VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1927 - 1929 of 16363)

Ticket Resolution Summary Owner Reporter
#15644 fixed VBoxManage list usbhost fails to correctly identify USB dongle => Fixed in SVN JsT
Description

Here is the output of various commands that might be useful. My report and comments are disclosed below.

$ uname -a
Linux badger 4.6.4-1-ARCH #1 SMP PREEMPT Mon Jul 11 19:12:32 CEST 2016 x86_64 GNU/Linux
$sudo lsusb -vv -d 0658:0200
Bus 001 Device 014: ID 0658:0200 Sigma Designs, Inc. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0658 Sigma Designs, Inc.
  idProduct          0x0200 
  bcdDevice            0.00
  iManufacturer           0 
  iProduct                0 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           67
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              0 
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          1
      CDC ACM:
        bmCapabilities       0x00
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0020  1x 32 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0020  1x 32 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)
$sudo VBoxManage list -l usbhost
...
UUID:               913ce319-f1b5-479b-af24-7e47a0d15b01
VendorId:           0x0058 (0058)
ProductId:          0x0000 (0000)
Revision:           0.0 (0000)
Port:               6
USB version/speed:  2/Full
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.7//device:/dev/vboxusb/001/014
Current State:      Busy
...
$ dmesg
...
[  617.493077] usb 1-3.7: new full-speed USB device number 14 using xhci_hcd
[  617.588369] cdc_acm 1-3.7:1.0: ttyACM0: USB ACM device

I have properly working Virtualbox and full list of USB devices available inside Windows guest OS. The problem I face is that a specific USB serial device 0658:0200 is not properly exposed by "VBoxManage list -l usbhost" and respectively not properly passed-through to Windows guest. All other devices are properly passed-through.

For some reason the (real id) "0658:0200" is detected by the "usbhost" as 0058:0000 (I can verify this by plugging and unplugging the device - this is the only device that is gone and then come back in the "usbhost" list).

Month ago (with an older version of Virtual Box /5.0.x) I was able to passthrough 0658:0200 successfully inside Windows OS. I don't recall doing something differently back then.

#15764 fixed Unknown device (USB pass through) => fixed in SVN/5.1.x JsT
Description

I have reported bug #15644 which was partially fixed. Please take a look there for all reported info and logs.

The problem is that the affected by the bug USB devices (from #15644) are now visible, but still without showing their full name and thus the Windows OS thinks that those devices are new.

For example the device 0658:0200 Sigma Designs, Inc. was recognized as 0058:0000 (lost high byte) now is correctly shown as 0658:0200, but the name "Sigma Designs, Inc." is still shown as "Unknown device".

#684 fixed Password Protecting Host Key Usage => Fixed in SVN Josh Wright
Description

I'd like the ability to lock host-key functions.

Perhaps just the ability to lock a VM into fullscreen mode.

Scenario: Windows guest running on stripped down Debian host, used as a public workstation.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy