networkn
asked on
Suse 11 SP3 Issues with Hyper-V 2012 (SLES)
We are having a problem where a Suse v11 SP3 guest on Hyper-V 2012 seems to be having intermittent connectivity issues.
Essentially we run a Suse VM which hosts our DataSync Product. Since Upgrading to SP3 and migrating from Vmware ESX to Hyper-V we have been having problems where occasionally network traffic to the VM is interupted every few hours for a few seconds. We aren't exactly sure how often but this is our best guess.
What is strange is that if we ping to or from the guest to or from outside the VM the issue doesn't seem to happen either at all or so infrequently as to cause no issues.
We aren't really sure how we can figure out what the issue is and fix it once and for all, we don't want to run a ping forever.
Essentially we run a Suse VM which hosts our DataSync Product. Since Upgrading to SP3 and migrating from Vmware ESX to Hyper-V we have been having problems where occasionally network traffic to the VM is interupted every few hours for a few seconds. We aren't exactly sure how often but this is our best guess.
What is strange is that if we ping to or from the guest to or from outside the VM the issue doesn't seem to happen either at all or so infrequently as to cause no issues.
We aren't really sure how we can figure out what the issue is and fix it once and for all, we don't want to run a ping forever.
Is there a backup schedules to run? Anything else running regularly (inventory of vm etc)?
You could always run a perfmon on the HyperV host monitoring network i/o to see if there is an issue.
You could always run a perfmon on the HyperV host monitoring network i/o to see if there is an issue.
ASKER
No the problem happens all day every day. We tried the legacy adapter but it basically loses connectivity after a few packets.
Auto Negotiate is set everywhere.
I don't see any settings where the vm would be paused.
Auto Negotiate is set everywhere.
I don't see any settings where the vm would be paused.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It wasn't a SUSE issue after all. We tracked down the issue after all.
I've not had much time with Hyper-V, only various flavors of VMWare (ESX, ESXi, vSphere, VMWorkstation) so I am offering places I would check.
Scott