locked
LIS 3.4 on Centos Hyper-V went horribly wrong! RRS feed

  • Question

  • I recently installed LIS 3.4 on a VM in Hyper-V running Centos 6.3. This machine had been running for some time with the legacy network adapter. I only recently learned of the LIS peice to fix this. So after reading the docs, I installed it per the document provided with LIS 3.4. Thats where it went lal wrong. I lost my cdrom and my NIC. I was able to get the CDROM back, but the NIC remained lost. I learned form the output of dmesg that it had been renamed to eth6. So, I named my ifcfg script apporpriately and restarted my network services, and the machine even. The NIC appears to come up, but it cannot ping anything or be pinged. Iptables is down, my gateway is loaded in /etc/sysconfig/network-scripts-network and it appears if I run a "route" command. I have tried removing the legacy network adaptoer, adding regular NIC, and vice versa and its always the same result. I have also rebuilt my ifcfg script for DHCP instead of static and it failes to receive a dhcp address everytime. I also tried removing LIS per the doc and it fails to remove the microsoft-hyper-v-rhel63-3.4-1.20120727 saying ... error reading information on service hv_kvp_daemon: No such file or directory. I cannot foind any info on that to try and resolve. I am completely lost at this point. This is a CRITICAL server and I need to try and get it fixed. HELP!!!!
    Tuesday, November 27, 2012 1:50 PM

Answers

  • I finally got it fixed. The Virtual Network setup in Virtual Network Manager in the Hypervisor had become corrupted. I deleted it, built a new one, deleted the synthetic nic and wnet back to legacy nic. Started the VM and it came up. Granted, its slower performance, but now i can get the data out of it and move it to a VMWare box or a physical server where it belongs rather than a Microsoft product.
    • Marked as answer by gcaudle Friday, November 30, 2012 8:51 PM
    Friday, November 30, 2012 8:51 PM

All replies

  • check file /etc/udev/rules.d/70-persistent-net.rules ... you may have multiple NIC mappings there, since your MAC address changed. You can empty file wit:

    echo "" > etc/udev/rules.d/70-persistent-net.rules

    and then reboot

    Wednesday, November 28, 2012 9:53 AM
  • Beleive me, i have tried that and followed just about every step by step guide to do this and cannot get eitehr legacy or synthetic to come back up properly. I am at a total loss on this.
    Wednesday, November 28, 2012 8:17 PM
  • I finally got it fixed. The Virtual Network setup in Virtual Network Manager in the Hypervisor had become corrupted. I deleted it, built a new one, deleted the synthetic nic and wnet back to legacy nic. Started the VM and it came up. Granted, its slower performance, but now i can get the data out of it and move it to a VMWare box or a physical server where it belongs rather than a Microsoft product.
    • Marked as answer by gcaudle Friday, November 30, 2012 8:51 PM
    Friday, November 30, 2012 8:51 PM