Amd svm mode: What is SVM Mode in your BIOS?

What is SVM Mode in your BIOS?

What is SVM Mode in your BIOs? Are there other, similar options you should keep an eye out for?

What even is this “Virtualization” that’s being thrown around alongside SVM?

In this article, I’m going to walk you through everything you need to know about SVM Mode.

What is SVM Mode In Your BIOs?

SVM Mode is an option within an AMD motherboard’s BIOS to enable what’s called a Secure Virtual Machine.

In addition to providing a secure virtual machine environment, SVM also allows for more direct access to the hardware than without. This means increased performance when using Virtual Machines, which is the main benefit of enabling specialized BIOS options like this.

Besides being called SVM, AMD also calls the technology AMD-V, so it may be listed in your BIOS under that name.

Of course, this begs the immediate question if you’re an Intel user: do you have an equivalent in your BIOS?

Is There an Intel Equivalent to SVM Mode?

Yes, there is an Intel equivalent to AMD-V/SVM Mode called Intel VT-x, or Intel Virtualization.

Pretty much, just look for a virtualization-related option in your BIOS and you should be able to find it.

What Is A Virtual Machine?

A Virtual Machine basically serves as an isolated instance of another operating system being run within a program on your main operating system.

It isn’t the same as a separate operating system entirely, since that requires an entirely separate disk partition.

Using Virtual Machine applications like VMWare or VirtualBox, you can run an isolated OS within your main OS without needing to reboot to switch partitions or need to set up a separate OS install partition at all.

For instance, you can use this to run a Mac or Linux Virtual Machine within a Windows OS.

Does Enabling Virtualization Impact Performance?

Outside of using the virtual machine itself, performance for the rest of your PC running normally, shouldn’t be impacted by enabling virtualization.

However, there are mixed reports about some virtualization options taking up extra performance or causing minor issues when they’re enabled, so I wouldn’t recommend enabling virtualization when it isn’t in active use.

Now, within the Virtual Machine itself, how is performance impacted compared to a proper operating system installation?

This can vary depending on numerous factors, but overall since Virtual Machines have little (if any) direct access to the hardware, there is a significant performance penalty when running something in a VM compared to not using virtualization at all.

Virtualization has some commonalities with emulation in this and other regards, but the two aren’t quite the same. Where emulation uses software to emulate hardware, virtualization is more about creating an independent operating environment for a separate OS that has part or all of the host machine’s hardware resources assigned.

The performance overhead from virtualization is quite minor compared to the cost of emulation.

What Kind of Use Cases Need Virtualization?

So, when do you actually need to start considering Virtualization?

Let’s talk about some scenarios where virtualization can come in handy.

In servers and data centers, virtualization is used fairly often to divide resources.

If you’ve ever used a service like Google Stadia or GeForce Now, you’re actually streaming the game from one of many virtual machines in a particular server farm.

In scenarios like this, resources like total CPU cores are usually divided evenly between however many VMs are present.

Outside of those server-grade scenarios, here’s where you might need to use virtualization:

  • For testing or developing applications for other operating systems. For instance, an Android or macOS VM on a Windows machine can be extremely handy for an Android app developer.
  • For fun and games…from other operating systems. If you’re a hardcore PC gamer and need access to play that hot Android game all your friends are playing without using a phone? An Android VM like BlueStacks is an ideal choice for you.
  • For using productivity software from another OS. Say you’ve recently switched to Windows from Mac OS and are missing your favorite OS X tools. With virtualization, you can still access those applications, allowing you to skip learning a new workflow for a new application.
  • For when you have multiple people use one machine and want something more secure than Windows User Accounts or Users in need of different Operating Systems. Use a solution like Unraid to preserve hardware performance if you’re using a solution like this, though.


What if SVM Mode isn’t in my BIOS?

Well, first verify that you aren’t using an Intel processor.

If you’re using an Intel processor and motherboard, you’ll need to enable Intel VT-x or another Enable Virtualization option in your Intel BIOS.

If you are using an AMD processor, it may also be called AMD-V instead of SVM Mode.

Basically what you’re doing is looking for your relevant BIOS option for enabling virtualization.

How do I check if virtualization is enabled?

A pretty easy way to do this is to open the Performance tab in Task Manager on Windows (CTRL+SHIFT+ESC).

Select CPU, and near the bottom where your various CPU specs are listed, you should see if Virtualization is enabled or not under “Logical processors”.

Is a Virtual Machine less powerful than a regular Operating System?


For one, virtualization by its very own nature is going to introduce some overhead.

It’s hard to pin down exactly how much since it can change depending on a variety of factors, but expect at least somewhere in the range of a 5% performance deficit for your CPU and memory. This deficit shouldn’t stack per-VM, though.

Depending on the solution, virtual machines can operate surprisingly close to the original hardware.

For example, Unraid can be used to turn a single PC into two or more by dividing up available resources.

This is good enough at utilizing the hardware that it’s used for gaming purposes, and LinusTechTips infamously managed to get 10 gaming rigs running off of a single machine using this Virtualization software:


SVM mode is a technology that allows your system to run virtual machines. It does not affect gaming or regular performance. However, if need to run virtual machines or gaming emulator like Bluestacks, it will definitely allow them to run more efficiently. 

Should You Enable SVM?

As long as you are not using any virtual machine or gaming emulators, it’s better to keep the SVM mode disabled. Some people claim that SVM mode negatively impacts regular performance when it’s on, but in reality, you should not experience performance degradation when you are not using any virtual machine or other programs that use SVM technology.  



SVM (Secure Virtual Machine) allows you to use programs like VMware and emulators at fast speed. As mentioned before, Android emulators like Bluestacks recommend users to enable SVM mode for better performance. 

It creates a safe environment where you can simultaneously use multiple operating systems. Just enabling the SVM mode will not offer plenty of advantages, but the programs SVM lets you run can be used to do things that are impossible without this tech.


According to some people, SVM has disadvantages because it divides the hardware resources so multiple programs can utilize them and run simultaneously. 

But it’s not a disadvantage; that’s the whole point. Even if you don’t use any virtualization software when your SVM mode is on, it does not cause any performance issues.


If you can find SVM mode in your BIOS settings, you are probably looking in the wrong menu. The User interface of BIOS can be different depending upon your motherboard manufacturer and series.  

BIOS -> Advanced -> CPU Configuration -> SVM Mode -> enabled

If you still can’t find the SVM mode option, use Speccy to check if your hardware is virtualization compatible or not. 


