#18965 closed defect (invalid)
User Manual error (I think)
Reported by: | Mark Filipak | Owned by: | |
---|---|---|---|
Component: | documentation | Version: | VirtualBox 6.0.12 |
Keywords: | VT-x/AMD-V | Cc: | |
Guest type: | Linux | Host type: | Windows |
Description
3.5.2 Processor Tab \n Enable Nested VT-x/AMD-V \n "This feature is available on host systems that use an AMD CPU. For Intel CPUs, the option is grayed out."
"grayed out"? Not true. Further, I have an Intel processor, and if I don't select "[_] Enable VT-x/AMD-V" in 'Settings' 'System' _/Acceleration\_, VBox complains.
I think this is simply a User Manual error. I could be wrong and it's a bug, but I think not. Please advise.
Regards, Mark Filipak.
Attachments (1)
Change History (10)
comment:1 by , 5 years ago
by , 5 years ago
Attachment: | screenshot.png added |
---|
comment:2 by , 5 years ago
The attached screenshot shows that 'Enable VT-x/AMD-V' defaults to ON and complains if I set it OFF. Further, if I leave it OFF, it is "enabled automatically", as the note promises. I DO HAVE an Intel processor, not AMD.
comment:3 by , 5 years ago
First of all, let's get things straight... Your ticket is not about the "Enable VT-x/AMD-V", but (as you originally said) it's about the "Enable Nested VT-x/AMD-V" under the VM Settings » System » Processor » Enable Nested VT-x/AMD-V. Those are different settings and you might have confused the two:
- VM Settings » System » Acceleration » Enable VT-x/AMD-V
- VM Settings » System » Acceleration » Enable Nested Paging
- VM Settings » System » Processor » Enable Nested VT-x/AMD-V
Again, the User Manual is correct on this. Your ticket should be closed as [Invalid] because what you thought of as an issue with the User Manual is, well ... invalid.
Now, even though this is a different issue, the "Enable VT-x/AMD-V" is required because (as you can clearly see in the warning) the VM's setup needs it, not sure what the problem is.
follow-up: 6 comment:4 by , 5 years ago
Well, I didn't know there was a 'Enable Nested VT-x/AMD-V' option under a differing tab. My bad.
comment:5 by , 5 years ago
Perhaps if 'Enable VT-x/AMD-V' & 'Enable Nested VT-x/AMD-V' were on the same page, with an explanatory note, ignorant users like me wouldn't make the mistake. You know, I'm here because I'm trying to be a good netcitizen and help the VBox team.
comment:6 by , 5 years ago
Replying to comment 4 by MarkFilipak:
Well, I didn't know there was a 'Enable Nested VT-x/AMD-V' option under a differing tab. My bad.
Don't worry, it happens. To tell you the truth, it is rather confusing if you look at it... I'll take this opportunity and suggest that the "Enable Nested VT-x/AMD-V" be changed to "Enable Nested Virtualization", as to avoid the similarities in the terminology.
Replying to comment 5 by MarkFilipak:
Perhaps if 'Enable VT-x/AMD-V' & 'Enable Nested VT-x/AMD-V' were on the same page
No, on this one I'm not with you... ;)
These are different features, one referring to the host (Nested Virtualization) the other to the features presented to the guest (Nested VT-x/AMD-V). They do belong in different tabs.
Replying to comment 5 by MarkFilipak:
You know, I'm here because I'm trying to be a good netcitizen and help the VBox team.
Much appreciated, and believe me, I can understand that better than most; you see I'm a volunteer too... ;)
comment:7 by , 5 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
follow-up: 9 comment:8 by , 5 years ago
@MarkFilipak
Good news (maybe?). If you download any development build higher than the original 6.1.0b1 (r133315), the following setting is gone:
- VM Settings » System » Acceleration » Enable VT-x/AMD-V
So, no more confusion I guess... ;)
comment:9 by , 5 years ago
You read about 6.1.0b1 (r133315) and thought of me and came back here to tell me? Socratus, you're too much. You . are . a . prince ! Live long and prosper.
Replying to MarkFilipak:
Yes true. Unless you're using the 6.1.0b1, that setting is disabled and greyed out if your CPU is an Intel one. And even in 6.1.0b1, you have to manually enable it from the command line before it's not greyed out any more. Not sure what you're seeing here, are you sure you are looking at that setting?
Of course it will, depending on the rest of the options.
You see... that's not what the bugtracker is for. It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.
For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".