Custom Query (16363 matches)
Results (1477 - 1479 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17438 | worksforme | Can't install Virtualbox 5.2.4 on OSX 10.13.2 | ||
| Description |
When I try to install Virtualbox on my Macbook pro, OSX 10.13.2 Installation fails with the message "The installation failed" "The installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance". |
|||
| #17437 | duplicate | Can't install Virtualbox 5.2.4 on OSX 10.13.2 | ||
| Description |
When I try to install Virtualbox on my Macbook pro, OSX 10.13.2 Installation fails with the message "The installation failed" "The installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance". |
|||
| #17435 | duplicate | VM 5.2.4 error message when starting Fedora 27 VM after kernel packages update Guru Meditation | ||
| Description |
I updated to 5.2.4. After updating all my linux VMs to the 5.2.4 Guest Additions they all did good restarts. I ran my Fedora 27 VM and did a regular update via DNF in a terminal. The only update was new kernel packages. Upon restart the VM generates a consistent error message and I do the recommended power off of the VM. It said to upload the log file and the .png file. The .png file is just a black rectangle. The error message is as follows: A critical error has occurred while running the virtual machine and the machine execution has been stopped. For help, please see the Community section on https://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the C:\Users\[username]\VirtualBox VMs\Fedora 27 x64\Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window. Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special (text recommending a power off follows) I have already posted to the forums, uploaded the VBox.log, and did a web search. In the forums the following was pointed out: 00:00:17.401353 !! VCPU0: Guru Meditation -1668 (VERR_PGM_INVALID_CR3_ADDR) I am attaching a .ZIP file of the VBox.log. |
|||