Sometimes computers refuse to boot up after enabling SVM mode and only show a black screen. There can be multiple reasons that can cause this issue, including outdated BIOS and chipset drivers.

In some instances, the computer boots up normally after enabling SVM, but once you attempt to use programs like Windows Sandbox, it throws a dialog with “Virtualization is disabled in the firmware” message. Below we have mentioned two solutions to fix the black screen issue, hopefully, they will fix the issue. 

Solution 1) Update BIOS and Chipset Drivers

If your PC is unable to boot up right after enabling the SVM mode in BIOS settings. Disable the SVM mode, and your PC should boot up normally. Then update your BIOS and chipset drivers. Also, upgrade to a newer version of Windows 10 and try enabling the SVM mode again. 

Solution 2) Disable and Re-enable the Program You Are Using

If you are using a corrupted program, it may also cause black screen issues. 

For example, if you are using Windows Sandbox, follow the steps mentioned below:

  1. Go to Control Panel.
  2. Click on Programs and features.
  3. On the left-hand side, click on Turn Windows features on or off.
  4. Now in the dialog box, scroll down and uncheck the option: Windows Sandbox.
  5. Finally, restart the computer.

Once your PC turns on, try to enable the Windows Sandbox again with SVM enabled. 

If you are using a third-party program, uninstall and reinstall to fix the issue. 


Read More
  1. What Is D-Ram Frequency? 
  2. How to Change CPU Fan Speed Without BIOS?
  3. What Is D.O. C.P? and How to Enable/Disable It?
  4. What Is Launch CSM Option? 
  5. What is Microsoft Virtual WiFi Miniport Adapter?
  6. What is FCLK Frequency? 
  7. What Does Erp-Ready Mean in Bios?
  8. What is XHCI hand off? Should you enable it?

Enable virtualization on Windows 11 PCs

Virtualization lets your PC emulate a different operating system, like Android™ or Linux. Enabling virtualization gives you access to a larger library of apps to use and install on your PC. If you upgraded from Windows 10 to Windows 11 on your PC, these steps will help you enable virtualization.

Note: Many Windows 10 PCs—and all PCs that come preinstalled with Windows 11—already have virtualization enabled, so you may not need to follow these steps.

Before you begin, determine your device model and manufacturer. You’ll need this info later in the process. 

Before you begin, we recommend opening this page on a different device. Here’s how to get to the UEFI from Windows:

  1. Save your work and close any open apps.

  2. Select Start  > Settings > System Recovery > Advanced startup, then select Restart now.

  3. Once your PC restarts, you’ll see a screen that displays Choose an option. Select Troubleshoot > Advanced options > UEFI Settings > Restart.

  4. Your PC will restart again and you’ll be in the UEFI utility. At this step, you might see the UEFI referred to as the BIOS on your PC.

The way the UEFI (or BIOS) appears depends on your PC manufacturer. Once you’ve enabled virtualization and exited the UEFI, your PC will restart.     

Important: Only change what you need to in the UEFI (or BIOS). Adjusting other settings might prevent you from accessing Windows. 

Instructions based on your PC manufacturer

Choose your PC manufacturer for specific instructions on enabling virtualization. If you don’t see your manufacturer listed, refer to your device documentation.

 These are external links to the manufacturers’ websites.

PC manufacturer



How to Enable Virtualization Technology on Acer Products


For PCs with AMD processors: 

[Notebook] How to enable or disable AMD Virtualization (AMD-V™) technology?

For PCs with Intel processors: 

[Motherboard] How to enable Intel(VMX) Virtualization Technology in the BIOS?

[Notebook] How to enable or disable Intel® Virtualization Technology (VT-x)?


How To Enable or Disable Hardware Virtualization on Dell Systems | Dell US


HP PCs — Enable Virtualization Technology in the BIOS


How to enable Virtualization Technology on Lenovo PC computers — Lenovo Support US


Virtualization is already enabled on Surface devices.  

Instructions based on your UEFI (or BIOS)

If your PC manufacturer isn’t listed or you’re unsure who it is, you may be able to find instructions for your UEFI (or BIOS). Choose your UEFI firmware developer for specific instructions on enabling virtualization. If you don’t see your firmware developer listed, refer to your device documentation.


Refer to your device’s firmware documentation


Refer to your device’s firmware documentation

These instructions may apply if you upgraded your PC from Windows 10 to Windows 11.

Note: Many Windows 10 PCs—and all PCs that come preinstalled with Windows 11—already have Virtual Machine Platform enabled, so you may not need to follow these steps.

Here’s how to turn it on:

  1. Select Start, enter Windows features, and select Turn Windows features on or off from the list of results.

  2.  In the Windows Features window that just opened, find Virtual Machine Platform and select it.

  3. Select OK. You might need to restart your PC.

 For more advanced info or help with troubleshooting, go to Microsoft Docs.  

Android is a trademark of Google LLC.  

Related topics

  • Install mobile apps and the Amazon Appstore

  • More help on Microsoft Docs

What is SVM Mode In BIOS? [Explained Under 2 Minutes 2021]

Some motherboard manufacturers like to bury their features in BIOS menus, which is strange considering that most of them will be useless to the majority of users. SVM (Super VGA Mode) is one of those features; it is a mode designed for overclocking and testing, and it cannot be activated after a system has been set up and assembled. This guide will show you how to activate it in BIOS, just in case you have a motherboard that has SVM Mode hidden in BIOS.

BIOS is the silicon that controls the computations of the system. BIOS is often bundled into a separate small package that can be switched to different modes such as SVM, EZ Mode, and so on, to suit different needs. These modes can be activated in BIOS by pressing a specific key.

If you come across the SVM mode in your BIOS settings, it may be perplexing.

So don’t be concerned.

I’m going to break it down for you in this article.

I’ll go through all there is to know about the SVM mode, including how to activate it and the dangers it poses.

So, what does SVM mode entail?

SVM mode is a safe virtualization technique that lets your PC serve as a host system while sharing its hardware resources with numerous virtual machines. As a result, you may effectively run several operating systems on the same computer at the same time.

Continue reading to learn all there is to know about the SVM mode.

Also, check out our separate article on how to adjust mouse acceleration in FPS games if you want to improve your shooting experience.

What Does BIOS SVM Stand For?

Secure Virtual Machine is abbreviated as SVM. A virtual machine is a computer that you may host or operate on your own personal computer. It divides and distributes your PC hardware across the many virtual machines you’re operating.

