Opened 9 years ago
Closed 9 years ago
#15178 closed defect (fixed)
VT-x/AMD-V stays enabled even if I uncheck it in Settings
Reported by: | Fifo F. | Owned by: | |
---|---|---|---|
Component: | VMM/HWACCM | Version: | VirtualBox 5.0.14 |
Keywords: | VT-x, AMD-V, | Cc: | |
Guest type: | all | Host type: | Mac OS X |
Description
VT-x/AMD-V stays enabled even if I uncheck it in the VM’s settings window – nothing helps to disable it.
VBox.log and screenshots are attached.
The guest freezes if I try to do anything in it. Also I’m encountering graphical glitches in it.
I could disable virtualisation completely in earlier versions of VirtualBox.
Attachments (2)
Change History (7)
by , 9 years ago
Attachment: | Screen Shot 2016-02-25 at 13.10.52.png added |
---|
by , 9 years ago
Attachment: | Screen Shot 2016-02-25 at 13.07.44.png added |
---|
Screenshot of VM settings showing VT-x disabled
follow-up: 2 comment:1 by , 9 years ago
That's expected behavior. The only problem is that we need to properly reflect the state which is currently not done. On Mac OS X it's not possible to disable VT-x. All Intel processors which were ever used by Apple support VT-x so there is no reason to support non-VT-x virtualization on Mac OS X.
comment:2 by , 9 years ago
Replying to frank:
That's expected behavior. The only problem is that we need to properly reflect the state which is currently not done. On Mac OS X it's not possible to disable VT-x. All Intel processors which were ever used by Apple support VT-x so there is no reason to support non-VT-x virtualization on Mac OS X.
Older OSes like Windows 2.x/3.x seem to hate VT-x and display graphical glitches all over the screen. How do I fix that?
follow-up: 4 comment:3 by , 9 years ago
If you experience problems with VT-x then this is a different issue and you should open a separate ticket for it. But supporting that ancient (older is not the right word) Windows versions has low priority. No question this should be fixed but there are more important problems.
comment:4 by , 9 years ago
Replying to frank:
If you experience problems with VT-x then this is a different issue and you should open a separate ticket for it. But supporting that ancient (older is not the right word) Windows versions has low priority. No question this should be fixed but there are more important problems.
Well, I’ll just give up trying to run older Windows versions under VBox/trying to disable VT-x.
comment:5 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fix is part of VBox 5.0.16 (VT-x cannot be disabled any longer).
Screenshot of VT-x enabled (bottom right corner)