Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
X86 virtualization
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== Network virtualization (VT-c) ==== * Intel's "Virtualization Technology for Connectivity" (VT-c).<ref>{{cite web |url=http://www.intel.com/content/dam/www/public/us/en/documents/technology-briefs/virtualization-technology-connectivity-brief.pdf |title=Intel Virtualization Technology for Connectivity (VT-c) |publisher=Intel.com |access-date=2018-02-14 |url-status=live |archive-url=https://web.archive.org/web/20160222022822/http://www.intel.com/content/dam/www/public/us/en/documents/technology-briefs/virtualization-technology-connectivity-brief.pdf |archive-date=2016-02-22}}</ref> ===== {{Anchor|PCI-SIG|SR-IOV}}PCI-SIG Single Root I/O Virtualization (SR-IOV) ===== {{Main|Single-root input/output virtualization}} ''PCI-SIG Single Root I/O Virtualization (SR-IOV)'' provides a set of general (non-x86 specific) I/O virtualization methods based on [[PCI Express]] (PCIe) native hardware, as standardized by PCI-SIG:<ref>{{cite web |url=http://www.pcisig.com/specifications/iov/ats |title=PCI-SIG I/O Virtualization (IOV) Specifications |publisher=Pcisig.com |date=2011-03-31 |access-date=2012-02-04 |url-status=dead |archive-url=https://web.archive.org/web/20120115211058/http://www.pcisig.com/specifications/iov/ats/ |archive-date=2012-01-15}}</ref> * ''Address translation services (ATS)'' supports native IOV across PCI Express via address translation. It requires support for new transactions to configure such translations. * ''[[Single-root input/output virtualization|Single-root IOV]] (SR-IOV or SRIOV)'' supports native IOV in existing single-root complex PCI Express topologies. It requires support for new device capabilities to configure multiple virtualized configuration spaces.<ref name="intel-grantley">{{cite web |url = http://www.intel.com/content/dam/technology-provider/secure/us/en/documents/product-marketing-information/tst-grantley-launch-presentation-2014.pdf#page=104 |title = Intel Look Inside: Intel Ethernet |date = November 27, 2014 |access-date = March 26, 2015 |publisher = [[Intel]] |format = PDF |page = 104 |url-status = dead |archive-url = https://web.archive.org/web/20160304003829/http://www.intel.com/content/dam/technology-provider/secure/us/en/documents/product-marketing-information/tst-grantley-launch-presentation-2014.pdf#page=104 |archive-date = March 4, 2016 }}</ref> * ''Multi-root IOV (MR-IOV)'' supports native IOV in new topologies (for example, blade servers) by building on SR-IOV to provide multiple root complexes which share a common PCI Express hierarchy. In SR-IOV, the most common of these, a host VMM configures supported devices to create and allocate virtual "shadows" of their configuration spaces so that virtual machine guests can directly configure and access such "shadow" device resources.<ref>{{cite web |url = http://www.usenix.org/conference/wiov-08/sr-iov-networking-xen-architecture-design-and-implementation |title = SR-IOV Networking in Xen: Architecture, Design and Implementation |date = 2008 |access-date = 2014-01-10 |author1 = Yaozu Dong |author2=Zhao Yu |author3=Greg Rose |publisher = [[USENIX]] |work = usenix.org |url-status = live |archive-url = https://web.archive.org/web/20140109052753/https://www.usenix.org/conference/wiov-08/sr-iov-networking-xen-architecture-design-and-implementation |archive-date = 2014-01-09 }}</ref> With SR-IOV enabled, virtualized network interfaces are directly accessible to the guests,<ref>{{cite web |url = http://www.intel.com/content/dam/www/public/us/en/documents/solution-briefs/10-gbe-ethernet-flexible-port-partitioning-brief.pdf |title = An Introduction to Intel Flexible Port Partitioning Using SR-IOV Technology |date = September 2011 |access-date = September 24, 2015 |author1 = Patrick Kutch |author2 = Brian Johnson |author3 = Greg Rose |publisher = [[Intel]] |url-status = dead |archive-url = https://web.archive.org/web/20150807015402/http://www.intel.com/content/dam/www/public/us/en/documents/solution-briefs/10-gbe-ethernet-flexible-port-partitioning-brief.pdf |archive-date = August 7, 2015 }}</ref> avoiding involvement of the VMM and resulting in high overall performance;<ref name="intel-grantley" /> for example, SR-IOV achieves over 95% of the [[Bare machine|bare metal]] network bandwidth in [[NASA]]'s virtualized datacenter<ref>{{cite web | url=http://www.intel.com/content/dam/www/public/us/en/documents/case-studies/10-gigabit-ethernet-nasa-case-study.pdf | title=NASA's Flexible Cloud Fabric: Moving Cluster Applications to the Cloud | publisher=[[Intel]] | access-date=2014-01-08 | url-status=dead | archive-url=https://web.archive.org/web/20121222083815/http://www.intel.com/content/dam/www/public/us/en/documents/case-studies/10-gigabit-ethernet-nasa-case-study.pdf | archive-date=2012-12-22}}</ref> and in the [[Amazon Web Services|Amazon Public Cloud]].<ref>{{cite web | url=http://blogs.scalablelogic.com/2013/12/enhanced-networking-in-aws-cloud.html | title=Enhanced Networking in the AWS Cloud | publisher=Scalable Logic | date=2013-12-31 | access-date=2014-01-08 | url-status=live | archive-url=http://archive.wikiwix.com/cache/20140109035046/http://blogs.scalablelogic.com/2013/12/enhanced-networking-in-aws-cloud.html | archive-date=2014-01-09}}</ref><ref>{{cite web |url=http://blogs.scalablelogic.com/2014/01/enhanced-networking-in-aws-cloud-part-2.html |title=Enhanced Networking in the AWS Cloud - Part 2 |publisher=Scalable Logic |date=2013-12-31 |access-date=2014-01-08 |url-status=live |archive-url=http://archive.wikiwix.com/cache/20140110122946/http://blogs.scalablelogic.com/2014/01/enhanced-networking-in-aws-cloud-part-2.html |archive-date=2014-01-10}}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)