Let’s suppose you wish to install Windows 7 on your Windows 10 computer. You may accomplish so with the assistance of a virtual machine.

Here’s how to repair it if you can’t hear anybody of discord.

When you start your virtual machine, you’ll see that the various hardware resources (CPU cores, RAM capacity, and so on) are split between your Windows 10 host and your Windows 7 virtual machine.

Furthermore, and most crucially,

Your Windows 7 virtual machine will operate as if it were a real computer with its own hardware.

Turning on the SVM mode in BIOS will enable you to setup and operate virtual machines on your PC. Also, learn how to set your display to 144hz.

Does SVM Have an Impact on Performance?

SVM mode affects performance solely when running virtual machines or emulators since it is a feature for operating virtual machines (like BlueStacks). So, until you run them, your PC won’t suffer any performance degradation.

Also, learn how to go to the Steam Screenshots folder.

Regardless of whether you run a virtual machine or not, if you’ve enabled the Hyper-V Windows Feature, your PC will operate as a privileged guest.

In such case, your PC’s performance may suffer minor setbacks. The Hyper-V Windows Feature has a fault or, more accurately, an architectural weakness.

In the BIOS, where is the SVM Mode?

SVM mode may be hidden under various sub-menus depending on the motherboard manufacturer. Follow the procedures below to locate SVM mode in BIOS:

For Asus motherboards, go to http://www.

  1. Turn on your computer.
  2. Continue to hold down the Del key until the BIOS appears.
  3. To enter Advanced Mode, press F7. (On ROG series motherboards, Advanced Mode may be accessed without hitting F7).
  4. Select Advanced CPU Configuration from the drop-down menu.
  5. Look for SVM mode.

For MSI motherboards, follow these steps:

  1. Turn on the computer.
  2. Continue to hold down the Del key until the BIOS appears on the screen.
  3. Go to the Advanced tab.
  4. SVM mode may be found there.

For Gigabyte motherboards, follow these steps:

  1. Turn on the computer.
  2. Continue hitting the Del key until the BIOS appears.
  3. Go to the Advanced tab.
  4. Select Advanced CPU Settings from the drop-down menu.
  5. Look for SVM mode.

For Asrock motherboards, go to

  1. Turn on the computer.
  2. Continue pressing the Del key until the BIOS menu appears.
  3. Go to the Advanced tab.
  4. Navigate to the CPU Configuration page.
  5. Look for SVM mode.

What Does AMD SVM Stand For?

The AMD SVM was the first virtualization solution for the x86 architecture. It was later called AMD-V. (AMD Virtualization).

It’s important to remember that this is only one of the numerous names for virtualization technology.

Check your power supply as soon as possible.

Is It Safe To Use SVM?

As previously stated, using SVM while also enabling Hyper-V Windows Feature may result in minor performance degradation.

As a result, unless you’re doing virtualization activities like virtual machines or emulators, there’s no need to activate SVM.

Make sure you have adequate hardware resources before turning on SVM to operate virtual machines.

As I previously said, a virtual machine functions as if it were a distinct computer. To function, it requires its own dedicated CPU, GPU cores, storage, and free RAM.

Here’s a comprehensive tutorial to using Twitch’s host mode.

So, how do you turn on SVM in BIOS?

To activate SVM in BIOS, follow these steps:

  1. During a fast reboot, click F2 to bring up the BIOS screen.
  2. Go to Advanced > CPU Configuration.
  3. Select Enable SVM Mode from the SVM Mode drop-down menu.
  4. Press Save & Exit, and select Save Changes and Reset option.

Why is SVM turned off by default?

SVM is turned off by default for security concerns.

If a malicious hypervisor infects your computer and manages to operate beneath your main operating system, the hypervisor effectively takes control of your computer.

So, if you’re sure you want to enable virtualization, you’ll have to go into BIOS and turn it on. Check to see if pximouse tiltwheel exe is a virus.

What Should You Do If Your BIOS Doesn’t Have SVM Mode?

Hardware-based virtualization is a feature. You won’t be able to use SVM mode in BIOS if your hardware doesn’t support virtualization.

There’s more to come.

Virtualization technique is known by many names depending on your hardware, including:

  • VT-x
  • AMD-V
  • SVM
  • VT-d (Intel Virtualization Technology)
  • AMD IOMMU (Intelligent Memory Management Unit)

As a result, don’t give up if you can’t locate SVM mode. Look in your BIOS for the names listed above.

How to Fix a Black Screen in SVM Mode

Depending on the nature of the problem, there are many options for dealing with the black screen. See our other article on how to solve VLC’s inability to open MRL files.

The methods to solve SVM Black Screen Error are as follows:

1. Drivers must be updated.

If you see a black screen after activating SVM mode, it’s possible that the outdated BIOS or chipset drivers are to blame.

Consider the following:

  1. SVM mode should be turned off.
  2. Turn on the computer.
  3. Install the latest BIOS and chipset drivers.
  4. Update your operating system.
  5. Switch to SVM mode and try starting again.
2. Uninstall and reinstall the virtualization software

If you can boot into the OS but your virtualization program/software crashes, the issue is almost certainly with the software.

Follow the steps below to get started:

  1. Remove the virtualization software from your computer.
  2. Ensure that SVM mode is enabled.
  3. Install the virtualization program from scratch.

The key takeaway from approach 2 is to install the virtualization software after activating SVM mode and ensuring that it has all of the necessary rights and functionality.

Reconfigure shared memory if necessary.

The UMA (Unified Memory Architecture) settings on an AMD CPU with integrated graphics may be the issue. Because integrated graphics don’t have their own graphics memory, it deals with memory (RAM) sharing between the PC and the GPU.

The steps of reconfiguring shared memory are as follows:

  1. Go to the BIOS menu.
  2. Select Advanced from the drop-down option.
  3. Look for the UMA option.
  4. It should be set to auto.
  5. Save your modifications and restart your computer.
4. Install Windows again

If all other options fail, the only option is to reinstall the Windows operating system from scratch. Many people discovered that reinstalling Windows fixed their problems and allowed them to utilize virtualization. Before you begin, make sure you have a backup of your data.

Check out how to combine two Microsoft accounts as well.


Is it safe to enable virtualization?

Answer: Turning on virtualization poses a security risk because it allows low-level access to other programs. As a result, only enable it if you’re using virtualization.

Is it true that virtualization causes computers to slow down?

