virtualbox.org

I've been running a windows 7 guest VM on OSX Lion for months now, but yesterday it stopped booting. During bootup it goes to the Windows 7 loading screen with the animated logo and then just turns off. This is the end of the log file

00:00:10.334 Guest Additions information report: Version 4.1.2 r73507 '4.1.2'
00:00:10.334 Guest Additions information report: Interface = 0x00010004 osType = 0x00037100
00:00:10.335 Guest Additions capability report: (0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:10.335 Guest reported fixed hypervisor window at 0x0000000008000000 (size = 0x2400000, rc = VINF_SUCCESS)
00:00:11.514
00:00:11.514 !!Assertion Failed!!
00:00:11.514 Expression: pTask->enmTransferType == PDMACTASKFILETRANSFER_WRITE || (uint64_t)(offStart + cbToTransfer) <= pEndpoint->cbFile
00:00:11.514 Location : /Users/vbox/tinderbox/4.1-mac-rel/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp(842) int pdmacFileAioMgrNormalTaskPrepareNonBuffered(PDMACEPFILEMGR*, PDMASYNCCOMPLETIONENDPOINTFILE*, PDMACTASKFILE*, RTFILEAIOREQINTERNAL**)
00:00:11.514 Read exceeds file size offStart=59524825088 cbToTransfer=4096 cbFile=59521626112

Any ideas would be greatly appreciated?

I have the same problem with the same error in the logs. Last time I started VBox, a couple of weeks ago it started normally and shut down normally. Now it the vm quits just after the Windows startup animation finishes.

Anyone have any ideas?

wibald wrote:Anyone have any ideas?

Have you tried "repairing permissions" ?

However, It sounds more like a problem with the VM. What troubleshooting have you tried?

Thanks for the suggestion. Repairing permissions didn't change anything. I'm not sure what other troubleshooting to try. CH. 12 of the manual doesn't mention anything quite like what I'm seeing, there is no mention of Win7 guests or of troubleshooting Mac hosts. I've looked at the logs and see the same error as included above but don't know what to do about it. What else should I try?

This issue has become very annoying since I upgraded to VirtualBox 4.1.6 (or probably it has something to do with kernel 3.0.3->3.0.8 upgrade).

I haven't had this problem with VirtualBox 4.1.4.

I also tried removing and reinstalling Vbox. No go. Removed and tried newer 4.1.6 Vbox. No go. Same results, same error in logs. I wonder if it is a Mac OS 10.7.2 thing?

Same thing just happened to me. OSX 10.6.8

Ok, well I've looked at this for a while and it just doesn't look like there is anything else I can do. Too bad there isn't a vm repair tool out there that could tell me in plain language what to do to fix it. Are other vm apps more stable/easier to troubleshoot? I'd hate to start from scratch just to have this happen again.

I'm having the exact same problem. My host kernel paniced while I was using my VM and after I rebooted I tried to restart the VM which only gets about half way into the windows startup then aborts. Same error messages as above. Running vbox 4.1.6 on lion 10.7.2 with a win2008r2 vm.

My problem was a VDI corruption somewhere in the middle of the file (not the header). The file in OSX was actually corrupt. I had to boot into my recovery partition and repair my disk which was successful. This only partially fixed the problem, the VM would still not boot. I was trying random ways to clone and copy the disk to different formats which all failed when I stumbled across the VBoxManage modifyhd command. The command that worked for me was the compact command: At one point it stalled around the 40% mark where the copying failed and I thought for sure it was going to fail as well, but then suddenly it passed that point and was successful. I then booted my VM as normal and it finally worked!

I just upgraded my Host OS from OpenSUSE 11.4 to 12.1 - completely reformatting for the install. This also incremented my version of VirtualBox from 4.x to 4.1.4. I copied my Windows 7 Guest VM to the new instance, and started getting the same errors mentioned here. I fiddled with some settings on the VM and that changed the behavior from "VirtualBox aborted" to actually booting the VM and having it tell me "Disk read error. Press Ctrl-Alt-Del to reboot."

That's when I started searching for help and I landed here.

I tried using VBoxManage modifyhd "Windows 7.vdi" --compact and it ran successfully. However, I'm still not up and running with my guest. The "Disk Read Error" message has gone away since I ran this command. Now when it boots, I see the BIOS screen for a second or so, and then the guest hangs at a black screen with a solid ASCII cursor in the top-left corner.

So I guess my guest is hosed, which is kind of inconvenient but that's what I get for trying to upgrade my OS this weekend. (Off topic: I really miss SUSE 10.3, ever since I left there a couple years ago I've been fighting with regressions ever since.)

I just had this same problem. I upgraded from Ubuntu Maverick to Oneric and I got the same errors that amonteiro had above ("Read exceeds file size").

I tried the modifyhd thing and that didn't help (same thing happened as brandonkirsch - solid cursor in the top-left corner).

I was able to boot back into the old Ubuntu and export as an OVF and then imported it back into the current version. That worked okay for me. It would be nice to know what's going on, though...