Hi All,
When attempting to capture my VirtualBox machine, I have the Virtual Box Guru Meditation Critical Error stop me in my tracks once the machine is attempting to reboot during the capture process.
I have already reduced the amount of RAM allocated to the VM. Disabled audio devices. Lowered the amount of graphics memory. Issues persist.
I am unable to make sense of the logs. Could I please have some assistance from someone with more knowledge?
I have attached these.
Thank you.
Virtual Box Guru Meditation Critical Error - Windows 10 MDT
Virtual Box Guru Meditation Critical Error - Windows 10 MDT
- Attachments
-
- Logs.zip
- (235.95 KiB) Downloaded 11 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtual Box Guru Meditation Critical Error - Windows 10 MDT
You seem to be running a nested VM, with VMWare as the host. This is not a supported configuration.
The actual error is VERR_EM_TRIPLE_FAULT, which usually indicates a corrupted drive, as evidenced by the fact that the crash happens immediately the VM begins to boot from the drive, and is fine before that. The extension pack has not been installed.
p.s. In future, please provide one relevant log only.
The actual error is VERR_EM_TRIPLE_FAULT, which usually indicates a corrupted drive, as evidenced by the fact that the crash happens immediately the VM begins to boot from the drive, and is fine before that. The extension pack has not been installed.
p.s. In future, please provide one relevant log only.
Re: Virtual Box Guru Meditation Critical Error - Windows 10 MDT
Thank you for the fast reply mpack.
I have since imported an export of my VM onto a physical machine running VirtualBox, and run into the same issue. I imagine this is due corruption as you had mentioned.
I have attached logs of this issue occurring again for reference.
Is there any guides or something that I can follow in order to repair the corruption? This is an image that I have unfortunately spent a considerable amount of time developing and would like to explore repair options prior to restarting from scratch - if this is possible.
I greatly appreciate your time and dedication. Thank you.
I have since imported an export of my VM onto a physical machine running VirtualBox, and run into the same issue. I imagine this is due corruption as you had mentioned.
I have attached logs of this issue occurring again for reference.
Is there any guides or something that I can follow in order to repair the corruption? This is an image that I have unfortunately spent a considerable amount of time developing and would like to explore repair options prior to restarting from scratch - if this is possible.
I greatly appreciate your time and dedication. Thank you.
- Attachments
-
- VBox.zip
- (66.18 KiB) Downloaded 6 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtual Box Guru Meditation Critical Error - Windows 10 MDT
I don't know enough about the nature of the corruption, and where and when it occurred, to offer any useful advice for fixing it. I can tell you that the corruption is of the disk content, not the VDI, so no VDI repair tool will help. I suspect that this VDI is copied from something else, and it was corrupted at source (first copy). But, that is just a guess based on very little information.
-
- Posts: 2
- Joined: 29. Oct 2020, 03:25
Re: Virtual Box Guru Meditation Critical Error - Windows 10 MDT
After a lot of mucking around with time zones and network cards and still getting nowhere I eventually got it to work.
Administrator account is disabled by default, so when the virtual machine reboots after being sysprepped its unable to run the connection correctly.
Sysprep in H2 seems to run WinPE initially, then reboot, then logs in as administrator, runs sysprep, reboots and wim creation proceeds.
If the Administrator account is disabled it can't do its thing.
For what its worth, I also made sure my MDT server had the fix for MDT8546 installed and made sure my server was fully updated.
Administrator account is disabled by default, so when the virtual machine reboots after being sysprepped its unable to run the connection correctly.
Sysprep in H2 seems to run WinPE initially, then reboot, then logs in as administrator, runs sysprep, reboots and wim creation proceeds.
If the Administrator account is disabled it can't do its thing.
For what its worth, I also made sure my MDT server had the fix for MDT8546 installed and made sure my server was fully updated.