Hyper-V VM unable to ping gateway but host can
-
Check and make sure the vSwitch is an external vSwitch.
Is this the only VM on this host?
-
@wirestyle22 said in Hyper-V VM unable to ping gateway but host can:
Morning everyone.
@JaredBusch I did specify the virtual switch
We're running Hyper-V version 6.1.7601.17514 on a Dell Poweredge 2900 on Windows Server 2008 R2. I was asked to look at it as a second pair of eyes but nothing immediately jumped out at me until I saw this:
You'll notice that I can't expand the network adapter. I think this is due to the fact that the host machine is running 2008 R2, but I haven't actually attempted to run a Hypervisor in it--every other VM host we have is 2012.
Is this correct?
Any conflicts with that mac address on the network?
-
@coliver said in Hyper-V VM unable to ping gateway but host can:
@wirestyle22 said in Hyper-V VM unable to ping gateway but host can:
Morning everyone.
@JaredBusch I did specify the virtual switch
We're running Hyper-V version 6.1.7601.17514 on a Dell Poweredge 2900 on Windows Server 2008 R2. I was asked to look at it as a second pair of eyes but nothing immediately jumped out at me until I saw this:
You'll notice that I can't expand the network adapter. I think this is due to the fact that the host machine is running 2008 R2, but I haven't actually attempted to run a Hypervisor in it--every other VM host we have is 2012.
Is this correct?
Any conflicts with that mac address on the network?
No there isn't
-
@dafyre said in Hyper-V VM unable to ping gateway but host can:
Check and make sure the vSwitch is an external vSwitch.
Is this the only VM on this host?
It's external
They are using this as a very small file server in addition to the VM but it's the only VM hosted currently.
-
@wirestyle22 said in Hyper-V VM unable to ping gateway but host can:
@dafyre said in Hyper-V VM unable to ping gateway but host can:
Check and make sure the vSwitch is an external vSwitch.
Is this the only VM on this host?
They are using this as a very small file server in addition to the VM but it's the only VM hosted currently.
Why does it have a static MAC? I know nothing of Hyper-V setups, but that seems odd unless they P2V'ed the VM.
-
@Dashrender said in Hyper-V VM unable to ping gateway but host can:
@wirestyle22 said in Hyper-V VM unable to ping gateway but host can:
@dafyre said in Hyper-V VM unable to ping gateway but host can:
Check and make sure the vSwitch is an external vSwitch.
Is this the only VM on this host?
They are using this as a very small file server in addition to the VM but it's the only VM hosted currently.
Why does it have a static MAC? I know nothing of Hyper-V setups, but that seems odd unless they P2V'ed the VM.
I had it set to dynamic before, it was just a test.
-
Have you tried removing the virtual NIC and reinstall it?
-
@Dashrender said in Hyper-V VM unable to ping gateway but host can:
Have you tried removing the virtual NIC and reinstall it?
Yes I did. I'm wondering if this has anything to do with the fact that the Dell Poweredge 2900 was one of the first generations to support Hyper-V.
-
Can you see the vSwitch in the Hyper-V setup itself?
-
@Dashrender You mean in the Virtual Network Manager?
-
This is what I see.
-
I really think that this is because the host is 2008 R2 but I don't have enough experience to definitively say that with zero doubt.
-
I'm not sure if Hyper-V 2008 R2 supports a Server 2012 VM or not. that could be the issue.
-
Yup. That is the case. https://msdn.microsoft.com/en-us/library/cc794868(v=ws.10).aspx
Thanks guys.
-
Well the good thing is - you can upgrade the hypervisor for free. shut the VM down, copy it somewhere else, wipe the host, reinstall Hyper-V 2016 server, copy the VM back, tada.
-
@Dashrender Yeah that's basically my plan. I'm glad I rad into this. My co-worker tried and I had never attempted to do this before. It's good to know.
-
My bigger question is - why was he deploying a single VM onto a 5 year old hypervisor, when upgrading/installing the latest is free?
Oh, I'd skip 2012R2 at this point as well, and go straight to Hyper-V 2016.
-
@Dashrender I'm not sure. I think it was for a timeclock so they just wanted something setup quickly. I don't even know if he's the person who did the initial install. We took over for another company and are still finding stuff.--
