How do I enable hardware virtualization technology (VT-x) for use in Virtualbox?
So I am trying to run Ubuntu in a virtualbox but on installing 12.10 from the .iso I was greeted by a warning telling me that audio wouldn't work then I pressed next and this popped up:
Failed to open a session for the virtual machine Tux 3
VT-x features locked or unavailable in MSR
(VERR_VMX_MSR_LOCKED_OR_DISABLED)
Details
Result Code:
E_FAIL (0x80004005)
Component:
Console
Interface:
IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
And then it doesn't work.
I assigned 4GB of my 8GB to Ubuntu, 100 dynamically allocated GB of space, and 12MB of graphics memory. I'm running an Asus p8z77 V LX mobo with an Intel i5 3550 processor.
Downloaded 12.04.2 on my PC and tried again. Still getting the same message.
system-installation virtualbox virtualization
edited Jan 19 '15 at 20:00
Takkat
108k37252379
asked Feb 16 '13 at 8:44
user132520user132520
391245
add a comment |
So I am trying to run Ubuntu in a virtualbox but on installing 12.10 from the .iso I was greeted by a warning telling me that audio wouldn't work then I pressed next and this popped up:
Failed to open a session for the virtual machine Tux 3
VT-x features locked or unavailable in MSR
(VERR_VMX_MSR_LOCKED_OR_DISABLED)
Details
Result Code:
E_FAIL (0x80004005)
Component:
Console
Interface:
IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
And then it doesn't work.
I assigned 4GB of my 8GB to Ubuntu, 100 dynamically allocated GB of space, and 12MB of graphics memory. I'm running an Asus p8z77 V LX mobo with an Intel i5 3550 processor.
Downloaded 12.04.2 on my PC and tried again. Still getting the same message.
system-installation virtualbox virtualization
edited Jan 19 '15 at 20:00
Takkat
108k37252379
asked Feb 16 '13 at 8:44
user132520user132520
391245
Related: Cannot install Ubuntu in VirtualBox due to " this kernel requires an x86-64 CPU, but only detects an i686 CPU, unable to boot" error
– kiri
Jan 3 '14 at 21:05
add a comment |
So I am trying to run Ubuntu in a virtualbox but on installing 12.10 from the .iso I was greeted by a warning telling me that audio wouldn't work then I pressed next and this popped up:
Failed to open a session for the virtual machine Tux 3
VT-x features locked or unavailable in MSR
(VERR_VMX_MSR_LOCKED_OR_DISABLED)
Details
Result Code:
E_FAIL (0x80004005)
Component:
Console
Interface:
IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
And then it doesn't work.
I assigned 4GB of my 8GB to Ubuntu, 100 dynamically allocated GB of space, and 12MB of graphics memory. I'm running an Asus p8z77 V LX mobo with an Intel i5 3550 processor.
Downloaded 12.04.2 on my PC and tried again. Still getting the same message.
system-installation virtualbox virtualization
edited Jan 19 '15 at 20:00
Takkat
108k37252379
asked Feb 16 '13 at 8:44
user132520user132520
391245
So I am trying to run Ubuntu in a virtualbox but on installing 12.10 from the .iso I was greeted by a warning telling me that audio wouldn't work then I pressed next and this popped up:
Failed to open a session for the virtual machine Tux 3
VT-x features locked or unavailable in MSR
(VERR_VMX_MSR_LOCKED_OR_DISABLED)
Details
Result Code:
E_FAIL (0x80004005)
Component:
Console
Interface:
IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
And then it doesn't work.
I assigned 4GB of my 8GB to Ubuntu, 100 dynamically allocated GB of space, and 12MB of graphics memory. I'm running an Asus p8z77 V LX mobo with an Intel i5 3550 processor.
Downloaded 12.04.2 on my PC and tried again. Still getting the same message.
system-installation virtualbox virtualization
system-installation virtualbox virtualization
edited Jan 19 '15 at 20:00
Takkat
108k37252379
asked Feb 16 '13 at 8:44
user132520user132520
391245
edited Jan 19 '15 at 20:00
Takkat
108k37252379
asked Feb 16 '13 at 8:44
user132520user132520
391245
edited Jan 19 '15 at 20:00
Takkat
108k37252379
edited Jan 19 '15 at 20:00
Takkat
108k37252379
edited Jan 19 '15 at 20:00
Takkat
108k37252379
108k37252379
asked Feb 16 '13 at 8:44
user132520user132520
391245
asked Feb 16 '13 at 8:44
user132520user132520
391245
asked Feb 16 '13 at 8:44
user132520user132520
391245
391245
Related: Cannot install Ubuntu in VirtualBox due to " this kernel requires an x86-64 CPU, but only detects an i686 CPU, unable to boot" error
– kiri
Jan 3 '14 at 21:05
add a comment |
Related: Cannot install Ubuntu in VirtualBox due to " this kernel requires an x86-64 CPU, but only detects an i686 CPU, unable to boot" error
– kiri
Jan 3 '14 at 21:05
Related: Cannot install Ubuntu in VirtualBox due to " this kernel requires an x86-64 CPU, but only detects an i686 CPU, unable to boot" error
– kiri
Jan 3 '14 at 21:05
Related: Cannot install Ubuntu in VirtualBox due to " this kernel requires an x86-64 CPU, but only detects an i686 CPU, unable to boot" error
– kiri
Jan 3 '14 at 21:05
add a comment |
2 Answers
2
active
oldest
votes
Before changing BIOS settings we may want to see if hardware virtualization (VT-x for Intel, AMD-V for AMD processors) is supported by our CPU.
From a terminal issue
grep --color vmx /proc/cpuinfo ## for an Intel processor
grep --color svm /proc/cpuinfo ## for an AMD processor
If virtualization was supported the flag vmx (for Intel CPUs) or svm (for AMD CPUs) will be colored.
In case the CPU supports hardware virtualization, we need to enable it in the computer BIOS to be able to use it.
Also read How to determine if CPU VT extensions are enabled in bios? for other approaches.
Enter the BIOS (often pressing Del or F12 while booting) and see with the manual how it is named there. Search for Virtualization, Virtualization Technology (VT-x), or similar, here shown for an Award BIOS:
For an example screenshot of an Asus EFI-BIOS see this answer on SU.
Set this entry to Enabled in case it is not yet set.
We then can choose to use hardware virtualization in the virtual machine's System -> Acceleration settings:
By this we use hardware virtualization for optimal performance, and we would even be able to run a 64-bit guest OS on a 32-bit host for testing.
edited Mar 1 at 8:20
dessert
25.3k673107
answered Feb 16 '13 at 12:21
TakkatTakkat
108k37252379
4
I still get this problem. My 'vmx' is coloured when running the command above and I've gone and enabled 'virtualisation' in the BIOS as well.
– Ads20000
May 29 '14 at 14:39
2
After changing the bios setting to ON, don't just restart your computer, turn it off and then on! Apparently just restart doesn't do the thing :/
– Boris Churzin
Jul 19 '14 at 18:54
2
In my case 'vmx' was colored. But when I checked BIOS 'virtualisation' wasn't enabled. So it seems checking terminal command suggested by Takkat isn't a confirmation that 'virtualisation' is enabled.
– Kaushik Acharya
Dec 24 '14 at 9:41
2
@KaushikAcharya: thank you for pointing this out.. The terminal commands for CPU flags were suggested by an edit from another user. I admit I had not tested them thoroughly - my bad. Nevertheless they are useful to see whether the CPU in our system does support virtualization at all.
– Takkat
Dec 24 '14 at 10:19
1
Just in case anyone has an HP computer, VT-x is in BIOS/Security/System Security.
– user1350992
Jul 19 '15 at 17:32
|
show 1 more comment
I had the same exact error, and fixed it by dropping the 4095 GB to 3072 MB (3 GB). This is because it was 32-bit. I think the more than 3 GB is throwing it off.
answered Aug 6 '15 at 20:08
AnonAnon
6111
I had the same experience - despite the articles I was finding saying that the BIOS needs to be modified, the issue apparently lied in that I tried upping the memory for the virtual machine and it apparently was more than the 32-bit system could handle.
– PromInc
Sep 23 '15 at 13:53
add a comment |
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f256792%2fhow-do-i-enable-hardware-virtualization-technology-vt-x-for-use-in-virtualbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Before changing BIOS settings we may want to see if hardware virtualization (VT-x for Intel, AMD-V for AMD processors) is supported by our CPU.
From a terminal issue
grep --color vmx /proc/cpuinfo ## for an Intel processor
grep --color svm /proc/cpuinfo ## for an AMD processor
If virtualization was supported the flag vmx (for Intel CPUs) or svm (for AMD CPUs) will be colored.
In case the CPU supports hardware virtualization, we need to enable it in the computer BIOS to be able to use it.
Also read How to determine if CPU VT extensions are enabled in bios? for other approaches.
Enter the BIOS (often pressing Del or F12 while booting) and see with the manual how it is named there. Search for Virtualization, Virtualization Technology (VT-x), or similar, here shown for an Award BIOS:
For an example screenshot of an Asus EFI-BIOS see this answer on SU.
Set this entry to Enabled in case it is not yet set.
We then can choose to use hardware virtualization in the virtual machine's System -> Acceleration settings:
By this we use hardware virtualization for optimal performance, and we would even be able to run a 64-bit guest OS on a 32-bit host for testing.
edited Mar 1 at 8:20
dessert
25.3k673107
answered Feb 16 '13 at 12:21
TakkatTakkat
108k37252379
4
I still get this problem. My 'vmx' is coloured when running the command above and I've gone and enabled 'virtualisation' in the BIOS as well.
– Ads20000
May 29 '14 at 14:39
2
After changing the bios setting to ON, don't just restart your computer, turn it off and then on! Apparently just restart doesn't do the thing :/
– Boris Churzin
Jul 19 '14 at 18:54
2
In my case 'vmx' was colored. But when I checked BIOS 'virtualisation' wasn't enabled. So it seems checking terminal command suggested by Takkat isn't a confirmation that 'virtualisation' is enabled.
– Kaushik Acharya
Dec 24 '14 at 9:41
2
@KaushikAcharya: thank you for pointing this out.. The terminal commands for CPU flags were suggested by an edit from another user. I admit I had not tested them thoroughly - my bad. Nevertheless they are useful to see whether the CPU in our system does support virtualization at all.
– Takkat
Dec 24 '14 at 10:19
1
Just in case anyone has an HP computer, VT-x is in BIOS/Security/System Security.
– user1350992
Jul 19 '15 at 17:32
|
show 1 more comment
Before changing BIOS settings we may want to see if hardware virtualization (VT-x for Intel, AMD-V for AMD processors) is supported by our CPU.
From a terminal issue
grep --color vmx /proc/cpuinfo ## for an Intel processor
grep --color svm /proc/cpuinfo ## for an AMD processor
If virtualization was supported the flag vmx (for Intel CPUs) or svm (for AMD CPUs) will be colored.
In case the CPU supports hardware virtualization, we need to enable it in the computer BIOS to be able to use it.
Also read How to determine if CPU VT extensions are enabled in bios? for other approaches.
Enter the BIOS (often pressing Del or F12 while booting) and see with the manual how it is named there. Search for Virtualization, Virtualization Technology (VT-x), or similar, here shown for an Award BIOS:
For an example screenshot of an Asus EFI-BIOS see this answer on SU.
Set this entry to Enabled in case it is not yet set.
We then can choose to use hardware virtualization in the virtual machine's System -> Acceleration settings:
By this we use hardware virtualization for optimal performance, and we would even be able to run a 64-bit guest OS on a 32-bit host for testing.
edited Mar 1 at 8:20
dessert
25.3k673107
answered Feb 16 '13 at 12:21
TakkatTakkat
108k37252379
4
I still get this problem. My 'vmx' is coloured when running the command above and I've gone and enabled 'virtualisation' in the BIOS as well.
– Ads20000
May 29 '14 at 14:39
2
After changing the bios setting to ON, don't just restart your computer, turn it off and then on! Apparently just restart doesn't do the thing :/
– Boris Churzin
Jul 19 '14 at 18:54
2
In my case 'vmx' was colored. But when I checked BIOS 'virtualisation' wasn't enabled. So it seems checking terminal command suggested by Takkat isn't a confirmation that 'virtualisation' is enabled.
– Kaushik Acharya
Dec 24 '14 at 9:41
2
@KaushikAcharya: thank you for pointing this out.. The terminal commands for CPU flags were suggested by an edit from another user. I admit I had not tested them thoroughly - my bad. Nevertheless they are useful to see whether the CPU in our system does support virtualization at all.
– Takkat
Dec 24 '14 at 10:19
1
Just in case anyone has an HP computer, VT-x is in BIOS/Security/System Security.
– user1350992
Jul 19 '15 at 17:32
|
show 1 more comment
Before changing BIOS settings we may want to see if hardware virtualization (VT-x for Intel, AMD-V for AMD processors) is supported by our CPU.
From a terminal issue
grep --color vmx /proc/cpuinfo ## for an Intel processor
grep --color svm /proc/cpuinfo ## for an AMD processor
If virtualization was supported the flag vmx (for Intel CPUs) or svm (for AMD CPUs) will be colored.
In case the CPU supports hardware virtualization, we need to enable it in the computer BIOS to be able to use it.
Also read How to determine if CPU VT extensions are enabled in bios? for other approaches.
Enter the BIOS (often pressing Del or F12 while booting) and see with the manual how it is named there. Search for Virtualization, Virtualization Technology (VT-x), or similar, here shown for an Award BIOS:
For an example screenshot of an Asus EFI-BIOS see this answer on SU.
Set this entry to Enabled in case it is not yet set.
We then can choose to use hardware virtualization in the virtual machine's System -> Acceleration settings:
By this we use hardware virtualization for optimal performance, and we would even be able to run a 64-bit guest OS on a 32-bit host for testing.
edited Mar 1 at 8:20
dessert
25.3k673107
answered Feb 16 '13 at 12:21
TakkatTakkat
108k37252379
Before changing BIOS settings we may want to see if hardware virtualization (VT-x for Intel, AMD-V for AMD processors) is supported by our CPU.
From a terminal issue
grep --color vmx /proc/cpuinfo ## for an Intel processor
grep --color svm /proc/cpuinfo ## for an AMD processor
If virtualization was supported the flag vmx (for Intel CPUs) or svm (for AMD CPUs) will be colored.
In case the CPU supports hardware virtualization, we need to enable it in the computer BIOS to be able to use it.
Also read How to determine if CPU VT extensions are enabled in bios? for other approaches.
Enter the BIOS (often pressing Del or F12 while booting) and see with the manual how it is named there. Search for Virtualization, Virtualization Technology (VT-x), or similar, here shown for an Award BIOS:
For an example screenshot of an Asus EFI-BIOS see this answer on SU.
Set this entry to Enabled in case it is not yet set.
We then can choose to use hardware virtualization in the virtual machine's System -> Acceleration settings:
By this we use hardware virtualization for optimal performance, and we would even be able to run a 64-bit guest OS on a 32-bit host for testing.
edited Mar 1 at 8:20
dessert
25.3k673107
answered Feb 16 '13 at 12:21
TakkatTakkat
108k37252379
edited Mar 1 at 8:20
dessert
25.3k673107
edited Mar 1 at 8:20
dessert
25.3k673107
edited Mar 1 at 8:20
dessert
25.3k673107
25.3k673107
answered Feb 16 '13 at 12:21
TakkatTakkat
108k37252379
answered Feb 16 '13 at 12:21
TakkatTakkat
108k37252379
answered Feb 16 '13 at 12:21
TakkatTakkat
108k37252379
108k37252379
4
I still get this problem. My 'vmx' is coloured when running the command above and I've gone and enabled 'virtualisation' in the BIOS as well.
– Ads20000
May 29 '14 at 14:39
2
After changing the bios setting to ON, don't just restart your computer, turn it off and then on! Apparently just restart doesn't do the thing :/
– Boris Churzin
Jul 19 '14 at 18:54
2
In my case 'vmx' was colored. But when I checked BIOS 'virtualisation' wasn't enabled. So it seems checking terminal command suggested by Takkat isn't a confirmation that 'virtualisation' is enabled.
– Kaushik Acharya
Dec 24 '14 at 9:41
2
@KaushikAcharya: thank you for pointing this out.. The terminal commands for CPU flags were suggested by an edit from another user. I admit I had not tested them thoroughly - my bad. Nevertheless they are useful to see whether the CPU in our system does support virtualization at all.
– Takkat
Dec 24 '14 at 10:19
1
Just in case anyone has an HP computer, VT-x is in BIOS/Security/System Security.
– user1350992
Jul 19 '15 at 17:32
|
show 1 more comment
4
I still get this problem. My 'vmx' is coloured when running the command above and I've gone and enabled 'virtualisation' in the BIOS as well.
– Ads20000
May 29 '14 at 14:39
2
After changing the bios setting to ON, don't just restart your computer, turn it off and then on! Apparently just restart doesn't do the thing :/
– Boris Churzin
Jul 19 '14 at 18:54
2
In my case 'vmx' was colored. But when I checked BIOS 'virtualisation' wasn't enabled. So it seems checking terminal command suggested by Takkat isn't a confirmation that 'virtualisation' is enabled.
– Kaushik Acharya
Dec 24 '14 at 9:41
2
@KaushikAcharya: thank you for pointing this out.. The terminal commands for CPU flags were suggested by an edit from another user. I admit I had not tested them thoroughly - my bad. Nevertheless they are useful to see whether the CPU in our system does support virtualization at all.
– Takkat
Dec 24 '14 at 10:19
1
Just in case anyone has an HP computer, VT-x is in BIOS/Security/System Security.
– user1350992
Jul 19 '15 at 17:32
4
4
I still get this problem. My 'vmx' is coloured when running the command above and I've gone and enabled 'virtualisation' in the BIOS as well.
– Ads20000
May 29 '14 at 14:39
I still get this problem. My 'vmx' is coloured when running the command above and I've gone and enabled 'virtualisation' in the BIOS as well.
– Ads20000
May 29 '14 at 14:39
2
2
After changing the bios setting to ON, don't just restart your computer, turn it off and then on! Apparently just restart doesn't do the thing :/
– Boris Churzin
Jul 19 '14 at 18:54
After changing the bios setting to ON, don't just restart your computer, turn it off and then on! Apparently just restart doesn't do the thing :/
– Boris Churzin
Jul 19 '14 at 18:54
2
2
In my case 'vmx' was colored. But when I checked BIOS 'virtualisation' wasn't enabled. So it seems checking terminal command suggested by Takkat isn't a confirmation that 'virtualisation' is enabled.
– Kaushik Acharya
Dec 24 '14 at 9:41
In my case 'vmx' was colored. But when I checked BIOS 'virtualisation' wasn't enabled. So it seems checking terminal command suggested by Takkat isn't a confirmation that 'virtualisation' is enabled.
– Kaushik Acharya
Dec 24 '14 at 9:41
2
2
@KaushikAcharya: thank you for pointing this out.. The terminal commands for CPU flags were suggested by an edit from another user. I admit I had not tested them thoroughly - my bad. Nevertheless they are useful to see whether the CPU in our system does support virtualization at all.
– Takkat
Dec 24 '14 at 10:19
@KaushikAcharya: thank you for pointing this out.. The terminal commands for CPU flags were suggested by an edit from another user. I admit I had not tested them thoroughly - my bad. Nevertheless they are useful to see whether the CPU in our system does support virtualization at all.
– Takkat
Dec 24 '14 at 10:19
1
1
Just in case anyone has an HP computer, VT-x is in BIOS/Security/System Security.
– user1350992
Jul 19 '15 at 17:32
Just in case anyone has an HP computer, VT-x is in BIOS/Security/System Security.
– user1350992
Jul 19 '15 at 17:32
|
show 1 more comment
I had the same exact error, and fixed it by dropping the 4095 GB to 3072 MB (3 GB). This is because it was 32-bit. I think the more than 3 GB is throwing it off.
answered Aug 6 '15 at 20:08
AnonAnon
6111
I had the same experience - despite the articles I was finding saying that the BIOS needs to be modified, the issue apparently lied in that I tried upping the memory for the virtual machine and it apparently was more than the 32-bit system could handle.
– PromInc
Sep 23 '15 at 13:53
add a comment |
I had the same exact error, and fixed it by dropping the 4095 GB to 3072 MB (3 GB). This is because it was 32-bit. I think the more than 3 GB is throwing it off.
answered Aug 6 '15 at 20:08
AnonAnon
6111
I had the same experience - despite the articles I was finding saying that the BIOS needs to be modified, the issue apparently lied in that I tried upping the memory for the virtual machine and it apparently was more than the 32-bit system could handle.
– PromInc
Sep 23 '15 at 13:53
add a comment |
I had the same exact error, and fixed it by dropping the 4095 GB to 3072 MB (3 GB). This is because it was 32-bit. I think the more than 3 GB is throwing it off.
answered Aug 6 '15 at 20:08
AnonAnon
6111
I had the same exact error, and fixed it by dropping the 4095 GB to 3072 MB (3 GB). This is because it was 32-bit. I think the more than 3 GB is throwing it off.
answered Aug 6 '15 at 20:08
AnonAnon
6111
answered Aug 6 '15 at 20:08
AnonAnon
6111
answered Aug 6 '15 at 20:08
AnonAnon
6111
answered Aug 6 '15 at 20:08
AnonAnon
6111
6111
I had the same experience - despite the articles I was finding saying that the BIOS needs to be modified, the issue apparently lied in that I tried upping the memory for the virtual machine and it apparently was more than the 32-bit system could handle.
– PromInc
Sep 23 '15 at 13:53
add a comment |
I had the same experience - despite the articles I was finding saying that the BIOS needs to be modified, the issue apparently lied in that I tried upping the memory for the virtual machine and it apparently was more than the 32-bit system could handle.
– PromInc
Sep 23 '15 at 13:53
I had the same experience - despite the articles I was finding saying that the BIOS needs to be modified, the issue apparently lied in that I tried upping the memory for the virtual machine and it apparently was more than the 32-bit system could handle.
– PromInc
Sep 23 '15 at 13:53
I had the same experience - despite the articles I was finding saying that the BIOS needs to be modified, the issue apparently lied in that I tried upping the memory for the virtual machine and it apparently was more than the 32-bit system could handle.
– PromInc
Sep 23 '15 at 13:53
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2f256792%2fhow-do-i-enable-hardware-virtualization-technology-vt-x-for-use-in-virtualbox%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
Related: Cannot install Ubuntu in VirtualBox due to " this kernel requires an x86-64 CPU, but only detects an i686 CPU, unable to boot" error
– kiri
Jan 3 '14 at 21:05