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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 7/14/2024 8: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.

You can see here, it's a fun toy to play with.

I tried to get nesting to work here, and tested
it twice, and it didn't work. There was a claim at
the time that "it only needed the platform to write
three subroutines to make it work", yet an article
on the topic, said the three subroutines are very hard
to write and they cannot be dismissed with the wave of
a hand. They're hard work for someone.

But like the lottery, you have to play in order to win, so
it requires keeping at it.

https://stackoverflow.com/questions/54251855/virtualbox-enable-nested-vtx-amd-v-greyed-out

I think the odds are better of getting it to work on the Linux side,
because some of the suggestions for Windows just aren't practical.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 7/14/2024 10:07 PM, Paul wrote:

On 7/14/2024 8:51 PM, philo wrote:

I've been using Virtual 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.

You can see here, it's a fun toy to play with.

I tried to get nesting to work here, and tested
it twice, and it didn't work. There was a claim at
the time that "it only needed the platform to write
three subroutines to make it work", yet an article
on the topic, said the three subroutines are very hard
to write and they cannot be dismissed with the wave of
a hand. They're hard work for someone.

But like the lottery, you have to play in order to win, so
it requires keeping at it.

https://stackoverflow.com/questions/54251855/virtualbox-enable-nested-vtx-amd-v-greyed-out

I think the odds are better of getting it to work on the Linux side,
because some of the suggestions for Windows just aren't practical.

Paul

Decided to look further into this and install Virtual Box 7 on my
Windows machine. Nested vtx is not present either but all the virtual
machines I've installed are working fine, to I guess that's not the
issue that broke VB

As long as I do have it working on at least one machine, that's good
enough for me. I prefer operating systems on real hardware anyway and
must have 30 different operating systems at my disposal...that's
probably enough.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 7/15/2024 6:24 AM, philo wrote:

On 7/14/2024 10:07 PM, Paul wrote:

On 7/14/2024 8:51 PM, philo wrote:

I've been using Virtual 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.

You can see here, it's a fun toy to play with.

I tried to get nesting to work here, and tested
it twice, and it didn't work. There was a claim at
the time that "it only needed the platform to write
three subroutines to make it work", yet an article
on the topic, said the three subroutines are very hard
to write and they cannot be dismissed with the wave of
a hand. They're hard work for someone.

But like the lottery, you have to play in order to win, so
it requires keeping at it.

https://stackoverflow.com/questions/54251855/virtualbox-enable-nested-vtx-amd-v-greyed-out

I think the odds are better of getting it to work on the Linux side,
because some of the suggestions for Windows just aren't practical.

    Paul

Decided to look further into this and install Virtual Box 7 on my Windows machine. Nested vtx is not present either but all the virtual machines I've installed are working fine, to I guess that's not the issue that broke VB

As long as I do have it working on at least one machine, that's good enough for me. I prefer operating systems on real hardware anyway and must have 30 different operating systems at my disposal...that's probably enough.

Start : Run : control.exe
Programs and Features
Windows Features

Turn off Hyper-V or use the BCDEdit control to stop
the launch of Hyper-V.

Then go back and check the status of your VBox7 on Windows, after your Windows reboots.

bcdedit ; Check and record the current details. Wipe and right-click once to copy.

bcdedit /set hypervisorlaunchtype off ; See if this improves your next VBox session (after a reboot)

bcdedit /set hypervisorlaunchtype auto ; It's possible this will match what the first "bcdedit" shows (Auto).

For example, unmodified, I see this. Auto is likely the "as installed" option. Or, I might have switched that on in Windows Features. I doubt it will fix
the bcdedit but you never know whether the automation is there for that.

Windows Boot Loader
-------------------
...

hypervisorlaunchtype Auto

Windows is normally virtualized. Hyper-V is an inverted hypervisor,
and it is the boss. Windows runs as a Guest. VirtualBox runs as a Guest
in a sense, too. But we don't know what ring numbers are assigned.
There is no block diagram (or for that matter, tools) to tell
you how any of it works. When Hyper-V is turned off as a platform,
it could be that Hyper-V is still being used to make Windows run as a Guest.

Ubuntu should be simpler. Ubuntu would be loaded as Host. Ubuntu does not
use an inverted Hypervisor. It would be the "other kind" of hypervisor, the legacy flavor, and "Nesting" should work if someone writes "the three subroutines".
Then, in the Guest, you'd need some sort of readout of virtualization
features (the area that Windows punts on, and refuses to comment). The
work done to make VirtualBox run in Windows (as a "Guest"), would be unused in the
Ubuntu case (an older VirtualBox had already figured out how to do that).

In Windows, after you do the bcdedit

bcdedit /set hypervisorlaunchtype off

then reboot, check

Start : run : msinfo32

There are slight differences between OSes, and here is a picture of them.
But without a block diagram, it's hard to judge which are significant contributors.

[Picture]

https://i.postimg.cc/NjH9Rzjx/W10-W11-Programs-Features-Virtualization.gif

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 7/15/2024 6:24 AM, philo wrote:

