virtualbox.org

I use a MacBook Pro with Max OS X 10.13.2 running VirtualBox 5.2.4 r119785 Qt5.6.3

Extension Packs: 1
Pack no. 0:   Oracle VM VirtualBox Extension Pack
Version:      5.2.4
Revision:     119785
Edition:      
Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.
VRDE Module:  VBoxVRDP
Usable:       true 
Why unusable:

Code: Select all

Host USB Devices:
UUID:               94992cc1-69b5-4277-9e7f-da5e5ce258c2
VendorId:           0x1058 (1058)
ProductId:          0x0820 (0820)
Revision:           16.18 (1618)
Port:               5
USB version/speed:  0/Super
Manufacturer:       Western Digital
Product:            My Passport 0820
SerialNumber:       575858314543334358455650
Address:            p=0x0820;v=0x1058;s=0x00002ab1df948a3b;l=0x14500000
Current State:      Unavailable

Running XP Pro and Win10 Pro as Guests:

Code: Select all

Name:            XP Pro
Groups:          /
Guest OS:        Windows XP (32-bit)
UUID:            8ed9cd2a-9a86-40b2-9a19-6a581be40973
Config file:     /Users/rs/VirtualBox_VMs/XP Pro/XP Pro.vbox
Snapshot folder: /Users/rs/VirtualBox_VMs/XP Pro/Snapshots
Log folder:      /Users/rs/VirtualBox_VMs/XP Pro/Logs
Hardware UUID:   8187e6dd-9f1b-4946-aa64-a2d11a6ad59e
Memory size:     4096MB
Page Fusion:     off
VRAM size:       128MB
CPU exec cap:    100%
HPET:            off
Chipset:         ich9
Firmware:        BIOS
Number of CPUs:  2
PAE:             off
Long Mode:       off
Triple Fault Reset: off
APIC:            on
X2APIC:          off
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: None
State:           powered off (since 2018-01-07T14:52:31.000000000)
Monitor count:   1
3D Acceleration: on
2D Video Acceleration: on
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
IDE (0, 0): /Users/rs/VirtualBox_VMs/XP Pro/XP Pro-disk001_1.vmdk (UUID: 95912946-7ae1-4f7c-86a9-ec1f27f5f935)
IDE (1, 0): Empty
NIC 1:           MAC: 080027DD2B9A, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82543GC, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: CoreAudio, Controller: AC97, Codec: STAC9700)
Audio playback:  enabled
Audio capture: enabled
Clipboard Mode:  Bidirectional
Drag and drop Mode: Bidirectional
VRDE:            disabled
USB:             enabled
EHCI:            enabled
XHCI:            disabled
Description:
XP Professional
Guest:

Configured memory balloon size:      0 MB

Code: Select all

Name:            Win10_Pro_x64
Groups:          /
Guest OS:        Windows 10 (64-bit)
UUID:            6d3ef6e7-76d4-42e6-af62-89cee6a9a711
Config file:     /Users/rs/VirtualBox_VMs/Win10_Pro_x64/Win10_Pro_x64.vbox
Snapshot folder: /Users/rs/VirtualBox_VMs/Win10_Pro_x64/Snapshots
Log folder:      /Users/rs/VirtualBox_VMs/Win10_Pro_x64/Logs
Hardware UUID:   6c56ff23-1035-4956-911d-b6c2ac00e9fb
Memory size:     8192MB
Page Fusion:     off
VRAM size:       256MB
CPU exec cap:    100%
HPET:            off
Chipset:         ich9
Firmware:        BIOS
Number of CPUs:  2
PAE:             off
Long Mode:       on
Triple Fault Reset: off
APIC:            on
X2APIC:          off
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: HyperV
State:           powered off (since 2018-01-07T15:10:06.000000000)
Monitor count:   1
3D Acceleration: on
2D Video Acceleration: on
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):            SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      3
Storage Controller Bootable (0):        on
SATA (0, 0): /Users/rs/VirtualBox_VMs/Win10_Pro_x64/Win10_Pro_x64.vdi (UUID: 46501b56-190e-4ec1-bc88-538043925f68)
SATA (1, 0): Empty
NIC 1:           MAC: 08002796AF63, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: CoreAudio, Controller: HDA, Codec: STAC9221)
Audio playback:  enabled
Audio capture: enabled
Clipboard Mode:  Bidirectional
Drag and drop Mode: Bidirectional
VRDE:            disabled
USB:             disabled
EHCI:            disabled
XHCI:            enabled

Bandwidth groups:  <none>


Description:
Windows 10 Professional x64 deutsch
Guest:

Configured memory balloon size:      0 MB

