Dexuan Cui <> changed:

           What    |Removed                     |Added
         Resolution|---                         |Works As Intended
             Status|New                         |Closed
                 CC|                            |

--- Comment #1 from Dexuan Cui <> ---
The real cause of the issue should exist in the Hyper-V host side and it's
unlikely to get this fixed in the near future considering the effort needed and
its priority, as far as I can tell.

And since we have an effective workaround (see the original description when I
reported the bug), let me close the bug -- I chose "Works As Intended" because
I couldn't find a better type like "WON'T FIX". Feel free to correct this, if
you know how to do it.

You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________ mailing list
To unsubscribe, send any mail to 

Reply via email to