Guru meditation after Fedora 23 -> 24 upgrade
Guru meditation after Fedora 23 -> 24 upgrade
I have a Linux Fedora desktop that I just upgraded from version 23 to 24. After that I can no longer start my Windows 7 (32-bit) guest OS. It boots up fine and I get to the login page and then after perhaps one or two seconds I get a critical error / guru meditation. The logs talk about Guru Meditation -2301 (VERR_REM_VIRTUAL_CPU_ERROR). I've installed the latest version VirtualBox-5.1-5.1.10_112026_fedora24-1.x86_64 and the extension pack but that didn't make any difference.
What to do?
What to do?
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Guru meditation after Fedora 23 -> 24 upgrade
Really need to see the guests log file, but it may be that you upgraded while the guest was in a saved state and not properly shut down. If so then discard the saved state and see if it boots.
Re: Guru meditation after Fedora 23 -> 24 upgrade
I'm not quite sure what you mean with saved state. But presently the state of the guest OS is 'Aborted', as it crashes hard every time I try to start it.
One strange thing in the log was this line
00:00:00.551761 Guest OS type: 'Windows7'
00:00:00.556571 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.
But the guest OS I'm trying to start is 32bit! Double checked in Settings -> General -> Basic -> Version that says 'Windows 7 (32-bit)'
One strange thing in the log was this line
00:00:00.551761 Guest OS type: 'Windows7'
00:00:00.556571 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.
But the guest OS I'm trying to start is 32bit! Double checked in Settings -> General -> Basic -> Version that says 'Windows 7 (32-bit)'
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Guru meditation after Fedora 23 -> 24 upgrade
To provide VM log file: with the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.Perryg wrote:Really need to see the guests log file
While the VM is not running, right click VM name in the manager, then select "Discard saved state".user9001 wrote:I'm not quite sure what you mean with saved state.
Re: Guru meditation after Fedora 23 -> 24 upgrade
Ok, I've attached the log.
I found the 'Discard Saved State' option, but it's grayed out
I found the 'Discard Saved State' option, but it's grayed out
- Attachments
-
- Windows 7-2016-11-24-13-54-29.log.tar.gz
- (77.25 KiB) Downloaded 11 times
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Guru meditation after Fedora 23 -> 24 upgrade
Code: Select all
00:00:00.556571 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization.
Re: Guru meditation after Fedora 23 -> 24 upgrade
Ok, I tried to create a new guest OS. I opened the Create Virtual Machine dialog but there in the Version drop-down selection all the available choices were 32-bit. Didn't matter if Type was Linux or Windows there were no 64-bit version available.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Guru meditation after Fedora 23 -> 24 upgrade
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Guru meditation after Fedora 23 -> 24 upgrade
Thanks for the link.
I had a look in the BIOS and there was an option to support Intel Virtual Technology. It was disabled (and was been since always), I switched it to enabled, but that didn't make any difference for VirtualBox.
I can't think of anything else on my desktop that would grab the hardware virtualization. Any clues what to look for in the system logs?
I had a look in the BIOS and there was an option to support Intel Virtual Technology. It was disabled (and was been since always), I switched it to enabled, but that didn't make any difference for VirtualBox.
I can't think of anything else on my desktop that would grab the hardware virtualization. Any clues what to look for in the system logs?
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Guru meditation after Fedora 23 -> 24 upgrade
The exact wording of the BIOS option is important. Also you need to power off the PC after changing the CPU option, don't just do a warm restart.
There will be nothing in the system logs regarding hardware virtualization as the host OS doesn't know it from Adam. You will have to consider for yourself any optional VM, AV or system level debug tools you might have installed.
There will be nothing in the system logs regarding hardware virtualization as the host OS doesn't know it from Adam. You will have to consider for yourself any optional VM, AV or system level debug tools you might have installed.
Re: Guru meditation after Fedora 23 -> 24 upgrade
Still trying to get this image to work.
So I installed newest version 5.1.12 r112440 (Qt5.6.2) of VirtualBox and some things changed.
- I no longer get a "WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization" in the logs
- When I open up the Create Virtual Machine dialog I get in the Versions drop-down selection both 32-bit and 64-bit variants
- But the thing that hasn't changed is that when I start the guest OS it boots up fine, but when it gets to the login page it goes into guru meditation.
I've attached latest log file.
So I installed newest version 5.1.12 r112440 (Qt5.6.2) of VirtualBox and some things changed.
- I no longer get a "WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization" in the logs
- When I open up the Create Virtual Machine dialog I get in the Versions drop-down selection both 32-bit and 64-bit variants
- But the thing that hasn't changed is that when I start the guest OS it boots up fine, but when it gets to the login page it goes into guru meditation.
I've attached latest log file.
- Attachments
-
- VBox.log.tar.gz
- (75.22 KiB) Downloaded 9 times
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Guru meditation after Fedora 23 -> 24 upgrade
I don't understand. Is the guest 64bit or not? If it's a 64bit guest then you can't use a 32bit template. Please fix the underlying problem - enable VT-x in the host BIOS, then choose the 64bit template for the guest.
Re: Guru meditation after Fedora 23 -> 24 upgrade
I'm not trying to create a new guest OS. That's not the problem. I'm trying to start a guest OS that I've had for years and worked fine until I ungraded from Fedora 23 -> 24. The guest OS is 32bit
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Guru meditation after Fedora 23 -> 24 upgrade
It's not the first time I have seen an in place upgrade cause issues and why I decided a long time ago to just install new and forget the upgrade. Of course it make is a lot easier if you have your /home folder on a separate partition so you don't loose your settings or other data. Below is the reason for the problem:
You might be able to fix this by purging the current install, reboot, and install again so the kernel modules are rebuilt properly.
I would also look in the syslogs ( not sure fedora still uses these as I dropped fedora as a lost cause years ago as well. Too many problems ).
Code: Select all
00:01:00.019876 fatal error in recompiler cpu: Trying to execute code with memory type addr_code=0000000092d62020 addend=00007f85abcb2000 at 0000000092d6286c. (iHandlerMemType=0x38 iMMIOMemType=0x30)
00:01:00.019877
00:01:00.019905 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:01:00.019918 Console: Machine state changed to 'GuruMeditation'
00:01:00.020617 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:00.020618 !!
00:01:00.020619 !! VCPU0: Guru Meditation -2301 (VERR_REM_VIRTUAL_CPU_ERROR)
I would also look in the syslogs ( not sure fedora still uses these as I dropped fedora as a lost cause years ago as well. Too many problems ).
Re: Guru meditation after Fedora 23 -> 24 upgrade
I did a the following
rpm -e VirtualBox-5.1-5.1.12_112440_fedora24-1.x86_64
reboot
rpm -i VirtualBox-5.1-5.1.12_112440_fedora24-1.x86_64.rpm
Unfortunately that didn't change anything.
What I get with journalctl -fl from start of guest OS until guru meditation is just
Jan 02 08:47:06 host kernel: vboxdrv: ffffffffc0000020 VMMR0.r0
Jan 02 08:47:07 host kernel: vboxdrv: ffffffffc0102020 VBoxDDR0.r0
Jan 02 08:48:07 host tracker-extract.desktop[2162]: (tracker-extract:2162): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
rpm -e VirtualBox-5.1-5.1.12_112440_fedora24-1.x86_64
reboot
rpm -i VirtualBox-5.1-5.1.12_112440_fedora24-1.x86_64.rpm
Unfortunately that didn't change anything.
What I get with journalctl -fl from start of guest OS until guru meditation is just
Jan 02 08:47:06 host kernel: vboxdrv: ffffffffc0000020 VMMR0.r0
Jan 02 08:47:07 host kernel: vboxdrv: ffffffffc0102020 VBoxDDR0.r0
Jan 02 08:48:07 host tracker-extract.desktop[2162]: (tracker-extract:2162): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.