Amazon EC2 Windows Drivers
-
Published by Amazon Web Services (http://aws.amazon.com/windows)
The Amazon EC2 service utilizes paravirtualization to provide Microsoft Windows Server instances with access to the underlying physical hardware. This utility installs/upgrades to the latest paravirtualization driver for stability and performance. In conjunction with the availability of this utility, the Microsoft Windows Server AMIs have also been upgraded so that all newly created instances will contain the latest paravirtualization driver.
Please refer to the step-by-step Guide for walking through the process and for troubleshooting information, or the SNS Subscription instructions for being notified of new drivers.
What's New
- 7.4.2
- Stability fixes for support of X1 instance type
- 7.4.1
- Performance improvement in AWS PV Storage driver
- Stability fixes in AWS PV Storage driver: Fixed an issue where the instances were hitting a system crash with bugcheck code 0x0000DEAD
- Stability fixes in AWS PV Network driver
- Added support for Windows Server 2008R2
- 7.3.2
- Logging and diagnostics: Improved logging and diagnostics
- Stability fix in AWS PV Storage driver: In some cases the disks may not surface in Windows after reattaching the disk to the instance.
- Added support for Windows Server 2012
- 7.3.1
- TRIM update: Fix related to TRIM requests. This fix stabilizes instances and improves instance performance when managing large numbers of TRIM requests.
- 7.3.0
- TRIM support: The AWS PV driver now sends TRIM requests to the hypervisor. Ephemeral disks will properly process TRIM requests given the underlying storage supports TRIM (SSD). Note that EBS-based storage does not support TRIM as of March 2015.
- 7.2.5
- Stability fix in AWS PV Storage drivers: In some cases the AWS PV driver could dereference invalid memory and cause a system failure.
- Stability fix while generating a crash dump: In some cases the AWS PV driver could get stuck in a race condition when writing a crash dump. Before this release, the issue could only be resolved by forcing the driver to stop and restart which lost the memory dump.
- 7.2.4
- Device ID persistence: This driver fix masks the platform PCI device ID and forces the system to always surface the same device ID, even if the instance is moved. More generally, the fix affects how the hypervisor surfaces virtual devices. The fix also includes modifications to the co-installer for the AWS PV drivers so the system persists mapped virtual devices.
- 7.2.2
- Load the AWS PV drivers in Directory Services Restore Mode (DSRM) mode: Directory Services Restore Mode is a safe mode boot option for Windows Server domain controllers.
- Persist device ID when virtual network adapter device is reattached: This fix forces the system to check the MAC address mapping and persist the device ID. This fix ensures that adapters retain their static settings if the adapters are reattached.
- 7.2.1
- Run in safe mode: Fixed an issue where the driver would not load in safe mode. Previously the AWS PV Drivers would only instantiate in normal running systems.
- Add disks to Microsoft Windows Storage Pools: Previously we synthesized page 83 queries. The fix disabled page 83 support. Note this does not affect storage pools that are used in a cluster environment because PV disks are not valid cluster disks.
- 7.2.0
- Base: The AWS PV base version.