Virtualization divides hardware resources among the virtual machines in use. If you run one or more virtual machines, the computer will slow down.

Is it legal to use virtual machines?

Virtual machines are legal, according to the law. They’re mostly used for running and testing multiple operating systems on a single piece of hardware. Emulators are also run on it.

Last Thoughts

SVM mode is a fantastic feature for running virtual machines. It expands the capabilities of your computer.

You can run multiple operating systems, emulators, and other programs.

You should, however, utilize it with caution. It may cause you problems if you don’t.

Frequently Asked Questions

What is SVM mode in BIOS?

SVM stands for Supervisor Mode and is a mode that can be enabled on the BIOS. This mode will allow you to boot from a USB device, such as a flash drive or CD/DVD.

What is SVM mode?

SVM mode is a special mode that was created to make the game harder for players who are skilled.

Does SVM mode affect performance?

No, SVM mode does not affect performance.

Corey Holmes

Graphic Designer and Blogger

Indiana — based graphic designer for more than 6 years. Creator of multiple awesome print and web designs. Interested in blogging as a second addiction since 2019. 100% animal lover.

AMD Secure Encrypted Virtualization (SEV)

AMD EPYC Hardware Memory Encryption

Hardware accelerated memory encryption for data-in-use protection. Takes advantage of new security components available in AMD EPYC processors

  1. AES-128 encryption engine embedded in the memory controller. Automatically encrypts and decrypts data in main memory when an appropriate key is provided.
  2. AMD Secure Processor. Provides cryptographic functionality for secure key generation and key management.

Feature Overview

AMD Secure Memory Encryption (SME)

Uses a single key to encrypt system memory. The key is generated by the AMD Secure Processor at boot. SME requires enablement in the system BIOS or operating system. When enabled in the BIOS, memory encryption is transparent and can be run with any operating system.

AMD Secure Encrypted Virtualization (SEV)

Uses one key per virtual machine to isolate guests and the hypervisor from one another. The keys are managed by the AMD Secure Processor. SEV requires enablement in the guest operating system and hypervisor. The guest changes allow the VM to indicate which pages in memory should be encrypted. The hypervisor changes use hardware virtualization instructions and communication with the AMD Secure processor to manage the appropriate keys in the memory controller.

AMD Secure Encrypted Virtualization-Encrypted State (SEV-ES)

Encrypts all CPU register contents when a VM stops running. This prevents the leakage of information in CPU registers to components like the hypervisor, and can even detect malicious modifications to a CPU register state.


Product Briefs

White Papers & Specifications

Document Description Revision Date
SEV Secure Nested Paging
Firmware ABI Specification
Documents the API available to the host hypervisor for management of SNP-active guests. 1.51 January
Secure Encrypted Virtualization API Documents the API available to the host hypervisor for management of keys and secure data transfer between host hypervisor and guest VM memory 0.24 April
AMD64 Architecture Programmer’s Manual Volume 2 Describes the AMD64 architecture’s resources and functions that are managed by system software. Note sections

  • 15.34. Secure Encrypted Virtualization and
  • 15.35. Encrypted State (SEV-ES)
  • 15.36. Nested Paging
3.33 April
Guest Hypervisor Communication Block (GHCB) Standardization Standardizes the Guest-Hypervisor Communication Block (GHCB) format and specifies the required exit support and associated guest state to be provided in the GHCB to allow interoperability between hypervisors and SEV-ES guests. 2.01 July
SVSM Draft Specification Secure VM Service Module (SVSM) for SEV-SNP Guests 0. 50 August
AMD SEV-SNP Strengthening VM isolation with integrity protection and more. January
OpenStack: libvirt driver launching AMD SEV-encrypted instances Proposes work required in order for nova’s libvirt driver to support launching of KVM instances which are encrypted using AMD’s SEV (Secure Encrypted Virtualization) technology. January
Protecting VM Register State With SEV-ES Technical overview of the SEV-ES feature, the principles behind the architecture, and protections offered to further isolate encrypted VMs. February
AMD Memory Encryption Introduction to Secure Memory Encryption (SME) and Secure Encrypted Virtualization (SEV). 9 October
Versioned Chip Endorsement Key (VCEK) Certificate and KDS Interface Specification Introduction to the VCEK certificate and the KDS interface used to retrieve the certificate. 0.50 October

Links & Downloads

Link Description Setup scripts useful for running SEV guests. Site also hosts Linux open source code under development (note SEV support has been accepted in upstream projects)
Using AMD Secure Memory Encryption with Oracle Linux Oracle UEK support for SME and SEV.
SUSE: AMD Secure Encrypted Virtualization (AMD-SEV) Guide Provides a basic understanding of how SEV works, how to enable and configure it, and some of the limitations and restrictions that its use causes as compared to non-encrypted virtualization.
ask_ark_naples.cert ASK/ARK certificates for EPYC 7xx1 (Naples)
ask_ark_rome.cert ASK/ARK certificates for EPYC 7xx2 (Rome)
ask_ark_milan.cert ASK/ARK certificates for EPYC 7xx3 (Milan)
amd_sev_fam17h_model01h_0. SEV Firmware | SEV firmware 0.17.48 [hex 00.11.30] for EPYC 7xx1 (Naples) SEV Firmware | SEV firmware 0.24.15 [hex 00.18.0F] for EPYC 7xx2 (Rome) SEV Firmware | SEV firmware 1.51.03 [hex 1.33.03] for EPYC 7xx3 (Milan)
CEK certificate web page Interactive tool for obtaining CEK certificate. Also available as<GetIDValue> AMD SEV Tool for managing SEV platform certificates SEV runtime for Kata Containers

Technical Presentations

Forum Presentation Date
Linux Security Summit (2019) Upcoming x86 Technologies for Malicious Hypervisor Protection November 2019
KVM Forum (2019) Secure Encrypted Virtualization – What’s Next? November 2019
Linux Security Summit (2019) Enarx – Attested, Secured Execution with AMD’s SEV August 2019
Linux Security Summit (2018) AMD Encrypted Virtualization Update November 2018
KVM Forum (2018) Extending Secure Encrypted Virtualization with SEV-ES October 2018
Linux Security Summit (2017) Protecting VM Register State with AMD SEV-ES September 2017
Linux Security Summit (2016) AMD x86 Memory Encryption Technologies December 2016
KVM Forum (2016) AMD’s Virtualization Memory Encryption Technology September 2016
Xen Summit AMD’s Virtualization Memory Encryption Technology September 2016
Usenix Security Symposium AMD x86 Memory Encryption Technologies August 2016

