TechNet - Только для профессионалов. Специально для Вас. >
Форумы
>
Virtual Machine Manager – Hyper-V
>
Hyper-V on 2008 w/ SP2 running on HP ML 370 G6, Synthetic network devices do not pass traffic.
Hyper-V on 2008 w/ SP2 running on HP ML 370 G6, Synthetic network devices do not pass traffic.
- I recently began configuring an HP Proliant ML 370 G6 (features a quad-port NC375i NIC). I installed 2008 Enterprise (with SP2 integrated, media from eOpen). I added the Hyper-V role, I setup a new Guest running 2008 Standard (with SP2 integrated from the same media). The Integration Services appeared to be baked in with SP2 as everything detected. The host OS works fine... moves traffic just fine. Any guest I run, while getting a DHCP address, doesn't pass any additional traffic--ICMP, NS, etc.). If I add a legacy NIC to the guest on any of the ports--everything is fine. I also installed a 2008 standard (no SP2) load and added the Intergration Services--same results.
I know that SP2 is new, I know that the G6 line is new--I'm thinking somethings not playing well together! Problem is this thing is supposed to go live very soon!
Ответы
- Tested with a USB-NIC, traffic passes just fine. I'm thinking it something with this nc375 quad-port NIC. As an aside, I installed wireshark on the vmguest and found that traffic is passing... it's just not making it ALL the way up the stack somehow. For instance, I run nslookup and do a query... while nslooup reports back that the request timed-out, wireshark shows that my DNS server received the request and responded with the appopriate response.Microsoft officially supports this hardware for Virtualization.HP officially supports the use of Hyper-V on this product.Let the finger-point begin!I have a support ticket open with Microsoft Professional Support, and while I've called HP already I think I'm going to call back to escalate the case.
- Помечено в качестве ответаCarmen SummersВладелец4 августа 2009 г. 2:15
Все ответы
- Tested with a USB-NIC, traffic passes just fine. I'm thinking it something with this nc375 quad-port NIC. As an aside, I installed wireshark on the vmguest and found that traffic is passing... it's just not making it ALL the way up the stack somehow. For instance, I run nslookup and do a query... while nslooup reports back that the request timed-out, wireshark shows that my DNS server received the request and responded with the appopriate response.Microsoft officially supports this hardware for Virtualization.HP officially supports the use of Hyper-V on this product.Let the finger-point begin!I have a support ticket open with Microsoft Professional Support, and while I've called HP already I think I'm going to call back to escalate the case.
- Помечено в качестве ответаCarmen SummersВладелец4 августа 2009 г. 2:15
- WOW... so, after A LOT of wasted time.It's an HP issue, that is to say--while the first HP tech put me on hold for 15 minutes while he "researched the issue", and then said "it's an issue you'll need to take up with Microsoft", the second tech I spoke to this morning had some clue regarding Virtualization and was able to determine that "this is an issue that we have been working on for some time but we have a work-around"--which is...On any NIC used with a Virtual Machine you'll need to disable "IPv4 Checksum Offload", which can be done in the adapter properties on the host machine.Hope this helps anyone else that has this issue!
- While disabling "IPv4 Checksum Offload" allowed ICMP traffic to pass, I found I also had to disable:TCP Checksum Offload IPv4UCP Checksum Offload IPv4TCP Checksum Offload IPv6UCP Checksum Offload IPv6
- I generally disable offloading on every physical NIC on Hyper-V host systems. It's definately not just limited to HP systems. Hyper-V R2 has limited support for TCP Offloading.
http://www.microsoft.com/windowsserver2008/en/us/hyperv-r2.aspx
Nathan Lasnoski- Предложено в качестве ответаCurt Huff 15 октября 2009 г. 21:59