On 7/14/2024 10:07 PM, Paul wrote:

On 7/14/2024 8:51 PM, philo wrote:

I've been using Virtual 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.

You can see here, it's a fun toy to play with.

I tried to get nesting to work here, and tested
it twice, and it didn't work. There was a claim at
the time that "it only needed the platform to write
three subroutines to make it work", yet an article
on the topic, said the three subroutines are very hard
to write and they cannot be dismissed with the wave of
a hand. They're hard work for someone.

But like the lottery, you have to play in order to win, so
it requires keeping at it.

https://stackoverflow.com/questions/54251855/virtualbox-enable-nested-vtx-amd-v-greyed-out

I think the odds are better of getting it to work on the Linux side,
because some of the suggestions for Windows just aren't practical.

    Paul

Decided to look further into this and install Virtual Box 7 on my Windows machine. Nested vtx is not present either but all the virtual machines I've installed are working fine, to I guess that's not the issue that broke VB

As long as I do have it working on at least one machine, that's good enough for me. I prefer operating systems on real hardware anyway and must have 30 different operating systems at my disposal...that's probably enough.

I tried Nesting on Ubuntu.

Ubuntu2404
Lubuntu2404 (installed)
Lubuntu2404 (just the DVD, live session)

and it worked. Nesting tick boxes on both copies of Virtualbox 7.0.16 .

[Picture]

https://i.postimg.cc/1t6VWkJB/ubuntu-vbox7016-nested-tick-box.gif

I put the Guest Additions in the top Virtual Machine, but not
needed just for a quick demo of the bottom Virtual Machine running.

The automation does not add you to the Vboxusers group. You have
to do that as a step from Terminal. Bullwinkle is the account running
the host and guest.

sudo usermod -a -G vboxusers bullwinkle

Note that, the second guest down was not completely happy. There was
something wrong with the graphics standard offered down there, but it
continued on, anyway. Lubuntu takes forever to install, and I
wasn't waiting for that to complete a second time. That's why
the second Guest received a minimal test. Too much time consumed
to do otherwise.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 7/16/2024 2:10 PM, Paul wrote:

On 7/15/2024 6:24 AM, philo wrote:

On 7/14/2024 10:07 PM, Paul wrote:

On 7/14/2024 8:51 PM, philo wrote:

I've been using Virtual 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.

You can see here, it's a fun toy to play with.

I tried to get nesting to work here, and tested
it twice, and it didn't work. There was a claim at
the time that "it only needed the platform to write
three subroutines to make it work", yet an article
on the topic, said the three subroutines are very hard
to write and they cannot be dismissed with the wave of
a hand. They're hard work for someone.

But like the lottery, you have to play in order to win, so
it requires keeping at it.

https://stackoverflow.com/questions/54251855/virtualbox-enable-nested-vtx-amd-v-greyed-out

I think the odds are better of getting it to work on the Linux side,
because some of the suggestions for Windows just aren't practical.

    Paul

Decided to look further into this and install Virtual Box 7 on my Windows machine. Nested vtx is not present either but all the virtual machines I've installed are working fine, to I guess that's not the issue that broke VB

As long as I do have it working on at least one machine, that's good enough for me. I prefer operating systems on real hardware anyway and must have 30 different operating systems at my disposal...that's probably enough.

I tried Nesting on Ubuntu.

Ubuntu2404
Lubuntu2404 (installed)
Lubuntu2404 (just the DVD, live session)

and it worked. Nesting tick boxes on both copies of Virtualbox 7.0.16 .

[Picture]

https://i.postimg.cc/1t6VWkJB/ubuntu-vbox7016-nested-tick-box.gif

I put the Guest Additions in the top Virtual Machine, but not
needed just for a quick demo of the bottom Virtual Machine running.

The automation does not add you to the Vboxusers group. You have
to do that as a step from Terminal. Bullwinkle is the account running
the host and guest.

sudo usermod -a -G vboxusers bullwinkle

Note that, the second guest down was not completely happy. There was something wrong with the graphics standard offered down there, but it continued on, anyway. Lubuntu takes forever to install, and I
wasn't waiting for that to complete a second time. That's why
the second Guest received a minimal test. Too much time consumed
to do otherwise.

Paul

I'm going to fool around with this on Linux some other day, I'm now
looking into various Windows configurations.

Just installed an old version of Virtual Box on my Win7 machine

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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)

On 21/07/2024 12:38, philo wrote:

We'd probably make a great team. He could offer fixes and I could offer breakages !

There are QA teams out there who would love to have you on board.

One of the most valuable people to have in QA are people who don't just
know it broke, they know what they did and can make it happen again.

I once spent 18 months off and on looking for a bug. We knew it was
happening, but we had no idea what triggered it. One of our field
engineers got promoted by working out how to trigger it. (it was a race condition)

Andy

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

I always told me crew:
If the customer has a problem...solve it.

If they don't have a problem...create one.

Anyway...I solved a lot mote problems than I created and that gave me
something quite valuable: job security .

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)