Virtualization in the spirit of AMD SVM

Modern Intel Virtualization Technology and AMD Virtualization Technology use the same principle, but if the 32-bit 80386 allowed virtualization only of the 16-bit 8086 operating in real mode, then today the virtualization object can be a full-featured 64- bit processor. Virtualization technologies from Intel and AMD are quite similar, but at the level of machine code they are incompatible.

A lot has been said about off-the-shelf software products that use virtualization. The proposed article has a slightly different focus. It is intended for professionals who want to study this issue from the inside, that is, at the level of assembly code and experiment with writing their own programs using these technologies. The material is supplemented with the source texts of the simplest virtual mode monitor in assembler, capable of allowing and forbidding calls of guest procedures to given hardware resources.

AMD SVM Basic Definitions

AMD SVM technology defines two special processor states for executing two kinds of software modules. Virtual Machine Monitor (VMM) or Hypervisor has unlimited authority when accessing system resources. Coordinates the work of the entire system and creates a specified number of virtual machines to run guest programs. Guests or guest programs are restricted from accessing system resources. When a guest program tries to access a resource that the hypervisor has denied access to, the execution of the guest program is interrupted and control is transferred to the hypervisor to process this event. Such a mechanism provides emulation of a given number of virtual machines according to a scenario determined by the hypervisor. It is also important that a failure in a virtual machine does not lead to a failure of the entire system.

Hypervisor and its permissions

To enable SVM mode and gain hypervisor permissions, the program must set the SVME (SVM Enable) bit. This is bit 12 of the IA32_EFER MSR register (MSR address C0000080h). Then, after preparing the structures needed to run virtual machines in RAM, the program can start guests using the VMRUN instruction. If the guest has accessed a system resource, access to which is denied for him or the time quantum allocated for his work has expired, control is transferred to the hypervisor. This operation is called #VMEXIT.

Note that after setting the SVME bit, the program must read the IA32_EFER MSR register and check that SVME=1. This is because SVM mode may be blocked. The blocking is controlled by the SVMDIS (SVM Disable) bit. This is bit 4 of the VM_CR MSR register (MSR address C0010114h). To enable the setting of the SVME bit, the SVMDIS bit must be set to zero.

The processor allows you to set protection against unauthorized activation of the SVM mode. If the LOCK bit (bit 3 of the VM_CR MSR register) is set, the SVMDIS bit can only be reset after the password has been written to the SVM_KEY MSR register (MSR address C0010118h).

AMD SVM Resource Identification

By executing the 80000001h function of the CPUID instruction, we can get a bitmap in the EDX and ECX registers, in which each bit indicates the support of a certain technology by the processor: 0=not supported, 1=supported (CPU Extended Feature Flags). SVM technology corresponds to bit 2 of the ECX register.

If SVM is supported, function 8000000Ah of the CPUID instruction is available. It allows you to read the revision number of the SVM, a number of parameters and the presence of modes supported optionally.

Host Save Area and VMCB regions,

used in AMD SVM

AMD SVM technology defines the following two special memory areas:

Host Save Area state when returning from the guest program to the hypervisor. Presumably, the size of this block does not exceed 4KB (unfortunately, the exact value of the size is not indicated in the AMD documentation). Its 64-bit physical address is in the VM_HSAVE_PA MSR register (MSR with address C0010117h). The address must be 4KB aligned, and within the maximum physical address supported by the processor. The Host Save Area is used by the processor in hardware, and program access to this region is not recommended for two reasons: its formatting may vary depending on the processor model, its contents are cached in the processor’s internal buffers, and the contents of these buffers and the memory region are not guaranteed to be coherent. Note that Intel has a similar situation with the VMXON region.

VMCB ( Virtual Machine Control Block ) — This region is used to control the virtual machine and the guest program running on it. Its size is 4 KB, and the base physical address is specified in the EAX (for 32-bit mode) or RAX (for 64-bit mode) register when the VMRUN instruction is executed. This instruction starts the virtual machine. The base physical address requirements are the same as for the Host Save Area. Unlike the Host Save Area, and unlike Intel’s VMCS region, the formatting of the VMCB region is documented. It consists of two logical groups:

  • The Control Area is used to control the operation of the virtual machine and set lists of system resources and machine instructions that the guest cannot use. When the latter accesses these resources, its work is interrupted, and control is transferred to the hypervisor to emulate or generate an error message. It also contains status fields that are hardware-updated by the processor when the virtual machine shuts down. Based on their contents, the hypervisor can determine the reason for the termination of the guest.
  • State Save Area is used to load the state of the guest when it starts and save its state when returning to the hypervisor.

AMD SVM instructions

AMD SVM technology defines the following processor instructions.

VMRUN — This instruction is used by the hypervisor to start the guest on the virtual machine. The EAX (for 32-bit mode) or RAX (for 64-bit mode) register contains the base physical address of the VMCB that will be used by the running virtual machine. The hypervisor context is stored in the Host Save Area block. The guest context is loaded from the VMCB. The execution of the guest on the virtual machine continues until one of the events to be intercepted by the hypervisor occurs. The list of such events depends on the contents of the Control Area in the VMCB block. When the trapped event occurs, the #VMEXIT operation is executed. The execution of the guest is interrupted, its context is stored in the State Save Area in the VMCB block. The hypervisor context is loaded from the Host Save Area block. The hypervisor starts running. Based on the contents of the status fields in the VMCB block, the hypervisor can determine the reason for terminating the guest.

VMMCALL — This instruction is used by the guest to explicitly transfer control to the hypervisor. It initiates the #VMEXIT operation described above. Note that for the VMMCALL instruction to function properly, the Intercept VMMCALL Instruction bit in the VMCB block must be set to 1.

VMSAVE — Stores in the VMCB a number of additional processor context parameters for the guest program that are not automatically saved when a #VMEXIT operation is performed. The base physical address of the used VMCB is in the register EAX (for 32-bit mode) or RAX (for 64-bit mode). The list of saved parameters is as follows: registers FS, GS, TR, LDTR, model-specific registers KernelGSbase, STAR, LSTAR, CSTAR, SFMAS, SYSENTER_CS, SYSENTER_EIP, SYSENTER_ESP.

VMLOAD — Loads a number of additional processor context parameters for the guest program from the VMCB that are not automatically loaded when the VMRUN instruction is executed. The base physical address of the used VMCB is in the register EAX (for 32-bit mode) or RAX (for 64-bit mode). The list of loaded parameters is the same as in the VMSAVE instruction.

