I just replaced my block and network virtio drivers in my Windows XP machine with the newest ones (the old block driver would bluescreen at boot time). The new drivers seem to work, but the network takes almost a minute to get initialized. During this time if I try to do things like right click on network and bring up properties, nothing happens at all, the window with the list of interfaces doesn't even appear for about a minute, and when it does appear, it is blank - I have to right click and refresh before the network shows up. Once this finally happens, it seems to be working normally. I can tell it to repair, and it only takes a few seconds to renew the DHCP lease, so I don't think this is a DHCP problem.
When I was using the older virtio drivers on the older libvirt, the network would come up right away without this mysterious delay, and other than updating the virtio drivers I haven't changed any settings.
Anyone have any clues to the problem, or ideas for how I can tell what is going on?
On Mon, Aug 02, 2010 at 08:39:09AM -0400, Tom Horsley wrote:
I just replaced my block and network virtio drivers in my Windows XP machine with the newest ones (the old block driver would bluescreen at boot time). The new drivers seem to work, but the network takes almost a minute to get initialized. During this time if I try to do things like right click on network and bring up properties, nothing happens at all, the window with the list of interfaces doesn't even appear for about a minute, and when it does appear, it is blank - I have to right click and refresh before the network shows up. Once this finally happens, it seems to be working normally. I can tell it to repair, and it only takes a few seconds to renew the DHCP lease, so I don't think this is a DHCP problem.
When I was using the older virtio drivers on the older libvirt, the network would come up right away without this mysterious delay, and other than updating the virtio drivers I haven't changed any settings.
Anyone have any clues to the problem, or ideas for how I can tell what is going on?
There's not much to go on here. Do the drivers log anything? eg in the Event Viewer?
Rich.
On Mon, 2 Aug 2010 20:13:48 +0100 Richard W.M. Jones wrote:
There's not much to go on here. Do the drivers log anything? eg in the Event Viewer?
I forgot about the event viewer (don't use windows that often). I'll check that when I get home. I suppose I should bring up the task manager as well and see if anything is running that stops running once the network interface appears. I've got it automatically logging me in and mounting a network share, so I suppose there could be some kind of race condition. Maybe if I turn off the share the network will come up faster. Lots of holes to poke sticks in, no clue which one might turn up something :-).
On Mon, 2 Aug 2010 15:22:26 -0400 Tom Horsley wrote:
Lots of holes to poke sticks in, no clue which one might turn up something :-).
Well, no solution, but some interesting info anyway:
I go into the device manager with the magic system environment variable
devmgr_show_nonpresent_device=1
and show hidden devices and then proceed to uninstall all traces of any redhat or realtek device drivers so I can install from scratch.
I then reboot, and it takes 90 seconds for the install new hardware wizard to appear.
Something just wants to hide the network interface for a while at boot, no idea what.
I suppose I should file a bug, but I have no idea what to file it against. Maybe qemu?
I'm tempted to change back to the emulated realtek NIC and see if it takes 90 seconds to show up as well.
On Mon, 2 Aug 2010 17:38:21 -0400 Tom Horsley wrote:
I suppose I should file a bug, but I have no idea what to file it against. Maybe qemu?
I went ahead and used qemu:
On Mon, 2 Aug 2010 17:57:14 -0400 Tom Horsley wrote:
I went ahead and used qemu:
HA! It looks like it is indeed a microsoft bug, and not a qemu problem. After sneaking up on windows updates a few at a time starting from a new XP install (which has other problems these days [1]), I finally found the ".NET Framework 4 Client Profile" was the one responsible. If I uninstall it, the network goes back to starting up as soon as I boot.
Time to tell Windows Update "never install that!" :-).
[1] other problems: https://bugzilla.redhat.com/show_bug.cgi?id=579348
On 02/08/10 22:38, Tom Horsley wrote:
On Mon, 2 Aug 2010 15:22:26 -0400 Tom Horsley wrote:
Lots of holes to poke sticks in, no clue which one might turn up something :-).
MS = turd gold throne = Fedora turd on gold throne is still a turd. :)
I have a Win7 laptop here, the last thing to come up is network activity, takes about 30-60 seconds after the desktop is on. (icon is there but not connected) Dual core, 3gb ram, 1000 nic.
Maybe it's a family trait?
-
Frank Murphy -
Richard W.M. Jones -
Tom Horsley