VT-x is enabled, but ubuntu 18.04 doesn't show it
up vote
0
down vote
favorite
I was running VMWare Workstation 14 on Ubuntu 16.04 for months with no problems. After upgrading to Ubuntu 18.04 I started getting a VT-x not enabled error message. VT-x is enabled in the BIOS. I contacted VMWare and they tested the hardware and confirmed VT-x support is enabled.
They state there must be an issue in Ubuntu 18.04... I agree.
Has anyone found a solution for this problem?
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 158
Model name: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
Stepping: 9
CPU MHz: 800.016
CPU max MHz: 3800.0000
CPU min MHz: 800.0000
BogoMIPS: 6816.00
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
NUMA node0 CPU(s): 0-3
virtualization vmware cpu
edited Oct 19 at 0:30
muru
134k19282483
asked Oct 19 at 0:14
Tommy Vinson
12
add a comment |
up vote
0
down vote
favorite
I was running VMWare Workstation 14 on Ubuntu 16.04 for months with no problems. After upgrading to Ubuntu 18.04 I started getting a VT-x not enabled error message. VT-x is enabled in the BIOS. I contacted VMWare and they tested the hardware and confirmed VT-x support is enabled.
They state there must be an issue in Ubuntu 18.04... I agree.
Has anyone found a solution for this problem?
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 158
Model name: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
Stepping: 9
CPU MHz: 800.016
CPU max MHz: 3800.0000
CPU min MHz: 800.0000
BogoMIPS: 6816.00
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
NUMA node0 CPU(s): 0-3
virtualization vmware cpu
edited Oct 19 at 0:30
muru
134k19282483
asked Oct 19 at 0:14
Tommy Vinson
12
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I was running VMWare Workstation 14 on Ubuntu 16.04 for months with no problems. After upgrading to Ubuntu 18.04 I started getting a VT-x not enabled error message. VT-x is enabled in the BIOS. I contacted VMWare and they tested the hardware and confirmed VT-x support is enabled.
They state there must be an issue in Ubuntu 18.04... I agree.
Has anyone found a solution for this problem?
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 158
Model name: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
Stepping: 9
CPU MHz: 800.016
CPU max MHz: 3800.0000
CPU min MHz: 800.0000
BogoMIPS: 6816.00
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
NUMA node0 CPU(s): 0-3
virtualization vmware cpu
edited Oct 19 at 0:30
muru
134k19282483
asked Oct 19 at 0:14
Tommy Vinson
12
I was running VMWare Workstation 14 on Ubuntu 16.04 for months with no problems. After upgrading to Ubuntu 18.04 I started getting a VT-x not enabled error message. VT-x is enabled in the BIOS. I contacted VMWare and they tested the hardware and confirmed VT-x support is enabled.
They state there must be an issue in Ubuntu 18.04... I agree.
Has anyone found a solution for this problem?
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 158
Model name: Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
Stepping: 9
CPU MHz: 800.016
CPU max MHz: 3800.0000
CPU min MHz: 800.0000
BogoMIPS: 6816.00
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 6144K
NUMA node0 CPU(s): 0-3
virtualization vmware cpu
virtualization vmware cpu
edited Oct 19 at 0:30
muru
134k19282483
asked Oct 19 at 0:14
Tommy Vinson
12
edited Oct 19 at 0:30
muru
134k19282483
asked Oct 19 at 0:14
Tommy Vinson
12
edited Oct 19 at 0:30
muru
134k19282483
edited Oct 19 at 0:30
muru
134k19282483
edited Oct 19 at 0:30
muru
134k19282483
134k19282483
asked Oct 19 at 0:14
Tommy Vinson
12
asked Oct 19 at 0:14
Tommy Vinson
12
asked Oct 19 at 0:14
Tommy Vinson
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I had this same exact problem. It happened after upgrading from ubuntu 16.06 to 18.04. Both virtualbox and vmware 15 started having issues where virtualization was not detected. I didn't change the BIOS and virtualization was enabled (I double checked). cpuinfo also showed that virtualization was enabled.
Here is how I fixed it. The idea was to force the bios to wipe its settings and then re-enable virtualization... maybe something got corrupted when ubuntu tried to install its key in the EFI partition.
Open the BIOS and restore to defaults. In my case, I had a choice
between two different defaults one for XP and Win 7 and one for new
OSes (aka Secure boot settings). I restored to the Win8 and above
settingsReboot
Enter the BIOS again and enable Virtualization and Disable Secure
boot (vmware modules wont load with it on unless you sign them your
self).Now vmware worked.
Good luck!
answered Nov 22 at 17:50
rbhkamal
1
New contributor
rbhkamal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I had this same exact problem. It happened after upgrading from ubuntu 16.06 to 18.04. Both virtualbox and vmware 15 started having issues where virtualization was not detected. I didn't change the BIOS and virtualization was enabled (I double checked). cpuinfo also showed that virtualization was enabled.
Here is how I fixed it. The idea was to force the bios to wipe its settings and then re-enable virtualization... maybe something got corrupted when ubuntu tried to install its key in the EFI partition.
Open the BIOS and restore to defaults. In my case, I had a choice
between two different defaults one for XP and Win 7 and one for new
OSes (aka Secure boot settings). I restored to the Win8 and above
settingsReboot
Enter the BIOS again and enable Virtualization and Disable Secure
boot (vmware modules wont load with it on unless you sign them your
self).Now vmware worked.
Good luck!
answered Nov 22 at 17:50
rbhkamal
1
New contributor
rbhkamal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
I had this same exact problem. It happened after upgrading from ubuntu 16.06 to 18.04. Both virtualbox and vmware 15 started having issues where virtualization was not detected. I didn't change the BIOS and virtualization was enabled (I double checked). cpuinfo also showed that virtualization was enabled.
Here is how I fixed it. The idea was to force the bios to wipe its settings and then re-enable virtualization... maybe something got corrupted when ubuntu tried to install its key in the EFI partition.
Open the BIOS and restore to defaults. In my case, I had a choice
between two different defaults one for XP and Win 7 and one for new
OSes (aka Secure boot settings). I restored to the Win8 and above
settingsReboot
Enter the BIOS again and enable Virtualization and Disable Secure
boot (vmware modules wont load with it on unless you sign them your
self).Now vmware worked.
Good luck!
answered Nov 22 at 17:50
rbhkamal
1
New contributor
rbhkamal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
I had this same exact problem. It happened after upgrading from ubuntu 16.06 to 18.04. Both virtualbox and vmware 15 started having issues where virtualization was not detected. I didn't change the BIOS and virtualization was enabled (I double checked). cpuinfo also showed that virtualization was enabled.
Here is how I fixed it. The idea was to force the bios to wipe its settings and then re-enable virtualization... maybe something got corrupted when ubuntu tried to install its key in the EFI partition.
Open the BIOS and restore to defaults. In my case, I had a choice
between two different defaults one for XP and Win 7 and one for new
OSes (aka Secure boot settings). I restored to the Win8 and above
settingsReboot
Enter the BIOS again and enable Virtualization and Disable Secure
boot (vmware modules wont load with it on unless you sign them your
self).Now vmware worked.
Good luck!
answered Nov 22 at 17:50
rbhkamal
1
New contributor
rbhkamal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I had this same exact problem. It happened after upgrading from ubuntu 16.06 to 18.04. Both virtualbox and vmware 15 started having issues where virtualization was not detected. I didn't change the BIOS and virtualization was enabled (I double checked). cpuinfo also showed that virtualization was enabled.
Here is how I fixed it. The idea was to force the bios to wipe its settings and then re-enable virtualization... maybe something got corrupted when ubuntu tried to install its key in the EFI partition.
Open the BIOS and restore to defaults. In my case, I had a choice
between two different defaults one for XP and Win 7 and one for new
OSes (aka Secure boot settings). I restored to the Win8 and above
settingsReboot
Enter the BIOS again and enable Virtualization and Disable Secure
boot (vmware modules wont load with it on unless you sign them your
self).Now vmware worked.
Good luck!
answered Nov 22 at 17:50
rbhkamal
1
New contributor
rbhkamal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 22 at 17:50
rbhkamal
1
New contributor
rbhkamal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 22 at 17:50
rbhkamal
1
answered Nov 22 at 17:50
rbhkamal
1
1
New contributor
rbhkamal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
rbhkamal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
rbhkamal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1085051%2fvt-x-is-enabled-but-ubuntu-18-04-doesnt-show-it%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