CLGI — resets the global interrupt enable flag (GIF). If GIF=0, all types of hardware interrupts (NMI, SMI, INTR) are disabled, the perception of the INIT soft reset signal, the control of the A20 line, and a number of other operations are prohibited, a complete list of which is given in [8].

Note. Anyone who has dealt with x86 assembler is familiar with the IF (Interrupt Flag) interrupt enable flag and the instructions for resetting it and setting the CLI and STI. The GIF (Global Interrupt Flag) flag and the associated CLGI and STGI instructions work on the same principle, with the only difference that when GIF=0, the perception of not only maskable interrupts, but also a number of other asynchronous events listed above is prohibited.

STGI — Sets the Global Interrupt Enable Flag (GIF). See the CLGI instruction comment.

INVLPGA — Invalidates the specified elements of the page translation buffer (TLB). The instruction takes in register EAX (for 32-bit mode) or RAX (for 64-bit mode) the linear address of the memory location. Those TLB elements that are involved in the translation of this address are cleared. The instruction also receives in the ECX register the number of the virtual address space (ASID — Address Space Identifier) ​​for which the operation is performed.

SKINIT ( Secure Init and Jump with Attestation ) — provides hardware support for protecting software modules from unauthorized modification. Uses an external Trusted Platform Module (TPM) device. The processor is initialized to execute a secure fragment (Secure Loader), the memory region containing the specified module is protected from external access, its contents are verified using TPM, then control is transferred to this program module. The instruction accepts in the EAX register the base physical address of the secured Secure Loader module, the address must be 64 KB aligned. Module size 64 KB.

Note. Not all processors that support AMD SVM support the SKINIT instruction. Before using it, you must execute the CPUID 80000001h function and check bit 12 of the ECX register (SKINIT feature).

How the program works

The program demonstrates the capabilities of AMD SVM virtualization technology. In subsequent publications, the author plans to consider a similar example for Intel VMX. For the purpose of exclusive and unhindered interaction of the debugged program with the hardware, the ancient technology of debugging under DOS is used. The rationale for such a step and recommendations for organizing the workplace are given in one of our publications.

At the same time, the acquired knowledge and skills are universal, so they will be useful when writing similar procedures for any OS. The same article describes in detail the procedure for switching the processor to 64-bit protected mode, which is also needed in this example. Recall that to use AMD SVM technology, the processor must be running in protected mode.

In this example, the hypervisor program starts the guest program. The guest outputs a byte to port 0080h and ends with a VMMCALL instruction. If the hypervisor has allowed the guest to access this port, output occurs and control returns to the hypervisor when the VMMCALL instruction is executed. If the hypervisor has denied the guest access to the port, no output occurs and control returns to the hypervisor when an OUT instruction is attempted. You can allow or deny access to the port by modifying the fragment executed at step 10 of the algorithm discussed below. Visualization of status information occurs in step 34.

Port address — 0080h was not chosen by chance. If the experimenter has a POST card, the output result of a byte can be observed on its indicators. The author used the IC80 V5.0 device manufactured by IC Book Labs, described in [17]. It supports a 16-bit data port, which expands the possibilities for experimentation. The choice of an output port with indication as an object of virtualization makes our experiments simple and visual.

Note. The simplest POST card is an 8-bit port with address 0080h. The data output to this port is displayed on the indicators. The main purpose of such a device is to display POST codes that the BIOS outputs for diagnostic purposes when the platform starts.

Program structure

Attached WORK directory contains the following files:

ASM_TD.BAT — assembles, links and runs the program under the debugger. When TASM and TLINK are launched, options are used to add debugging information to the EXE file and debug with viewing the source code of the program.

ASM_EXE.BAT — performs assembly and linking. EXE file is generated.

MAKE_SVM.ASM is the main program module. Checks the program launch conditions, prepares the context for working in protected mode with paging and calling a guest procedure using AMD SVM technology.

CODESEGS.INC — code segments for protected mode. The CODE_32 segment contains the Transit_32 procedure from which the guest procedure is called. The TARGET_32 segment contains the procedure Guest_Routine_32. The TARGET_64 segment is reserved for 64-bit guest procedures. The INTERRUPTS_16 segment is reserved for interrupt handling in protected mode.

DATASEGS.INC — data segments. DATA_16 contains variables and text strings. GLOBAL_DESCRIPTOR_TABLE — global descriptor table. PAGING_AND_VMCONTROL — dynamically created page tables and tables to support virtual mode. STACK_16 — stack segment.

A20.INC — A library of procedures for managing the A20 address line.

DOSMSG.INC — procedure for outputting text strings using the DOS service.

NUMPRINT.INC is a library of procedures for visualizing hexadecimal and decimal numbers.

Description of the program operation

Consider the execution of the main module. The numbering of the paragraphs of this description corresponds to the numbering of the comment paragraphs in the source text — the WORK\make_svm.asm file.

1) Setting the stack address, loading the SS and SP registers.

2) Issuing a message about the start of the configuration check procedure.

3) Checking the support of the 32-bit instruction set. We check the availability for writing bit 14 (NT-Nested Task) of the flag register. Such a check is needed so that when you try to run it on computers below 80386, the program will display an error message, and not hang.

4) AMD SVM technology support check. First, we check the support of the CPUID instruction, then, using the functions 80000000h (Processor vendor and largest extended function number) and 80000001h (Processor family, model, stepping and features) of the CPUID instruction, we check that the AMD processor and SVM are supported.

5) Checking the operating mode of the processor. The program uses direct access to system resources, so the processor must be running in real mode at the time of its launch.

6) Read and visualize the AMD SVM version and support for the SKINIT instruction. Functions 80000001h (Processor family, model, stepping and features) and 8000000Ah (SVM Revision and Feature Identification) of the CPUID instruction are used.

7) Enable SVM mode. To do this, first set the VM_CR .SVMDIS bit to zero, then set the IA32_EFER.SVME bit to 1. A check is made to see if the SVM is blocked. The contents of the modified registers are saved for later restoration when exiting the program.

