On 7/20/24 21:46, Paul wrote:
On 7/20/2024 8:46 PM, philo wrote:
On 7/14/24 7:51 PM, philo wrote:
I've been using Vurtual Box for years and have never had a problem until >>> I upgraded Ubuntu from 22.04 to 24.04.
It was a simple fix, I just had to upgrade VB from version 6 to 7.
All fine until today
None of my machines work anymore and the error message is
No nested vtx present.
The option in settings is grayed out so I can't add it.
A Google search shows it must be enabled in the BIOS.
I just checked to make sure it is.
Don't know why it broke all of a sudden.
Not critical to me...just curious.
It was a BIOS setting for virtualization that I had to scroll down to find
So a battery change, and a setting that is not correct by default ?
Paul
I did not change the battery or any settings in the BIOS other than boot order.(That I'm aware of)
The VM error message was "no vt-x in BIOS"
I looked in the BIOS and "vt-x" was enabled but in Virtual Machine, the
option to enable it was grayed out.
Yesterday, I decided to see if there was anything I missed.
It turned out the option to enable virtualization was set to "disabled"
The reason I missed it was because that option did not show up on the
screen, I had to scroll down to get to it.
I forgot that sometimes BIOS settings are not obvious.
Funny thing though...VM is now working but I never did check off the no
longer grayed out "vt-x" option.
BTW: I occasionally correspond with an IT expert who told me he uses
Debian sid because he likes to analyze new code and offer fixes.
We'd probably make a great team. He could offer fixes and I could offer breakages !
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)