| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 43 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 95:34:57 |
| Calls: | 290 |
| Files: | 904 |
| Messages: | 76,423 |
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.
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
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.
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.
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
