Hello everyone
I am new to VirtualBox and appreciate any and all help.
I have VB 6.1.12
I am trying to create a VM of Windows Server 2019 and get a critical error before the install completes.
The logs are too big to attach to the post. What can I do?
Critical error on Windows 10 machine
Critical error on Windows 10 machine
- Attachments
-
- VBox.png (3.43 KiB) Viewed 886 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Critical error on Windows 10 machine
Zip 'em.MYF wrote:The logs are too big to attach to the post. What can I do?
Start the guest from full power off, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.
Please right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Re: Critical error on Windows 10 machine
Also, to get smaller logs, shut down Virtualbox, rename the current log, restart and create your error, then shut down again. That way, you only have that one session of info in the log. Then, zip the log file.
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Critical error on Windows 10 machine
Riolinda, the guest logs get automatically renamed every run of the guest (Vbox.log > Vbox.log.1 > Vbox.log.2 > Vbox.log.3) So Vbox.log will always be fresh, no manual renaming needed.
Re: Critical error on Windows 10 machine
Thanks! zipped logs attached.
- Attachments
-
- Logs.zip
- (84.47 KiB) Downloaded 5 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Critical error on Windows 10 machine
Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)