VirtualBox

Opened 13 years ago

Closed 8 years ago

#9904 closed defect (obsolete)

Panic on FreeBSD (initiate_write_inodeblock_ufs2)

Reported by: Max Savenkov Owned by:
Component: other Version: VirtualBox 4.1.6
Keywords: Cc:
Guest type: BSD Host type: Windows

Description (last modified by aeichner)

I'm using VirtualBox to run FreeBSD 7.2-RELEASE. From time to time, I get panic with the following message:

"panic initiate_write_inodeblock_ufs2 already started"

I gather that it is related to problems with disk access. This VM use a single VDI virtual drive and nothing else. The same host machine is also running 3 other VirtualBox machines, one FreeBSD and two WinXP, all using different vdi drives, located on the same physical drive. May this be a problem? I also sometimes see one of my WinXP VMs BSOD, but not the other.

This problem persisted through all releases of Virtual Box I tried, from 3.x to 4.1.6.

Configuration: Hardware: CPU: Intel Core i5 760 RAM: 8Gb

Software: Host OS: Windows 7 64-Bit Professional, VirtualBox 4.1.16 Bridged LAN Guests: 2xFreeBSD 7.2-RELEASE (32bit), 2xWindows XP SP2 (32bit)

Detailed VM config and VBox.log are attached.

Attachments (2)

VBox.log (53.5 KB ) - added by Max Savenkov 13 years ago.
VBox.log with crash
VM config.txt (2.6 KB ) - added by Max Savenkov 13 years ago.
VM configuration

Download all attachments as: .zip

Change History (3)

by Max Savenkov, 13 years ago

Attachment: VBox.log added

VBox.log with crash

by Max Savenkov, 13 years ago

Attachment: VM config.txt added

VM configuration

comment:1 by aeichner, 8 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

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