[XEN] Windows PV drivers for Amazon EC2: behavior on 'netsh <dev> disable'

Solution Verified - Updated -

Issue

When a user of Amazon EC2 issues a 'netsh <devname> disable' inside his Windows virt on the EC2 cloud, the Windows PV driver that Amazon obtains from Redhat notifies the dom0 backend that the device is going into XenbusStateInitializing, which causes the dom0 kernel to remove the backend VIF without an 'offline' event being generated.  From the standpoint of the cloud control, the VIF simply disappears w/o any kind of notification.

We would like to know if there is some change or changes that can be made to the Windows PV network driver to behave better with regard to the backend.

Environment

  • Red Hat Enterprise Linux 5.5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.