virtualbox.org

I was able to create a VB computer running Windows 10 on my MBP OS 10.12.6 which worked for a few months earlier this year, no problems. Then all of a sudden it stopped booting. I start the computer, it loads for a few seconds, and then goes black & white, pixilated and will not progress any further. I have included the log file and a screenshot of what the screen looks like when it reaches this point.

I am not very computer literate, and will appreciate any help and advice offered.

VBox.log wrote:

00:00:01.344835 Host RAM: 16384MB (16.0GB) total, 7405MB (7.2GB) available
00:00:01.533114   RamSize           <integer> = 0x00000002fc200000 (12 819 890 176, 12 226 MB, 11.9 GB)
00:00:01.533471   VRamSize         <integer> = 0x0000000008000000 (134 217 728, 128 MB)

You have allocated memory to the guest that you don't have available on the host. Your options are: a) allocate less memory to the guest, b) close some applications on the host, or c) buy some more memory for the host. Personally, I don't see what you can be doing in a Windows 10 guest that is going to need 11.9GB memory. You should reduce it down to 4.0GB or 6.0GB at most.

VBox.log wrote:

00:00:01.533111   NumCPUs           <integer> = 0x0000000000000002 (2)
00:00:01.806912 CPUM: Physical host cores: 2

You have allocated both of your hosts CPU cores (VirtualBox cares about cores not threads) to the guest which is going to lead to resource starvation on the host. You will have to reduce this to 1.

As it is a Windows 10 guest you may want to check that you have 2D and 3D graphics acceleration enabled and don't forget to eject the ISOs from the virtual optical drives when you are done with them.

-Andy.

Looks like 3D acceleration is already enabled, but the Guest Additions are out of date - worth fixing as there have been 3D acceleration fixes in the early 5.2.x branch.

Thanks andyp73 and mpack. I believe I have made those changes you suggested, but still no boot up. It no longer turns black and white, but it still hangs on startup. Also I don't think I can update guest additions until I can login, which the issue being I am unable to reach the login screen, unless there is another way around it I am unaware of...

I've attached the latest log.

00:00:01.431907   Serial0IoPortBase   <integer> = 0x00000000000003f8 (1 016)
00:00:01.431908   Serial0Irq          <integer> = 0x0000000000000004 (4)
00:00:01.431909   Serial1IoPortBase   <integer> = 0x00000000000002f8 (760)
00:00:01.431909   Serial1Irq          <integer> = 0x0000000000000003 (3)
00:00:01.431910   Serial2IoPortBase   <integer> = 0x00000000000003e8 (1 000)
00:00:01.431911   Serial2Irq          <integer> = 0x0000000000000004 (4)
00:00:01.431912   Serial3IoPortBase   <integer> = 0x00000000000002e8 (744)
00:00:01.431913   Serial3Irq          <integer> = 0x0000000000000003 (3)

Do you really need 4 serial ports for your guest? I'd really like to know what you're using this VM for...

00:00:01.432234 [/USB/Msd/0/LUN#0/] (level 4)
00:00:01.432235   Driver <string>  = "SCSI" (cb=5)

I have absolutely no clue what this "/USB/Msd" is. Looks like a hard drive interface of sorts, but I don't have any instance of it, in any of my VMs' logs. I'm going to go and search the source code and see what this is all about...

00:00:21.301047 VD#0: Read (0 bytes left) returned rc=VERR_DEV_IO_ERROR
00:00:21.301094 AHCI#0P0: Read at offset 3843293184 (131072 bytes left) returned rc=VERR_DEV_IO_ERROR
00:00:21.301682 AHCI#0: Port 0 reset
00:00:21.302761 VD#0: Cancelling all active requests
00:00:22.521474 AHCI#0: Port 0 reset
00:00:22.522562 VD#0: Cancelling all active requests
00:00:23.178578 AHCI#0: Port 0 reset
00:00:23.179666 VD#0: Cancelling all active requests

You get one of these blocks of errors every five seconds. I'm not sure about the condition of your hard drive, but I think it might be ready to leave this planet.

• Are you getting any other errors in the Console application of OSX (/Applications/Utilities/Console.app)?
• Is this the original hard drive from mid-2012?
• Do you have a backup?

I am not aiming in alarming you, maybe it's just the VDI that's corrupt. But something is not right when reading the VDI, that's why you get a "Device I/O error".

PS. For future reference, you should completely shut down the VM before grabbing the VBox.log. If you can't shut it down, close the VM window, force closing it.