<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Difference between VMX root mode and non-VMX mode (VMX OFFe in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Difference-between-VMX-root-mode-and-non-VMX-mode-VMX-OFFed/m-p/876889#M9005</link>
    <description>&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;After VMXON, the VMM is the vehicle for system schedule.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;After VMXON you operate in root mode. The VMM may use a helper guest [ XEN Dom0 for example to assist in management]&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;The VMM can Launch a Guest [ VmLaunch or VmResume ] [ on a particular processing thread ]&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;The guest will run until it does something to cause a VmExit or a timeout forces a VmExit.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;Their are about 32 of these somethings. They are designed to keep the Guest contained.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;Without Root Mode, the special "VMEXIT" controls are not active to "protect/manage" the operations of the "guest".&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;Note: VMEXIT is not a command but a response to a guest attempting to do a "protected" request.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;If the guest was not "launched" from the root, this special relationship does not exist.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 18 Jun 2008 17:54:05 GMT</pubDate>
    <dc:creator>Steven_T_Intel</dc:creator>
    <dc:date>2008-06-18T17:54:05Z</dc:date>
    <item>
      <title>Difference between VMX root mode and non-VMX mode (VMX OFFed)</title>
      <link>https://community.intel.com/t5/Software-Archive/Difference-between-VMX-root-mode-and-non-VMX-mode-VMX-OFFed/m-p/876888#M9004</link>
      <description>Is there no difference between VMX root mode and non-VMX mode (when VMX is disabled or VMXOFFed) apart from -&lt;BR /&gt;i) certain values can't be loaded into certain CRs in VMX mode, and&lt;BR /&gt;ii) these new VMX operations are available in VMX mode.&lt;BR /&gt;&lt;BR /&gt;If that is the case, the VMM has all the priviledges of the OS-kernel. So, in a scenario where the VMM installs on top of the OS-kernel (or as a module in it), the VMM can starve the other non-VM processes of the host OS&lt;BR /&gt;&lt;BR /&gt;e.g. consider this sequence of events:&lt;BR /&gt;&lt;BR /&gt;i) VMXON switches control to the VMM &lt;BR /&gt;ii) VMM launches VM1 &lt;BR /&gt;iii) VM1 VM-exits&lt;BR /&gt;iv) VMM launches VM2&lt;BR /&gt;iv) VM2 Vm-exits&lt;BR /&gt;v) VMM resumes VM1 &lt;BR /&gt;
vi) VM1 VM-exits&lt;BR /&gt;
vii) VMM resumes VM2&lt;BR /&gt;
viii) VM2 Vm-exits&lt;BR /&gt;
--- &lt;BR /&gt;this could keep on repeating, what about the other host OS applications ? What if the VMM doesn't executes VMXOFF ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Also, why the restrition on the 'values that can be loaded into the CRs' ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 06 Jun 2008 13:42:45 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Difference-between-VMX-root-mode-and-non-VMX-mode-VMX-OFFed/m-p/876888#M9004</guid>
      <dc:creator>sukanto</dc:creator>
      <dc:date>2008-06-06T13:42:45Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between VMX root mode and non-VMX mode (VMX OFFe</title>
      <link>https://community.intel.com/t5/Software-Archive/Difference-between-VMX-root-mode-and-non-VMX-mode-VMX-OFFed/m-p/876889#M9005</link>
      <description>&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;After VMXON, the VMM is the vehicle for system schedule.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;After VMXON you operate in root mode. The VMM may use a helper guest [ XEN Dom0 for example to assist in management]&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;The VMM can Launch a Guest [ VmLaunch or VmResume ] [ on a particular processing thread ]&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;The guest will run until it does something to cause a VmExit or a timeout forces a VmExit.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;Their are about 32 of these somethings. They are designed to keep the Guest contained.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;Without Root Mode, the special "VMEXIT" controls are not active to "protect/manage" the operations of the "guest".&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;Note: VMEXIT is not a command but a response to a guest attempting to do a "protected" request.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN class="891574522-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;If the guest was not "launched" from the root, this special relationship does not exist.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 18 Jun 2008 17:54:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Difference-between-VMX-root-mode-and-non-VMX-mode-VMX-OFFed/m-p/876889#M9005</guid>
      <dc:creator>Steven_T_Intel</dc:creator>
      <dc:date>2008-06-18T17:54:05Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between VMX root mode and non-VMX mode (VMX OFFe</title>
      <link>https://community.intel.com/t5/Software-Archive/Difference-between-VMX-root-mode-and-non-VMX-mode-VMX-OFFed/m-p/876890#M9006</link>
      <description>&lt;DIV align="left"&gt;&lt;SPAN class="126221423-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;In this case, the host scheduler will switch from VM1/VM2 (usually a process in host OS) to non-VM process, so no startving happens.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV align="left"&gt;&lt;SPAN class="126221423-17062008"&gt;&lt;FONT face="Arial" color="#000000" size="2"&gt;There is no need to execute VMXOFF normally except you want to quit from VMX mode, if yes, then you can never execute VM Resume/Launch instruction.&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 18 Jun 2008 17:56:46 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Difference-between-VMX-root-mode-and-non-VMX-mode-VMX-OFFed/m-p/876890#M9006</guid>
      <dc:creator>Steven_T_Intel</dc:creator>
      <dc:date>2008-06-18T17:56:46Z</dc:date>
    </item>
  </channel>
</rss>

