Windows VM keeps restarting on Mac

[LindseyV]

Code: Select all

I downloaded VirtualBox today and it only worked once. I deleted the vm that worked and now they keep restarting, over and over again. I have deleted VirtualBox and reinstalled as well as try different VMs but no luck.


00:02:12.299185 VMMDev: Guest Log: BIOS: int13_harddisk_ext: function 43, error 04 !
00:02:13.355134 GIM: HyperV: Guest OS reported ID 0x1040601011db1
00:02:13.355150 GIM: HyperV: Open-source=false Vendor=0x1 OS=0x4 (Windows NT or derivative) Major=6 Minor=1 ServicePack=1 Build=7601
00:02:13.355199 GIM: HyperV: Enabled TSC page at 0x000000001ffb2000 - u64TscScale=0xd3680d00000000 u64TscKHz=0x2f4d60 (3 100 000) Seq=1
00:02:13.355205 TM: Switching TSC mode from 'Dynamic' to 'RealTscOffset'
00:02:13.884193 AHCI#0: Reset the HBA
00:02:13.899805 VMMDev: Guest Additions information report: Version 4.3.12 r93733 '4.3.12'
00:02:13.899895 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x00037000 (Windows 7, 32-bit)
00:02:13.900155 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:02:13.900174 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:02:13.900289 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:02:13.900392 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:02:13.900403 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:02:13.910911 AHCI#0: Port 0 reset
00:02:13.918006 AHCI#0: Port 0 reset
00:02:13.969401 AHCI#0P0: Write at offset 3243261952 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:02:14.962403 AHCI#0P0: Write at offset 3243261952 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER

[0190]

Any luck solving this?
Having exactly the same problem here on virtualbox 5.0.22 and 5.1.0.

[socratis]

I don't know how I missed this one. First of all moving to "Windows guests", this is not an OSX guest problem.

@190
"Me too" doesn't help. You need to describe exactly the problem. You are sitting in front of your computer; I am not, I'm blind. Please read the following: Minimum information needed for assistance. The most important piece of information is the VBox.log, just like LindseyV did.

@LindseyV
I don't think I've taken a detailed look at your VBox.log. I will and let you know what I think. But from a quick look, I think that 512 MB of RAM for a Win7-x64 is way too low.

[mpack]

Note that the OPs post is from April. I also don't know why it was never answered: from my POV this was posted in the evening, just after I would normally knock off. So it may just have been bad timing. "New messages" doesn't cover more than a few hours.

I think that 512 MB of RAM for a Win7-x64 is way too low.

27MB of VRAM probably isn't ideal either.

However, I suspect the actual crash is related to this:

00:01:17.376856 AHCI#0P0: Write at offset 3188748288 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:18.375993 AHCI#0P0: Write at offset 3188748288 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:18.376439 AHCI#0P0: Write at offset 3188748288 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:19.376579 AHCI#0P0: Write at offset 3188748288 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:19.377269 AHCI#0P0: Write at offset 3188748288 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:20.377651 AHCI#0P0: Write at offset 3188748288 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:20.377940 AHCI#0P0: Write at offset 3188748288 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:21.376274 AHCI#0P0: Write at offset 3188748288 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:21.376932 AHCI#0P0: Write at offset 3188748288 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:21.377637 AHCI#0P0: Write at offset 3188744192 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:22.376809 AHCI#0P0: Write at offset 3188744192 (4096 bytes left) returned rc=VERR_INVALID_PARAMETER

There are many more in the log. This is telling me that a (virtual) AHCI (SATA) drive is having write problems. Either the host is out of space, has a failing disk, or there are permission problems.

[0190]

@190
"Me too" doesn't help. You need to describe exactly the problem. You are sitting in front of your computer; I am not, I'm blind. The most important piece of information is the VBox.log, just like LindseyV did.

Well, I was talking to OP, not to you.
If I was interest in getting support from someone else, I would've opened my own thread.
In case OP had a solution and it happened to help me, that would be enough. But in case there's no solution, and my issue is not connected to OP's at all, I'd like not to lead the thread away from the original issue.