Windows 7 SP1
Tuesday 15th March, 2011 11:22 Comments: 0
There seems to be a small number of people having issues with this service pack. It's been fine on every host I've upgraded, including over half a dozen Windows 7 and three Windows 2008 R2 boxes. The only slight issue I experienced was the Hyper-V server took a long time to reboot. I jumped onto the KVM over IP device and was able to see the server was shutting down, but seemed to be hanging on:
Shutting down Hyper-V Virtual Machine Management service
After waiting about 20 minutes, I decided to walk into the lab, unlock the rack, take off the faceplate and look at the hard disk activity. There was none. This surprised me as I figured, even though the VMs had been paused or stopped, it might be trying to write a lot of data to disk. I suspect it was doing some intense CPU calculations, but there are no flashing lights on the box to show that, and I can't imagine it'd take that long for this one service. At least the spinning icon kept spinning, so I knew the server was okay as I sat back at my desk with the KVM window open.
After resisting the urge to go back in the lab and hold down the power button for several seconds, it eventually rebooted and moved onto the next set of stages. It probably took an hour from clicking "Restart" to being able to log in again. More painful than I expected, but at least I didn't hit the 0xC0000034 error that some people are seeing.
Shutting down Hyper-V Virtual Machine Management service
After waiting about 20 minutes, I decided to walk into the lab, unlock the rack, take off the faceplate and look at the hard disk activity. There was none. This surprised me as I figured, even though the VMs had been paused or stopped, it might be trying to write a lot of data to disk. I suspect it was doing some intense CPU calculations, but there are no flashing lights on the box to show that, and I can't imagine it'd take that long for this one service. At least the spinning icon kept spinning, so I knew the server was okay as I sat back at my desk with the KVM window open.
After resisting the urge to go back in the lab and hold down the power button for several seconds, it eventually rebooted and moved onto the next set of stages. It probably took an hour from clicking "Restart" to being able to log in again. More painful than I expected, but at least I didn't hit the 0xC0000034 error that some people are seeing.