Hyper-V networking status "Degraded (Integration Services upgrade required)"

Comments

Display comments as (Linear | Threaded)

Jeff A on Monday, June 10. 2013:

This means the integration services currently installed in the VM is older than the version used in the VM host server. To fix it, open up the VM's console, and in the console window's menu, select Action - Insert Integrations Services Setup Disk. This mounts the proper CD *inside the VM*. Then install the new version in the VM by going to the newly mounted disk in windows explorer there and running setup for the proper (32 vs 64 bit) version.

Comment (1)

Jari Turkia on Tuesday, June 11. 2013:

Well, no.

Thanks for the idea, but the version in the Intergrations Services -image is much older than the version in current Linux 3.9 kernels. It does not solve the issue. Maybe on Windows, but on Linux, no.

Comments (3)

Brendan Skoreyko on Wednesday, June 12. 2013:

I too have the same problem on 3 different CentOS Virtual Machines running in Hyper-V on Windows 8 Pro x64. I have a 4th CentOS VM which is using a legacy network card instead of the standard Hyper-V NIC. This 4th VM does not show the network services as degraded. I’ve tried to rebuild several variations to produce the same results but have had no luck.

I wish Microsoft had better integration for Linux Operating Systems and that Linux Distro's would recognize the need to support this. In my opinion Integration is the only missing feature of the latest Hyper-V. I have been and will remain an avid VMware user but I have to say the newest Hyper-V (Windows Server 2012/Windows 8 Pro) is amazing. Hopefully Microsoft can tweak the Integration Services which would make it harder to choose between the 2 Virtual Solutions.

Thank you for your post.

Comment (1)

Jari Turkia on Wednesday, June 12. 2013:

I'm also loving this Windows 8 Hyper-V thing a lot! It makes my software development much easier, as there is no need for extra software for getting my Linuxes to run.

That being said, I have NOT noticed any performance issues with this "degraded" network interface. It works ok by my standards. Also, Microsoft guys have been upgrading the Hyper-V virtual SCSI-disc driver for Linux (see my post about that). Apparently the new version will be included in Linux 3.10. It would be safe to guess, that they might do the same for Hyper-V virtual network driver too.

Comments (3)

Ricky on Wednesday, April 16. 2014:

Having the same issue here, running CentOS 6.5. I just upgraded to LIM 3.5 from 3.4 and it made no difference. Still have the Degraded message. However, one thing changed. The IP Addresses column next to the degraded message, now shows proper DHCP obtained IP address info, including IPv6.

Will keep troubleshooting, but I haven't noticed any issues as of yet.

Comment (1)

Jari Turkia on Thursday, April 24. 2014:

I didn't notice the IP-address info. Thanks for letting everybody know.

Comments (3)

Jules on Tuesday, February 9. 2016:

Yes, that worked on Windows 2003 network degraded issue after moving a VM from 2008R2 to 2012R2, but it causes the operating system to need to be reactivated. But it worked. Thanks,

Comment (1)

Add Comment

Name

Homepage

Comment

In reply to

E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.

Standard emoticons like :-) and ;-) are converted to images.

Remember Information?

Submitted comments will be subject to moderation before being displayed.

Mon	Tue	Wed	Thu	Fri	Sat	Sun
← Back	December '24
						1
2	3	4	5	6	7	8
9	10	11	12	13	14	15
16	17	18	19	20	21	22
23	24	25	26	27	28	29
30	31

Hyper-V networking status "Degraded (Integration Services upgrade required)"

Hacker's ramblings