Microsoft Hyper-V network support in Fedora

["Jóhann B. Guðmundsson"]

Greetings

I've been digging a bit into running Fedora as a an guest in the most 
common virtulzation solution out there most notably running as a guest 
in hyperv/kvm/vbox/vmware/xen, which was spurred by a discussion in the 
QA community and crawling through the internet I found 1 bug [1] that 
affects all of them and one issue limit to hyper-v as in networking not 
working out of the box [2].

Digging to the root cause of this leads me to this when users use the 
legacy tulip network driver as is mentioned there in that blog post

"The real problem here is that the device does not support carrier 
detection via ethtool or mii-tool. If the driver supported carrier 
detection, NetworkManager would bring it up automatically."
( With an obvious workaround if that's the case simply disable NM 
configure and use initscripts network service instead )

The mentioned issue has been reported upstream here [3]

So my question are these.

1. What's the current status on an fix for that tulip kernel driver bug?
2. What ever happened to the native hyper-v drivers that Microsoft 
pushed upstream?
3. If those drivers have not been rejected and simply are stuck in 
staging? is there something preventing us pulling into Fedora and 
enabling them by default to improve the situation?

JBG

1.https://bugzilla.redhat.com/show_bug.cgi?id=810040
2.http://blog.robertseder.com/2012/08/29/win8hyper-v-what-works-and-what-doesnt-edition/
3. https://bugzilla.kernel.org/show_bug.cgi?id=11092