Hi,
Every time I want to install Windows 11 on my Vbox 6.1.30 I get a gurumeditation.
What I'm I doing wrong.
Windows 11 Guru Meditation
-
- Posts: 55
- Joined: 26. Jun 2007, 09:24
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: XP, WIN 7, OpenSuse 11.1
Windows 11 Guru Meditation
- Attachments
-
- VBox.zip
- The log file of the vm.
- (71.15 KiB) Downloaded 17 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 11 Guru Meditation
I don't see anything obvious, except that you are getting a "triple fault" guru meditation while booting from an ISO, which I associate with a corrupted ISO.
Where did the ISO come from? It does not seemed to be named in a common Microsoft style.
Where did the ISO come from? It does not seemed to be named in a common Microsoft style.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Windows 11 Guru Meditation
FWIW, it probably is the official name: My own ISO file downloaded directly from Microsoft is named Win11_German_x86.iso, and Win10_21H1_German_x64.iso was the latest Windows 10 ISO at the time.mpack wrote:Where did the ISO come from? It does not seemed to be named in a common Microsoft style.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Windows 11 Guru Meditation
You're using an AMD CPU.jslegers wrote:What I'm I doing wrong.
Seriously, probably you're doing nothing wrong. You've encountered a known yet unsolved bug that only very few users reported so far. See 20468 for known technical details. AFAIK, the VirtualBox developers couldn't reproduce it so far.
After ~7 minutes, ~1 second before the Guru Meditation, the guest OS initiated a reboot. Was this reboot an expected event?
-
- Posts: 55
- Joined: 26. Jun 2007, 09:24
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: XP, WIN 7, OpenSuse 11.1
Re: Windows 11 Guru Meditation
Thanks for the info. Ah ok I hope they will fix it in the future this AMD bug.fth0 wrote:You're using an AMD CPU.jslegers wrote:What I'm I doing wrong.
Seriously, probably you're doing nothing wrong. You've encountered a known yet unsolved bug that only very few users reported so far. See 20468 for known technical details. AFAIK, the VirtualBox developers couldn't reproduce it so far.
After ~7 minutes, ~1 second before the Guru Meditation, the guest OS initiated a reboot. Was this reboot an expected event?
No I didn't initiate the reboot. This was during a install.
And if I use the iso on a real machine it works fine so it looks like de iso is ok.
Re: Windows 11 Guru Meditation
Hello i have a similar problem that when i power off one virtual machine, all other vm's will go in guru meditation and i have to start them up all over again.
i am on windows 11.
i'll attach a log of the event from both crashed vm's.
i'd be happy to know why and if it can be solved.
many thanks!
i am on windows 11.
i'll attach a log of the event from both crashed vm's.
i'd be happy to know why and if it can be solved.
many thanks!
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 11 Guru Meditation
@Soebren. It doesn't sound like the same problem, and in any case you didn't provide a log. Please start your own topic, describe the problem, and attach a zipped VM log.
Re: Windows 11 Guru Meditation
I got the same behavior described, repeated a couple times. Then I shut down my other running VMs so the Win11 install VM was the only running and retried and it worked without a problem. Running VB 6.1.30 also, on an AMD 4750G. hth
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 11 Guru Meditation
Interesting, timapi! Your situation could have been caused by all the running VMs using up the available host RAM, so the last VM didn't have enough RAM to work in.