1 / 56

Inside Microsoft’s Network and Storage VSP/VSC

Inside Microsoft’s Network and Storage VSP/VSC. Brian Henry Program Manager Windows Virtualization Microsoft Corporation. Agenda. Networking Introduction Architecture Configuration Compatibility Requirements Wrap-up Storage Requirements Architecture Other topics.

billy
Download Presentation

Inside Microsoft’s Network and Storage VSP/VSC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Inside Microsoft’s Network and Storage VSP/VSC Brian HenryProgram ManagerWindows VirtualizationMicrosoft Corporation

  2. Agenda • Networking • Introduction • Architecture • Configuration • Compatibility Requirements • Wrap-up • Storage • Requirements • Architecture • Other topics

  3. Virtualized Networking • Introduction • Architecture • Configuration • Compatibility Requirements • Wrap-up

  4. Networking Goals • High performance • Avoiding copying data • Security • Strong isolation • Extensibility & Compatibility • Different topologies • Sharing a NIC • Owning a NIC • NAT • Interpartition networking • Hardware, drivers and standards

  5. Networking Solution • Emulation • Emulated DEC 21140 support will still be provided • For PXE boot • For OSes that aren’t enlightened • Enlightenment • Enlightened networking • Much better performance • Networking devices virtualization-aware

  6. Agenda • Introduction • Architecture • Configuration • Compatibility Requirements • Wrap-up

  7. Networking Components • Virtual network switch • Admin mostly interacts with this • Like physical switch, but can add/delete ports • Virtual network card • Guest-visible component • Emulated network card • Provides emulation where appropriate • Traps on I/O operations • Service stack • Provides configuration, setup/teardown • Provides WMI interface • Runs emulation code

  8. Switch Features • Flexible NIC configuration • Admin can create multiple switches • Admin decides which switch to use for internal,physical, and guest VMs’ Network Interface Cards • Learning algorithm • Anti-denial-of-service implementation • Port control • Bandwidth control • VLAN (802.1q) • Monitor mode • Offloading support • Large Send Offload • Checksum Offload

  9. Generic VSP/VSC VSP VSC VMBus

  10. Virtual Switch Network VSP/VSC Parent Partition Child Partition Parent OS Child OS NetworkVSP NetworkVSC InternalNIC Virtual MachineNIC VMBus Physical NIC

  11. NDIS Interaction With VSC Child Partition NDIS Network VSC(NDIS MiniportDriver)

  12. Virtual Switch NDIS Interaction With VSP Parent Partition NDIS Network VSP(NDIS IM Driver) Vendor-ProvidedPhysical NIC Driver(NDIS Miniport Driver) Physical NIC

  13. Agenda • Introduction • Architecture • Configuration • Compatibility Requirements • Wrap-up

  14. Switch Configuration • Per port • Monitor mode • VLAN ID • Bandwidth controls • Per switch • Switch name • Configuration is always through virtualization stack • Not SNMP, not Telnet

  15. Parent OS Stack Child OS(1) Stack Child OS(2) Stack Virtual Switch PhysicalNIC Configuration SampleStandard

  16. Virtual Switch Child OS(1) Stack Child OS(2) Stack Configuration SampleDual physical NICs Parent OS Stack PhysicalNIC #1 PhysicalNIC #2

  17. Child OS(3) Stack Child OS(4) Stack Virtual Switch Configuration SampleChild Partition Isolation Parent OS Stack Child OS(1) Stack Child OS(2) Stack Virtual Switch PhysicalNIC

  18. Parent OS Stack Child OS(1) Stack Child OS(2) Stack Virtual Switch PhysicalNIC Child OS(3) Stack Virtual Switch Configuration SampleDedicated NIC PhysicalNIC

  19. Physical NIC Configuration • MAC address • Virtual switch port binding

  20. Virtual NIC Configuration • MAC address • Dynamic • Static • Virtual switch port binding • Microsoft has new IEEE Organizationally Unique Identifier (OUI) for virtual NICs • OUI is 00-15-5D • Used when dynamically allocated • Avoids collisions with earlier virtualization efforts

  21. MAC Address Conflicts • Networking infrastructure is not responsible for MAC address conflict detection or resolution • Microsoft Windows virtualization in-box solution will prevent conflicts within scope of physical machine (best effort) • External management solutions are required to prevent conflicts outside scope of physical machine

  22. Configuration Mechanisms • UI • Basic out-of-box configuration • Built on top of WMI, no private API • WMI • Fully documented • Basis for command-line support • Basis for external management apps

  23. WMI Details For Networking • Objects exposed: Switches, ports,and NICs • Create switches, ports and NICs,bind to switches • Retrieve statistical/accounting data • Packets sent • Packets received • Packets dropped • Per port and per switch

  24. WMI Object Hierarchy - Switch

  25. WMI Object Hierarchy - VDEV

  26. WMI Object Hierarchy – Resource Allocation

  27. Config State And Migration • Config state is kept in XML,which is private to the VDev • Initial config is achieved through WMI • Config changes made through WMI • XML schema will not be published • XML is used for serialization/deserialization on store and startup • We have made the assumption thatmigration does not depend on state • Policy must be defined above networkingstack by management components

  28. Agenda • Introduction • Architecture • Configuration • Compatibility Requirements • Wrap-up

  29. Compatibility Requirements • NDIS driver • Listen in promiscuous mode • Receive packets with any destination MAC address • Accept the OID_GEN_CURRENT_PACKET_FILTERwith a value of NDIS_PACKET_TYPE_PROMISCUOUS • Flexible source MAC • Transmit packets with any source MAC address • 802.3 • Ethernet frames • Return NdisMedium802_3 when handling OID_GEN_MEDIA_SUPPORTED • Note: 802.11 is not compatible and not supported

  30. Compatibility Requirements(future) • Use PCI bus architecture to enable device assignment • Each device should have its own PCI Bus-Device-Function (BDF)

  31. Agenda • Introduction • Architecture • Configuration • Compatibility Requirements • Wrap-up

  32. Your Input Is Needed • We want your input to help prioritize our efforts for future versions of the virtual environments • Device assignment • Chimney (TOE) support • SNMP agent for switch • MAC address lists

  33. Virtualized StorageGoals • Participants will leave withan understanding of • How Microsoft intends to enableefficient storage device virtualization • What options are available forbacking storage • How common enterprise scenarios work

  34. Agenda (Storage) • Requirements • Architecture • Device emulation • Enlightened I/O • Other topics • Extensibility • VHD utility • Clustering • VSS

  35. RequirementsFunctional goals • Provide a general purpose, high-speed virtual storage infrastructure • Allow format-independencebetween the backing storeand the child partition • Using an image, either ISO or VHD • Using an entire physical drive • Using NAS or SAN

  36. Solution RequirementsPerformance • Provide greatly improved performance for identified scenarios • Minimize code path length

  37. Agenda • Requirements • Architecture • Device emulation • Enlightened I/O • Other topics • Extensibility • VHD utility • Clustering • VSS

  38. Device EmulationComponents • SCSI emulator • Emulates Adaptec 7870 SCSI controller • IDE emulator • Emulates Intel PIIX4 IDE controller • Drivers • Uses native in-box drivers for Windows® • Uses drivers common in other OSes

  39. Device EmulationArchitecture I/O operationscause traps Hypervisor intercepts and redirects Emulations make requests ofstorage server Storage serverpasses requestson to a VHD parser Lots of context switching

  40. Device EmulationBenefits • Pros • Standard set of supported legacy devices • Adequate for non-performance-intensive applications • Cons • Inadequate performance for some applications

  41. Device EmulationWhen to use • During boot • When using unenlightenedoperating systems

  42. Enlightened I/OComponents • Storage VDev • Used to instantiate, configure, andcontrol enlightened storage devices • Exposes WMI interface • Virtual storage server • Uses SRB protocol to communicatewith client • Top edge interfaces with storage VDev

  43. Enlightened I/OComponents • Image parsers • Translates storage requests and responses from SRB to backing store format • Parsers • VHD • ISO (read-only) • Pass-through

  44. Enlightened I/OComponents • Virtual storage miniport • Storport miniport • VMBus • Inter-partition communication mechanism

  45. Enlightened I/OArchitecture • No I/O traps • Little hypervisor Involvement • Enlightenedrequests makerequests ofstorage server • Storage serverpasses on requests • VHD parser • Directly to a LUN • Much less context switching

  46. Enlightened I/OSupported backing storage • Direct-attached storage • ATA • SCSI • Other • Network-attached storage • Storage area networks

  47. Enlightened I/OBenefits • Pros • Much better performance than emulation • Cons • Does not work for unenlightened guests

  48. Enlightened I/OWhen to use • Wherever possible • Wherever VSCs are available

  49. Agenda • Requirements • Architecture • Device emulation • Enlightened I/O • Other topics • Extensibility • VHD utility • Clustering • VSS

  50. Other TopicsExtensibility • Image parser not extensible in first release • Third parties are encouraged to add value for specialized markets

More Related