<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<font size="2">>
On 2/24/2013 9:31 AM, Lew Berry wrote:
<br />>
> I have a 5108 box [UTF-8?](2.6.32–131.17.1.el6.x86_64) running on HyperV with
<br />>
> the legacy adapter.
<br />>
>
<br />>
> It has lost connectivity to the network, [UTF-8?]won’t answer to anything.
<br />>
>
<br />>
> While in the process of booting up, it will answer about 10 or 12 pings
<br />>
> then quit.
<br />>
>
<br />>
> Any ideas?
<br />>
<br />>
Sounds like a problem with HyperV. That's the one virtualization
<br />>
platform I've absolutely sworn off of so I won't be able to help you
<br />>
with the settings there, but you might try experimenting with the
<br />>
network adapter settings on it.
<br />>
<br />>
--
<br />>
Chris Gebhardt
<br />
<br />
<br /><font size="2">My <font size="2"><font size="2">sympathies</font> Lew. </font>I'm <font size="2">also fighting a 'BlueOnyx on <font size="2">Hyper-V<font size="2">' problem. I<font size="2">n my case, the LVM container won't mount - so the system can't get into the partitions to boot. I'm still <font size="2">attempting to recover that LVM <font size="2">container.
<br />
<br />One of the things I've notices while having to manage multiple BX servers on Hyper-V - it occasionally looses the network configu<font size="2">rations/connectivity. Most of the time it hap<font size="2">pens, we<font size="2">'re able to <font size="2"><font size="2">modify the Hpyer-V settings to get the networking back up. Change it from "<font size="2">Public" to "Internal LAN"<font size="2">, <font size="2">and then back. Sometimes, we did<font size="2">n't even have to shutdown<font size="2"> the VM. Making the cha<font size="2">nges fixed it right <font size="2">away. Other times, we'd have to shutdown/modify/re<font size="2">boot to fix it. And in one case - we never got it fixed and I rebui<font size="2">lt that BX server.....</font></font></font></font></font></font>
<br />
<br /><font size="2">OH YEA! A<font size="2">nd make sur<font size="2">e your H<font size="2">yper-V VM is using a <font size="2">"Legacy Network Adapter", not the standard "Network Adapter". If you're using the sta<font size="2">ndard "Network Adapter" - you'll have all kinds of networ<font size="2">k problems<font size="2"> (including loss of network connectivity like you're having).</font></font></font></font></font></font></font></font>
<br /></font></font></font></font></font></font></font></font>
<br />
<br /><font size="2">Chuck
<br />
<br /></font>
<br />
<br />
<br />
<br /></font></font></font></font></font></font></font>
</font>
</BODY>
</HTML>