Bug 239835

Summary:

emulators/virtualbox-ose doesn't recognize AMD Ryzen 7 3800X "SVM" feature - won't allow 64-bit guests

Product:

Ports & Packages

Reporter:

Jim D. <radicleparticles>

Component:

Individual Port(s)

Assignee:

Virtualbox Team (Nobody) <vbox>

Status:

Closed Works As Intended

Severity:

Affects Many People

CC:

madpilot

Priority:

---

Keywords:

needs-patch

Version:

Latest

Flags:

bugzilla: maintainer-feedback? (vbox)

Hardware:

amd64

OS:

Any

Attachments:

Description	Flags
Screen shot showing CPU type selections are now 32-bit only	none
VBox machine startup error message about no recognizable virtualization support	none
MSI MEG X570 ACE BIOS settings relevant to virtulization	none
Verification of MSI MB virtualization controls enabled	none
OS boot messages verifying AMD SVM enabled	none
Additional verification of SVM ("Intel Secure Ring")	none

Description Jim D. 2019-08-14 01:17:39 UTC

Created attachment 206506 [details]
Screen shot showing CPU type selections are now 32-bit only

H/W: AMD Ryzen 7 3800X CPU, MSI MEG X570 ACE MB (no option to enable or disable virtualization)

Relevant DMESG line: 
AMDFeatures2=0x75c237ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,IBS,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX,

AMD Virtualization Reference:
https://en.wikipedia.org/wiki/X86_virtualization#AMD_virtualization_(AMD-V)

Relevant text:
'The CPU flag for AMD-V is "svm". This may be checked in BSD derivatives via dmesg or sysctl and in Linux via /proc/cpuinfo.'

Previously created 64-bit VBox machines on earlier H/W and VBox are no longer "defined" as 64-bit machines. All machine type selections are now 32-bit only (see 'FBSD-VBox-5.2.18_no_64_bit.png' screen shot).

Attempting to start a previously configured 64-bit VM now results in an error message (see 'FBSD-VBox-5.2.18_no_VTx_AMD-V_HW.png' screen shot) which further informs that CPU virtualization support is "missing".

Comment 1 Jim D. 2019-08-14 01:18:59 UTC

Created attachment 206507 [details]
VBox machine startup error message about no recognizable virtualization support

Comment 2 Jim D. 2019-08-14 01:20:41 UTC

Could not find any relevant documentation at VirtualBox.org about CPU virtualization support or detection.

Comment 3 Jim D. 2019-08-14 11:52:35 UTC

Created attachment 206523 [details]
MSI MEG X570 ACE BIOS settings relevant to virtulization

Two bits of information that I didn't have before:
a) AMD virtualization (AMD-V) is also referred to as "SVM"
b) MB virtualization settings are in Overclocking area which I skimmed over without making any changes upon initial system installation

Needed to enable IOMMU and SVM Mode

Comment 4 Jim D. 2019-08-14 11:54:39 UTC

Created attachment 206525 [details]
Verification of MSI MB virtualization controls enabled

Exiting from BIOS setup showing settings changes ("Global C-state" can be ignored)

Comment 5 Jim D. 2019-08-14 11:57:23 UTC

Created attachment 206526 [details]
OS boot messages verifying AMD SVM enabled

FBSD boot messages showing expanded list of AMD CPU features now including expanded SVM list.

Comment 6 Jim D. 2019-08-14 12:00:05 UTC

Created attachment 206528 [details]
Additional verification of SVM ("Intel Secure Ring")

More OS boot messages indicating active AMD SVM

Comment 7 Jim D. 2019-08-14 12:02:16 UTC

So, I now have AMD-V (SVM) enabled and VirtualBox-5.2.18 recognizes 64-bit VM. So this PR can be closed.

Comment 8 Jim D. 2019-08-14 12:04:17 UTC

VirtualBox Machine/Session Information now shows "VT-x/AMD-V" as Active.

Comment 9 Jim D. 2019-08-14 12:07:51 UTC

One last clue that pointed me in the right direction came from,

[Solved] No virtualization support with Gigabyte GA-AB350 Gaming 3?
https://forum.level1techs.com/t/solved-no-virtualization-support-with-gigabyte-ga-ab350-gaming-3/114171

Comment 10 Jim D. 2021-11-23 10:51:12 UTC

This problem report may be closed.

Comment 11 Guido Falsi freebsd_committer

2021-11-23 14:39:03 UTC

Close on submitter request.