I have configuered USB 2.0 (EHCI) for the XP Machine.
and USB 3.0 (xHCI) for the Win10 Machine.
If VB with XP is running i can plug in a USB 2.0 Stick or HDD and all is fine.But when i plug in (and hand over to the VB) i get the error message:

"Das USB-Gerät .... konnte nicht an die virtuelle Maschine XP Pro gebunden werden."

If i plugin a USB 2.0 HDD it takes a very long (approx. 2 minutes) to have access to the drive.
=======================================================
On the Win10 Machine I can plug in USB 2.0 Sticks and HDDs. They wrk fine.
I also can plug in USB 3.0 HDDs and sticks without error messages.
The HDD was NTFS Format. When i tried to transfer big file (for e.g. 2.6 GB) the transfer was interrupted by the USB 3.0 HDD with an error message.
the HDD was still visible in the VB but with no reaction.

If VB with XP is running i can plug in a USB 2.0 Stick or HDD and all is fine.But when i plug in (and hand over to the VB) i get the error message:

"Das USB-Gerät .... konnte nicht an die virtuelle Maschine XP Pro gebunden werden."

If i plugin a USB 2.0 HDD it takes a very long (approx. 2 minutes) to have access to the drive.

Can you please explain to me why you selected the (not recommended) ICH9 chipset? Do you know something more that made you change the template defaults?
You have not set up a USB filter. You might want to do that.
WinXP does not directly support USB3. Please read the following thread: USB basics and troubleshooting, all of the posts.
OSX does not have native support for NTFS. So, I assume that you use something like NTFS-3G on top of OSXFuse. This is an added layer of software, that can take some time to initialize. You might have better luck with exFAT HDDs.

Hello socratic,

1.) In deed, it is a good question why ICS9. I thought it was preselected when i created the VB. Now i tried to create a new VB but PIX3 was preselected.
may be i should chance to PIX3 and test again.
On my other PC with Win 7 x64 running both XP and Win 10 has PIX3. So i changed to ICH9 but this has a reason. I will check later.

2.) I tried with filter and without filter. the same result. to verify whats goin on i changed to my HP Laptop also installed VB 5.2 (same version same guest additions)
and same XP VB and same Win10 VB. Just so see if the problem is typical Mac Host.
But on the windows host i can see more in the Device Manager. Without filter as soon i plug in my USB 3.0 Stick (FAT32) in the USB 3.0 Port the Driver for the host will be installed. When i eject the USB stick from the Host to get it available for the guest, then i can see that the driver in the host ist not completely removed. I can see still the driver for the host with a yellow triangle. I also tried to install a filter for the Usb stick. but this failed also in 1 time of 5 trials. But i could see that the driver at the host was a VB-Driver. Yesterday day i had installed VB 5.1 on the Windows machine. Later i installed the newest VB (with guest additions)
I think with VB 5.1 the stick could be sometimes installed to the guest but mostly not. With VB 5.2 as i tried today, it was never possible to see the stick in XP guest.
Not with the filter and not without filter. the reason is that the host installs its driver before the filter can install its VB-Driver.

But i have a solution: I installed the Renesas-Driver for USB3.0 in XP Guest. Then i changed the VB-Intel USB emulation to the Renesas up720201 emulation and changed USB to xHCI. Now i have a USB 3.0 Renesas Chip in the Guest. All works fine.
I tried also a USB 2.0 extension cable, so the USB 3.0 Stick was connected as USB 2.0 Stick. this worked. (before i changed the USB emulation to uP720201)
but i am more happy with the first solution.

3. ) I know that XP does not support USB 3.0, and i all read the USB basics and troubleshooting. "all of the posts" i am not a newbee.

4.) OS X does support of NTFS! It can read NTFS but standard not write. But this is not a problem in a Windows guest. the file system is on an higher level of OS. so the file system is only relevant when the drive ist installed in guest. I don't use OSXFuse and i don't use NTFS-3G. I have the same problem with a USB3.0 Stick formatd as FAT32. I also use a partition formatted with exFat. so i can read/write with the Mac OS on host and read/write with Windows guest.
but this solves not my problem. My Problem with Win10 Guest ist, that i can not write to the NTFS Partition (and not to an other ext. HDD (USb3.0) with only NTFS) big files (e. g. 2.6 GB or 70GB) during writing i get an error message and then the drive is visible without any access.

but i hold do more tests. first to change the chipset to PIX3. and then to connect the ext. drive with a USB 2.0 cable.

thanks for your help.

virtualbox.org

Trouble with USB 2.0 / 3.0 on Mac OS

Trouble with USB 2.0 / 3.0 on Mac OS

Re: Trouble with USB 2.0 / 3.0 on Mac OS

Re: Trouble with USB 2.0 / 3.0 on Mac OS