VirtualBox takes hours to boot machine on Intel

[jared.harder]

Recently installed Solaris 11 11/11 and VirtualBox 4.1.16. First guest that I set up was going to be Win7 64-bit, but it took forever to even get to boot from the install media. It's been nearly 24 hours and it's still on the "Windows is loading files..." progress bar (100%, waiting to launch the installer). Below are my guest and host specs. I'm running VB as root right now, but it had the same functionality as a user, except it threw an exception when using passthrough mode on the BluRay drive (and wouldn't boot from the DVD with it disabled).

VirtualBox version: 4.1.16 r78094 Solaris version: Oracle Solaris 11 11/11

VirtualBox VM specs: OS: Win7 64-bit (ideally, if it installs) Memory: 11264MB CPU: 1, 100% execution cap CPU acceleration: VT-x/AMD-v, nested paging disabled Video: 24MB memory, 1 display, no 3D acceleration, no remote server Storage: 25GB dynamic VMDK stored on zpool, BD drive with passthrough Audio: disabled Network: 1 port enabled, NAT Serial, USB, Shared Folders all disabled/defaults

Host specs: Motherboard: Intel DX79SI CPU: Intel Core i7-3820 Memory: G.SKILL Ares Series 16GB Boot drive: OCZ Vertex 3 VTX3-25SAT3-60G Data drive: 5.54TB zpool with 6 hard drives using raidz2 (drives of various sizes including 1TB, 1.5TB, and 2TB) RAID card: SIL-3114 raid controller. I had to flash this card with an IDE-only firmware to get Solaris to pick up my drives, then in the format utility I had to specify the numbers so I could use the drive. There are 2 drives connected to this, the other 6 SATA devices (5 hard drives, optical drive) are connected directly to the motherboard) Optical drive: LG BluRay burner VT-x is enabled in the BIOS

Not sure what logs you'll need to help me troubleshoot this. Let me know and I'll provide them.

[Frank Mehnert]

Please attach a VBox.log file from a VM session for such a slow guest. You can find these logs in the main VM selector window, menu Machine / Show Log ...

[jared.harder]

Log file is over 6MB uncompressed, and tar just brings it to 1.5MB, still too big to attach. I've uploaded the logs: ​http://www.sendspace.com/file/jdkz2g (compressed) and ​http://www.sendspace.com/file/v9l0zj (uncompressed).

[Frank Mehnert]

Thanks for the logs. Investigating...

[jared.harder]

Replying to frank:

Thanks for the logs. Investigating...

Don't mean to be pushy, but is there any update on this issue?

[jared.harder]

I'd really love to use the Solaris solution, but I don't think I can wait much longer to find out if I can get a resolution. If there's absolutely anything I can do to help track down the root cause of this error, please let me know and I'll gladly help out.

[Ramshankar Venkataraman]

I tried downloading the files and I get: Sorry, the file you requested is not available.

I would recommend using something like DropBox (public folder) for uploading as it will retain the file as long as you wish than SendSpace.

[jared.harder]

Well I think I've already lost those log files as I uploaded them 6 weeks ago and have since formatted that box in an attempt to find a solution that does work (still haven't found a solution I like).

I'm willing to reinstall Solaris/VirtualBox if somebody can poke at my log files again. Might not be able to get around to testing it until this weekend.

In the meantime, are there any runtime parameters I can use with VB to enable additional logging so I can limit the number of times I need to repro this?

Thanks ramshankar!