Hyper-V host connectivity lost but VMs still communicate
-
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?
-
@JaredBusch oh I know, I was just thinking it may not be worth the 20 minutes to check the patches today.
-
@dafyre said in Hyper-V host connectivity lost but VMs still communicate:
Execute the powershell script to disable VMQ at system boot?
wtf, you don't beat problems over the head with a sledge.
-
@dafyre he could... but that isn't a fix to the issue, it's a bandaid.
-
@DustinB3403 said in Hyper-V host connectivity lost but VMs still communicate:
@dafyre he could... but that isn't a fix to the issue, it's a bandaid.
It works until he finds the fix.
-
@JaredBusch said in Hyper-V host connectivity lost but VMs still communicate:
@dafyre said in Hyper-V host connectivity lost but VMs still communicate:
Execute the powershell script to disable VMQ at system boot?
wtf, you don't beat problems over the head with a sledge.
Depends on the size of the problem.
-
@dafyre said in Hyper-V host connectivity lost but VMs still communicate:
@JaredBusch said in Hyper-V host connectivity lost but VMs still communicate:
@dafyre said in Hyper-V host connectivity lost but VMs still communicate:
Execute the powershell script to disable VMQ at system boot?
wtf, you don't beat problems over the head with a sledge.
Depends on the size of the problem.
Sasquatch?
-
@wirestyle22 said in Hyper-V host connectivity lost but VMs still communicate:
@dafyre said in Hyper-V host connectivity lost but VMs still communicate:
@JaredBusch said in Hyper-V host connectivity lost but VMs still communicate:
@dafyre said in Hyper-V host connectivity lost but VMs still communicate:
Execute the powershell script to disable VMQ at system boot?
wtf, you don't beat problems over the head with a sledge.
Depends on the size of the problem.
Sasquatch?
Need something bigger than a sledgehammer.
