Once again, VirtualBox could not start my new machine unless I checked the box in Storage, use Host I/O Cache.ģ) Everything went OK, except the Windows 7 guest failed to install an item called Base System Device. This time I had it reference both my Boot Camp and my EFI partition, whereas yesterday it had only referenced partition 4 (Boot Camp). vmdk file, following the instructions in the user manual precisely. And I set RAM for VirtualBox to about 1.2 GB. Unlike yesterday, I did not continue on and install the guest additions from the virtual CD-ROM. The other item I found in posts dealing with using VirtualBox to successfully run using a Boot Camp partition that has Windows 8 or 10 installed is to completely uninstall VirtualBox 5.0.X and to instead use 4.3.32.Īny comments on any of these more recent posts/tutorials?ġ) I used the VirtualBox uninstaller script to completely remove Virtual Box.Ģ) I reinstalled VirtualBox 5.0.12 and then the matching extension pack. In the same vein, it's highly recommended, once in VirtualBox to let VirtualBox know that the system is an EFI based system. Not just referencing the Boot Camp partition (4). In my case, that means having -partitions 1,4 at the end of the command that creates the. My system is EFI based, and according to the more recent posts (2014-2015) I have found, it is HIGHLY recommended, to put it mildly, to include both the EFI partition and the Boot Camp partition when creating the. Therefore I decided to search the Virtual Box forums for newer posts, including ones for running Windows 8 as a guest in my host OS (10.9 Mavericks). I have noticed that the tutorials I followed were written in 20. I was disappointed because I had very carefully followed a couple of tutorials to the letter, and Windows 7 ran fine under Virtual Box, but then Windows 7 booting properly from Boot Camp was problematic - all the BIOS errors under Windows 7. I agree with what you said saying VirtualBox "damaged the partition" was too strong. I can not attach my VirtualBox log - I tried, but it's 235 kb, and the limit is 128, and I don't know if any part of it is more important than another. I did install the Guest video driver to give me a full screen display in Virtual Box. And no ACPI error 13 messages.īut I am very hesitant to start the virtual machine again, in spite of it seeming to run well. I restored the image to the partition, and Bootcamp is again working very well - Starting Windows takes no more than 10-12 seconds. I tried running Chkdsk, I tried SFC /Scannow, and nothing improved the situation at all.īecause I had had some concerns about something like this happening, I had used Winclone to image my Boot Camp partition. In some situations, this error may cause the computer to function incorrectly. You should check with your computer manufacturer for an upgraded BIOS. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. : The embedded controller (EC) did not respond within the specified timeout period. I was able to finally log in, and decided to look at the System log in Event Viewer. It probably took 5-10 minutes to get past Starting Windows. Success!īut then I turned off my virtual machine, and later chose to boot the Mac using Boot Camp. My virtual machine launched OK, and everything seemed to be working great. I read the error messages, looked for potential fixes, and found that Settings, Storage, use Host I/O Cache did the trick. I used Terminal to set it all up, and at first I couldn't get the virtual machine to start. I thought it sounded like it might be handy if I needed to do something briefly in Windows. I read a number of online tutorials on how to use a Mac's Boot Camp Windows partition as a virtual disk with Virtual Box. 4 GB installed RAM, around 1.9 allocated to Virtual Machine, Windows 7 64-bit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |