Hyper-V host connectivity lost but VMs still communicate
-
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
This is the only thing I can find that might be the culprit.
Take a look
I found that one too, but I am not using the broadcom teaming. I am using native Hyper-V teaming.
-
Just to ask, did you see those event logs on the host at all (I know I know you're using the hyper-v teaming)
-
So this says at the VM level the intermittent connection issue, but people here have reported it affecting the host as well..
Edit: Update the drivers to the NICs
-
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
Just to ask, did you see those event logs on the host at all (I know I know you're using the hyper-v teaming)
No there are no even logs at all related to networking. In fact, the host still says it has internet access even though it cannot ping out.
Also this is Server 2012 R2 +GUI + Hyper-V Role. I forgot about this client using this. I am so used to everything I have setup being Hyper-V Server.
The Errors are all related to the Veeam 4am backup crashing.
-
There is also the recommendation to disable "Virtual Machine Queue" on both the host and the VM's to address this issue.
-
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
There is also the recommendation to disable "Enable Virtual Machine Queue" on both the host and the VM's to address this issue.
Always and forever disabled...
-
I just rebooted a CentOS 7 VM on the host and it lost network connectivity, cannot even ping the local gateway.
So it looks like networking is shitting itself, but online VMs are still working.
But it pulled a DHCP address...
-
I bet if you rebooted the host the issue goes away (at least for a short while) what version drivers are installed for these NICs?
-
@JaredBusch said in Hyper-V host connectivity lost but VMs still communicate:
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
There is also the recommendation to disable "Enable Virtual Machine Queue" on both the host and the VM's to address this issue.
Always and forever disabled...
btw, I checked again just be to sure and it is still/back on when I swear I had turned it off at the Hyper-V level as well as in the settings for each VM over a year ago.
-
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
I bet if you rebooted the host the issue goes away (at least for a short while) what version drivers are installed for these NICs?
Of course it will as that is how I fixed it 3 weeks ago.
-
@JaredBusch said in Hyper-V host connectivity lost but VMs still communicate:
@JaredBusch said in Hyper-V host connectivity lost but VMs still communicate:
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
There is also the recommendation to disable "Enable Virtual Machine Queue" on both the host and the VM's to address this issue.
Always and forever disabled...
btw, I checked again just be to sure and it is still/back on when I swear I had turned it off at the Hyper-V level as well as in the settings for each VM over a year ago.
Just checked the VMs themselves. all disabled. cannot even comprehend how this is on and those are off.
-
@JaredBusch said in Hyper-V host connectivity lost but VMs still communicate:
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
There is also the recommendation to disable "Enable Virtual Machine Queue" on both the host and the VM's to address this issue.
Always and forever disabled...
Get-NetAdapterVmq | Disable-NetAdapterVmqand everything starts running.
-
According to my ScreenConnect timeline, the Hyper-V host lost connectivity just after midnight. There is not a damned thing in the logs for the time frame.
Up yours VMQ.....
-
VQM to the rescue, am I right?
Maybe there is a bug in Hyper-V that enables it after a patch... I honestly don't know... just throwing darts...
-
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
VQM to the rescue, am I right?
Maybe there is a bug in Hyper-V that enables it after a patch... I honestly don't know... just throwing darts...
Quite possible because I patched the servers after November patch Tuesday and that first failure was the following week.
-
Well I'm glad I was able to assist, make a note to check after patch tuesday to ensure VQM is off.
-
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
Well I'm glad I was able to assist, make a note to check after patch tuesday to ensure VQM is off.
Man, I don't wanna check each of these KB manually, but I guess I need to.
-
Wouldn't it be easier to just check the host and VM's as you did previously, and saw it was enabled?
I mean, I get checking the patches... because there may be something in there that enables it again. I was thinking check monthly to ensure its still disabled after any new patches.
if its on again next month, then you could check the patches and see if something is enabling it.
-
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
Wouldn't it be easier to just check the host and VM's as you did previously, and saw it was enabled?
I mean, I get checking the patches... because there may be something in there that enables it again. I was thinking check monthly to ensure its still disabled after any new patches.
if its on again next month, then you could check the patches and see if something is enabling it.
For this, I meant to check if one of these patch was related to networking or VM config in some way.
-
Execute the powershell script to disable VMQ at system boot?