8) Initialization of pointers for special memory areas: Load_CR3 — pointer to the root page table, used to load the CR3 control register. Load_VM_HSAVE_PA is a pointer to the Host Save Area block, in which the hypervisor context is saved when the guest program starts. The pointer is used to load the low 32-bit word of the 64-bit VM_HSAVE_PA MSR. Load_VMCB is a pointer to the Virtual Machine Control Block that is used to control the execution of the guest program and from which its context is loaded. The pointer is used to load the operand of the VMRUN instruction into the EAX register. Load_IOPM is a pointer to the Input/Output Permission Map block, which is used to control the guest program’s access to I/O ports. All pointers contain 32-bit physical addresses aligned at 4 KB according to the processor’s requirements for the location of the corresponding memory areas.

9) Preliminary cleaning of special memory areas. The page table, Host Save Area and VMCB blocks are set to zero. The Input/Output Permission Map block is filled with the constant FFh.

10) This is a commented out snippet used in debugging. Resetting the bit corresponding to port 0080h in the IOPM table. If this bit is set to zero, guest access to port 0080h is allowed. If this bit is set to 1, then when the guest tries to access port 0080h, the guest’s execution is interrupted, control is transferred to the hypervisor. Based on the contents of the status fields of the VMCB block, the hypervisor can determine the reason for the termination of the guest, the address of the intercepted port, the bitness of the intercepted operation, and other parameters.

11) Load the VM_HSAVE_PA MSR register, which specifies the address of the Host Save Area. The original value of the register is saved for restoration when the program exits. The original and loaded values ​​are visualized.

12) Issuing a message about the beginning of the context preparation procedure for the hypervisor and guest to work in protected mode.

13) Load register CR3, which defines the base physical address of the root page table.

14) Building PML4, PDP, PDE page tables. See [8] for details. Since the memory area in which the tables are built was zeroed in step 9, on here we write the values ​​of only those fields that must be non-zero.

15) Initialize register CR4. Set the bits responsible for paging options: PSE (Page Size Extension), PAE (Physical Address Extension).

16) Load the base address of the global descriptor table (GDT) into the GDTR register.

17) Building a global descriptor table that describes all segments used when working in protected mode.

18) Prepare an address for an inter-segment call to the Transit_32 subroutine located in the 32-bit CODE_32 code segment.

19) Preparation of parameters in the virtual machine control block (VMCB) that will be used to load the processor context when calling the guest procedure, including fields from which the values ​​of the CS registers are loaded, RIP addressing the entry point to the guest procedure. Since the memory area in which the VMCB is built was zeroed in step 9, on here we write the values ​​of only those fields that must be non-zero.

20) Enable address line A20. We save the initial state A20 for restoration when exiting the program.

21) Issuing a message about the beginning of the guest call procedure.

22) Saving registers SS, SP for subsequent restoration of the real mode context.

23) Disable hardware interrupts.

24) Switch to protected mode. The program is currently running in a 16-bit code segment.

25) Inter-segment jump to the next instruction to load code segment attributes.

26) Loading of data segment selectors DS and ES.

27) Loading the SS stack segment selector. The SP value is not reloaded because the same stack is used as in real mode, with the only difference that the SS register is not the base address, but the stack segment selector.

28) Inter-segment call of the Transit_32 subroutine, located in the 32-bit code segment CODE_32, located in the CODESEGS. INC file of the source text. This subroutine adjusts the values ​​of the SS and RSP registers in accordance with the rules of the 64-bit mode, turns on page translation and the IA-32e mode, which allows the execution of 32 and 64-bit code segments. A selector is loaded into the FS register to access the DATA_16 segment.

Then, using the VMRUN instruction, we start the guest procedure Guest_Routine_32, located in the TARGET_32 segment. The EAX register contains the address of the VMCB prepared in step 19.

The guest procedure context is being loaded from the VMCB. After its completion, the status fields of the VMCB block will be overwritten by the processor; their contents can be used to determine the reason for the termination of the guest and other parameters, the set of which depends on the termination reason.

As can be seen from the CODESEGS.INC file, the Guest_Routine_32 guest routine consists of outputting byte 55h to port address 0080h and a VMMCALL instruction to explicitly return to the hypervisor. If access to port 0080h is allowed, the output of the byte will take place and the procedure will end with the VMMCALL command. If access is denied, the procedure will terminate when an OUT command is attempted and no byte will be output. Next, at step 34, information about the reason for terminating the guest will be rendered. Recall that access permission on port 0080h is set in step 10.

Guest returns to the instruction after the VMRUN instruction. After that, the TARGET_32 subroutine turns off page translation and IA-32e mode. 16-bit access to the stack segment is restored.

29) Control returned from subroutine TARGET_32. We load 16-bit segment selectors into the segment registers, clear the page translation buffer and switch to real mode.

30) Real mode context recovery. We perform an inter-segment transition to the next instruction to load the attributes of the code segment. Restore the values ​​in the SS and SP registers.

31) Enable interrupts.

32) Restore the initial state of the address line A20.

33) Restore values ​​in system registers: VM_HSAVE_PA MSR, IA32_EFER MSR, VM_CR MSR.

34) Displaying a message about the return of control from the guest procedure. Visualization of status information, which can be used to determine the reason for the termination of the guest procedure: fields Exit Code, Exit Info 1 of the VMCB block. Waiting for a key press. Then we output 00h to port 0080h and exit to DOS with exit code 00h.

35) Control is transferred here if the program terminates due to errors that occurred while checking the configuration or setting the context. The BP register contains the address of the line to display the error message. We display an error message. Waiting for a key press. Then we output 01h to port 0080h and exit to DOS with exit code 01h.

Analysis of results

If in the IOPM table, the bit that allows access to port 0080h is set to 1, then the output to the port is not performed, the OUT instruction is intercepted and causes the guest to terminate. The result is visualized: Exit Code = 0000007Bh, Exit Info 1 = 00800110h.

If in the IOPM table, the bit that allows access to port 0080h is set to zero, then the output to the port is performed, the guest does not end at the OUT instruction, but reaches the VMMCALL instruction. The result is visualized: Exit Code = 00000081h, Exit Info 1 = 00000000h.

You can control the state of the specified bit of the IOPM table by editing step 10 of the above algorithm. If the experimenter has a POST card, the byte output can also be observed on its indicators.

Using the SVM Intercept Exit Codes table given in document [8], let’s decipher our results:

  • Exit Code = 0000007Bh means exit when a guest tries to access a prohibited I/O port (VMEXIT_IOIO).
  • Exit Code = 00000081h means exit when the guest executes the VMMCALL instruction (VMEXIT_VMMCALL).

