Ubuntu installs failing. Suspect hybrid ssd/spindle drive

[cfichter]

Hi folks -
I've tried to install several versions of Ubuntu (most recent builds) both 32 and 64 bit and getting the same result.
After initial install and system wants to reboot (for first boot), Virtual box crashes and I get a debug dialogue (no error message).

The host is an HP Envy 4t-1000 Ultrabook with 16gb RAM and a 500gb hybrid hard drive -- that has a 32gb SSD also for the OS performance.
The chip is an AMD with an Intel 3000/AMD video card.

[mpack]

Please provide log files as zipped attachments, don't just spray text all over us. In any case what would be better is a VM log file - you can delete that host system info report. The VM log file is called "VBox.log" and can be found in the "Logs" subfolder of the VM folder.

[cfichter]

Log file attached. Thank you for taking a look.
I've used VirtualBox for a long time, but this is a new PC, never had a failure like this before. Much appreciated for the assist.

[mpack]

That log doesn't show a crash, and it also seems to be incomplete. You need to shut down (and not suspend) the VM before grabbing the log.

If you attached a PNG of the error dialog, empty or not, then it may also help.

[cfichter]

Hmmm. Screen shot doesn't seem to work for Vbox - using my normal shift+ctrl+fn+print screen button doesn't capture the window (tested on this pc, takes screen shots of everything else). I tried the VBox option from the Machine/Take Screenshot menu option, a dialogue box pops asking me to save the image, I hit OK but no file is created (tried several save locations and image formats).

I'll describe what happens. After install, I see a dialogue box that says "...Installation complete. You need to restart your computer in order to use the new installation."

There is a "Restart Now" button on that dialogue box.

When I hit the Restart Now, the VBox machine (not Vbox manager) crashes with a debug window (I have Visual Studio installed but don't have Vbox source).

Not sure where to go from here.

[cfichter]

I am thinking this is either a disk issue (I have explained it is the new hybrid drives, 512gb with 32gb ssd up front for OS performance), or possibly graphics (AMD proc with combined Intel 3000/Radeon HD 7670M.

Just to add, I did try the option/switch for SSD drive in the config in one of the efforts (thinking vbox might think the entire disk volume is ssd), same crash result.

[cfichter]

Worked first try just now on same machine with VMWare workstation v7 desktop - all default config, worked first install.

[mpack]

I am thinking this is either a disk issue.

VirtualBox normally doesn't care about what technology a host disk drive uses. That is a matter for the host OS and host drivers to worry about. VirtualBox files are opened and read/written using host OS file I/O APIs just like on any other drive.

If you are experiencing a problem with I/O to a drive then it wouldn't be a VirtualBox matter - it would be affecting all apps, plus the host OS filesystem itself.