1. Inside Microsoft’s Network and Storage VSP/VSC Brian Henry Program Manager Windows Virtualization Microsoft Corporation

2. Agenda NetworkingIntroductionArchitectureConfiguration Compatibility Requirements Wrap-upStorageRequirementsArchitecture Other topics

3. Virtualized Networking IntroductionArchitectureConfiguration 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 IntroductionArchitectureConfiguration 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 VSCVSP VMBus

10. Network VSP/VSC Parent PartitionChild Partition Child OS Parent OS Network VSC Network VSP VMBus Physical NIC Virtual Machine NIC Internal NIC Virtual Switch

11. NDIS Interaction With VSC NDIS Network VSC (NDIS Miniport Driver) Child Partition

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

13. Agenda IntroductionArchitectureConfiguration 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. Configuration Sample Standard Virtual Switch Physical NIC Child OS (1) Stack Parent OS Stack Child OS (2) Stack

16. Configuration Sample Dual physical NICs Virtual Switch Physical NIC #1 Child OS (1) Stack Parent OS Stack Child OS (2) Stack Physical NIC #2

17. Configuration Sample Child Partition Isolation Virtual Switch Physical NIC Child OS (1) Stack Parent OS Stack Child OS (2) Stack Virtual Switch Child OS (3) Stack Child OS (4) Stack

18. Configuration Sample Dedicated NIC Virtual Switch Physical NIC Child OS (1) Stack Parent OS Stack Child OS (2) Stack Virtual Switch Child OS (3) Stack Physical NIC

19. Physical NIC Configuration MAC address Virtual switch port binding

20. Virtual NIC Configuration MAC address DynamicStatic 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 that migration does not depend on state Policy must be defined above networking stack by management components

28. Agenda IntroductionArchitectureConfiguration Compatibility Requirements Wrap-up

29. NDIS driver Listen in promiscuous mode Receive packets with any destination MAC address Accept the OID_GEN_CURRENT_PACKET_FILTER with 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 IntroductionArchitectureConfiguration 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 Storage Goals Participants will leave with an understanding of How Microsoft intends to enable efficient storage device virtualization What options are available for backing storage How common enterprise scenarios work

34. Agenda (Storage) RequirementsArchitecture Device emulation Enlightened I/O Other topics Extensibility VHD utility ClusteringVSS

35. Requirements Functional goals Provide a general purpose, high- speed virtual storage infrastructure Allow format-independence between the backing store and the child partition Using an image, either ISO or VHD Using an entire physical drive Using NAS or SAN

36. Solution Requirements Performance Provide greatly improved performance for identified scenarios Minimize code path length

37. Agenda RequirementsArchitecture Device emulation Enlightened I/O Other topics Extensibility VHD utility ClusteringVSS

38. Device Emulation Components 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 Emulation Architecture I/O operations cause traps Hypervisor intercepts and redirects Emulations make requests of storage server Storage server passes requests on to a VHD parser Lots of context switching

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

41. Device Emulation When to use During boot When using unenlightened operating systems

42. Enlightened I/O Components Storage VDev Used to instantiate, configure, and control enlightened storage devices Exposes WMI interface Virtual storage server Uses SRB protocol to communicate with client Top edge interfaces with storage VDev

43. Enlightened I/O Components Image parsers Translates storage requests and responses from SRB to backing store format ParsersVHD ISO (read-only) Pass-through

44. Enlightened I/O Components Virtual storage miniport Storport miniport VMBus Inter-partition communication mechanism

45. Enlightened I/O Architecture No I/O traps Little hypervisor Involvement Enlightened requests make requests of storage server Storage server passes on requests VHD parser Directly to a LUN Much less context switching

46. Enlightened I/O Supported backing storage Direct-attached storage ATASCSIOther Network-attached storage Storage area networks

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

48. Enlightened I/O When to use Wherever possible Wherever VSCs are available

49. Agenda RequirementsArchitecture Device emulation Enlightened I/O Other topics Extensibility VHD utility ClusteringVSS

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

51. Other Topics VHD utility functions Creation Creating new disks Compaction Compacting dynamic disks Expansion Expanding dynamic disks beyond original max size Merging and forking Merging differencing disks Inserting new differencing disks

52. Other Topics Clustering and VSS Clustering “just works” Host-side or guest-side Volume Shadowing Services “just works” Child receives VSS messages from parent (for enlightened guests)

53. Call To Action Be aware of compatibility requirements Consider your value add Send us your feedback at msvirtex@microsoft.com

54. Questions?

55. © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.