VirtualBox

Ticket #7108 (closed defect: obsolete)

Opened 4 years ago

Last modified 4 months ago

Linux kernel >= 2.6.32 and VirtualBox >= 3.1.6 causes "Delayed Write Failed" for iPod on WinXP guest

Reported by: stharward Owned by:
Priority: major Component: USB
Version: VirtualBox 3.2.6 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description

If I run VirtualBox (any version since 3.1.6) on a Linux host using kernel 2.6.32 or higher, I cannot use iTunes -- which is running on a Windows XP SP3 32-bit guest -- to sync my iPod through the USB interface. After about 30 minutes of sitting around trying to write to the iPod, Windows throws up a "Delayed write failed" error, as seen in the attached screenshot (E:\ is the drive letter of the iPod). I have tried enabling/disabling write caching on the drive through the Windows Control Panel (which was suggested by several online sources), but changing this setting has no effect.

Attachments

Win XP running on 2.6.31.log Download (128.6 KB) - added by stharward 4 years ago.
Machine log running on linux kernel 2.6.31 (no delayed write errors)
Win XP running on 2.6.34.log Download (118.0 KB) - added by stharward 4 years ago.
Machine log running on linux kernel 2.6.34 (causes delayed write error; log file is marked at point where error occurred)
Win XP running on 2.6.34-delayed write error screenshot.png Download (199.8 KB) - added by stharward 4 years ago.
Screenshot of "Delayed write error" when running guest under kernel 2.6.34

Change History

Changed 4 years ago by stharward

Machine log running on linux kernel 2.6.31 (no delayed write errors)

Changed 4 years ago by stharward

Machine log running on linux kernel 2.6.34 (causes delayed write error; log file is marked at point where error occurred)

Changed 4 years ago by stharward

Screenshot of "Delayed write error" when running guest under kernel 2.6.34

comment:1 Changed 4 years ago by stharward

I guess I should clarify that I have not tried running any version of VirtualBox before 3.1.6. In other words, I'm not implying that the problem appeared in 3.1.6. It could have existed in previous versions, but I don't know if it did because I never tested them.

comment:2 Changed 4 months ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use