Using the I/O Intercept Information table given in the document [8], let’s decode the additional parameter generated when intercepting a port call: Exit Info 1 = 00800110h.

  • Bits [31-15] = 0080h, this is the port address that was intercepted.
  • Bit[8] = 1 means 32-bit addressing.
  • Bit[4] = 1, means 8-bit data.

Information sources

Electronic documents available from

  1. Intel 64 and IA-32 Architectures Software Developer’s Manual. Volume 1: Basic Architecture. Order Number 253665-034US.
  2. Intel 64 and IA-32 Architectures Software Developer’s Manual. Volume 2A: Instruction Set Reference, A-M. Order Number 253666-034US.
  3. Intel 64 and IA-32 Architectures Software Developer’s Manual. Volume 2B: Instruction Set Reference, N-Z. Order Number 253667-034US.
  4. Intel 64 and IA-32 Architectures Software Developer’s Manual. Volume 3A: System Programming Guide, Part 1. Order Number 253668-034US.
  5. Intel 64 and IA-32 Architectures Software Developer’s Manual. Volume 3B: System Programming Guide, Part 2. Order Number 253669-034US.
  6. Intel Processor Identification and the CPUID Instruction. Application Note 485. Order Number 241618-033.

Electronic documents available from

  1. AMD64 Architecture Programmer’s Manual. Volume 1: Application Programming. Publication no. 24592.
  2. AMD64 Architecture Programmer’s Manual. Volume 2: System Programming. Publication no. 24593.
  3. AMD64 Architecture Programmer’s Manual. Volume 3: General Purpose and System Instructions. Publication no. 24594.
  4. AMD64 Architecture Programmer’s Manual. Volume 4: 128-Bit Media Instructions. Publication no. 26568.
  5. AMD64 Architecture Programmer’s Manual. Volume 5: 64-Bit Media and x87 Floating-Point Instructions. Publication no. 26569.
  6. AMD64 Architecture Programmer’s Manual. Volume 6: 128-Bit and 256-Bit XOP, FMA4 and CVT16 Instructions. Publication no. 43479.
  7. BIOS and Kernel Developer’s Guide for AMD NPT Family 0Fh Processors. Publication no. 32559.
  8. BIOS and Kernel Developer’s Guide (BKDG) for AMD Family 10h Processors. Publication no. 31116.
  9. BIOS and Kernel Developer’s Guide (BKDG) for AMD Family 10h Processors. Publication no. 41256.
  10. AMD CPUID Specification. Publication no. 25481.

Electronic documents available on the website

  1. IC80 V5.0. Diagnostic board. User’s manual. Revision 1.5. IC Book Labs, © 2006.

You can download the ZIP-archive
with an example of programming
assembler here.

AMD SVM Support — what is it in the BIOS — enable or not? (Support Vector Machine, SVM Mode)

Greetings dear ones! There are new motherboards, processors, memory .. all hardware is getting better and faster. New features are coming. The old ones remain. But today we will talk about one of the old functions that has existed for a long time .. I don’t know when AMD introduced it, but Intel introduced it back in Pentium 4 model 662/672 — there was simple VT-x virtualization.


SVM Support (Support Vector Machine) — the option allows you to enable or disable the AMd SVM (Secure Virtual Machine) technology. This technology is AMD hardware virtualization, which is necessary for some programs to work.

This technology is present in almost all modern AMD processors, Intel has its own — Intel VT.

Older processors may not support virtualization.

Another description of the option — helps to offload the processor during the use of virtual machines, most likely this description is not entirely accurate. Although in fact the effect is exactly the same — if you use virtual machines and do not enable the option — there will be really wild brakes.

How it works — in simple terms

In fact, there is nothing complicated:

  1. Virtualization allows some programs to send commands to the processor directly so that it processes them faster. Applicable only to special programs that emulate the environment — for example, Android, Windows, Linux and others.
  2. There is a regular virtualization and advanced. The first one provides direct access to the processor. The second is access to devices on the PCI bus (for example, an audio / video card).
  3. Theoretically, hardware virtualization can also be used by some conventional programs, such as Chrome or a video player. Why? You’ve probably heard somewhere — hardware acceleration. I about it. It may run faster with virtualization enabled. Such acceleration seems to be in Chrome, and may be in some video players.

Should it be included?

And here, too, everything is very simple:

  1. To answer this question, I will say differently — there is no point in turning it off. The technology does not load the PC in any way, does not change the principle of the processor, it simply includes some instructions in it and that’s it.
  2. With this option disabled, sometimes there may be problems installing some programs — they may simply tell you that virtualization technology is needed, sometimes they call it Hyper-V (although this is hypervisor-based virtualization).

Bios option:


Also known as SVM Mode:


What programs need this technology?

There are few programs and they all have a common focus — emulation of the environment (OS):

  1. VMware Workstation/Player. Allows you to create a real virtual PC with its own processor, RAM, hard drive, and so on. Requires virtualization enabled, with it disabled, there will be terrible lags. By itself, a virtual PC represents a window in another PC — Windows can be installed there, there will be a start menu, everything is as usual. But this Windows is completely isolated from the real one.
  2. VirtualBox. An analogue of the previous program, but completely free. In most cases, the functions are the same, the difference is in the interface. In my experience, VMware is faster.
  3. BlueStacks/NOX. Allows you to emulate the Android environment — you can install applications, test them, even play games. And all this on a regular Windows PC. A significant drawback is resource requirements, virtual Android will not work smartly on the PC where virtual Windows works smartly. At least 2 cores (better with high frequency and the latest generation) and 4 gigs of opera.
  4. Well, as I wrote above — perhaps virtualization will help those programs that use hardware acceleration to work faster. But this is a theory, I will not lie — I did not test it.


We found out that SVM Support:

  1. Must be switched on. Just because it doesn’t hurt in any way — nothing, absolutely. There is not a single problem in the world in which, in order to solve it, you need to disable virtualization. So feel free to turn it on — set Enabled / Enable in the BIOS.
  2. When using software that emulates a virtual PC, it must be enabled.
  3. Present on almost all modern processors, both Intel and AMD, but can be disabled by default.

I hope the information helped. Good luck.

To main!


Ctrl+C Ctrl+V — what does it mean? (control+c control+v)
Grizzly folder — what is it?
Mb3install — what folder?
PORT. IN on the music center — what is it?
Windows10UpgraderApp — what is it?
scoped_dir — what is this folder?
Windows10Upgrade — can it be uninstalled?
im_temp — what folder?


Amd svm support in bios what is