{"id":84,"date":"2008-05-18T06:42:00","date_gmt":"2008-05-18T06:42:00","guid":{"rendered":"http:\/\/wp.neependra.net\/?p=84"},"modified":"2008-05-18T06:42:00","modified_gmt":"2008-05-18T06:42:00","slug":"why-para-vitualization-was-needed","status":"publish","type":"post","link":"https:\/\/neependra.net\/index.php\/2008\/05\/18\/why-para-vitualization-was-needed\/","title":{"rendered":"Why Para-vitualization was needed?"},"content":{"rendered":"

Why Para-vitualization was needed?
<\/span>I had this question in my mind for some time but the answer was not clear to me. So, I read some docs and figured it out.

From http:\/\/en.wikipedia.org\/wiki\/Intel-VT
<\/span>x86 virtualization is the method by which x86-based “guest” operating systems are run under another “host” x86 operating system, with little or no modification of the guest OS. The x86 processor architecture did not originally meet the Popek and Goldberg virtualization requirements. As a result, it was very difficult to implement a general virtual machine on an x86 processor.<\/p>\n

From http:\/\/www.kernelthread.com\/publications\/virtualization\/
<\/span>One of the most popular architectures, IA-32(x86), is not virtualization friendly. The analysis in a paper titled Analysis of the Intel Pentium’s Ability to Support a Secure Virtual Machine Monitor reports at least seventeen instructions on the Pentium that make it “non-virtualizable”. IA-32’s privileged instructions cause a General Protection Exception when executed in non-privileged mode. Instructions like STR can be problematic: STR can be executed at any privilege level, but it tells you the security state of the machine (the value it retrieves has the Requestor Privilege Level, or RPL).

To overcome this guest OS was modified, so that it was aware that it is being virtualized.<\/span>
And this is called para-vitualization.<\/span>

From http:\/\/www.ibm.com\/developerworks\/linux\/library\/l-linux-kvm\/
<\/span>Older x86 processors produce different results for certain instructions depending upon the domain of execution. This creates a problem, because the hypervisor should execute in only the most protected domain. For this reason, virtualization solutions such as VMware will pre-scan code that is to execute to replace these instructions with trap instructions so that the hypervisor can handle them appropriately. Xen, supporting a cooperative method of virtualization, requires no modification, because the guest is aware that it’s being virtualized and is modified. KVM simply ignores this problem and mandates that if you want virtualization, you’ll have to run on newer hardware.<\/span>
<\/span><\/span><\/span><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Why Para-vitualization was needed?I had this question in my mind for some time but the answer was not clear to me. So, I read some docs and figured it out.From http:\/\/en.wikipedia.org\/wiki\/Intel-VTx86 virtualization is the method by which x86-based “guest” operating systems are run under another “host” x86 operating system, with little or no modification of … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[48],"tags":[],"class_list":["post-84","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t