On Tue, Apr 05, 2011 at 03:54:54PM +0000, Haiyang Zhang wrote: > > -----Original Message----- > > From: Greg KH [mailto:gregkh@xxxxxxx] > > Sent: Tuesday, April 05, 2011 11:42 AM > > But that's a hypervisor bug, right? It shouldn't be sending a "connect" > > event on the ethernet device if the network really isn't present. How > > about getting it fixed there, which will resolve the issues for all > > guest operating systems, not just Linux. > > > > Or, if this is something that the hyperv developers are not going to > > fix, we need to document it in the code itself so that people don't try > > to remove it in a few years as an "optimization". > > Fix on the Hyper-V side is not available for now at least. I will add the > comments into code. What happens when the hyperv code is fixed? Will this be removed? Or will all guests have this delay in them for no reason and the older "unfixed" guests suddenly work faster? That seems odd... thanks, greg k-h _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
