登入
 
首頁文件庫學習園地下載支援社群論壇
IT 專業人員的技術資源 >
> 
> 
Can not start guest OS with legacy network adapter enabled.

Întrebare Can not start guest OS with legacy network adapter enabled.

  • 2012年5月18日 上午 10:24
     
     
    登入以投票
    0

    Hi

    Start this morning, all of our guest OS(all in CentOS 5) can not be started except one that running windows 2008, the error message we get was follow:

    an error occur during starting of VM

    "name of the VM" can not be started.(VM ID XXXXXX)

    (it is a translation as I am using Chinese version of the software).

    We find out that it was the legacy network adapter cause the problem, once we remove the legacy network adapter from the VM, all of them can be started, however, once the legacy network adapter enabled, none of the VM can be started(we tried with the only windows 2008 VM as well, it can not be started after we add a legacy network adapter into it).

    There is no error message other than that, and we didn't find any similar error in the web. Please advice.

    The server has only one physical network adapter enabled, and it direct connect to the external network, the network setting was default since we installed Hyper-V. the only recent operation we did was we ran "route /f" command which was mistakenly removed gataway IP, then we re-configed it.

    some more info:

    Host OS: windows 2008 R2 datacenter 

    Guest OS: Cent OS, windows 2008 R2 enterprise.

    Role enabled: DNS, IIS, network policy and routing. Hyper-V

     

所有回覆

  • 2012年5月18日 下午 05:54
     
     
    登入以投票
    0

    Hi,

    The synthetic device is a new concept with Hyper-V. Synthetic devices are designed to work with virtualization and are optimized to work in that environment, so performance is better than with emulated devices. When you choose between Network Adapter and Legacy Network Adapter, the first is a synthetic device and the second is an emulated device. Some devices, such as the video card and pointing device, can be booted in emulated mode and then switched to synthetic mode when the drivers are loaded to increase performance. For best performance, you should use synthetic devices whenever possible.

    If the virtual machine needs to boot using a Pre-eXecution Environment (PXE) or if your operating system requires access to the network before you’re able to install the Hyper-V Integration Services. Likewise, if you need to install your virtual machine over the network, you’ll need to use the legacy network adapter. The legacy network adapter uses software to emulate a well-supported network adapter. If u not gonna install/boot VM over the network u don't need to have legacy adapter there.

     
  • 2012年5月20日 上午 06:08
     
     
    登入以投票
    0

    Hi!

    Does the problem occur both when a VM has a legacy network adapter connected to the external virtual network, as well as when a legacy network adapter is not connected?

    If the problem occurs when network adapters are configured to be connected to the ext. virtual network, you can try with set all adapters to not connected, remove the ext. virtual network, and create it again.

     
  • 2012年5月20日 上午 06:19
     
     
    登入以投票
    0

    Hi

    It happens if the adapter connected or not, as long as the legacy network adapter added to the machine, it will fail to start.

     
  • 2012年5月22日 下午 02:13
    版主
     
     
    登入以投票
    0

    Hi,

    Is there any other information in the error except the "name of the VM" can not be started.(VM ID XXXXXX)? Did you find any other error about Hyper-V in Event Viewer?

    By the way, as you are using Chinese version of Windows system, it is recommended that you perform the further research in Chinese corresponding community so that you can get the most qualified pool of response.

     

     

     
  • 2012年5月23日 上午 10:05
     
     
    登入以投票
    0

    The version of OS in VM is directly related to how it perform. The legacy device is a must of OS that unaware of virtualization. You have a luck because Microsoft provides some degree of support to Linux through integration component. Cent OS may be aware it is running in virtualization and you can you use synthetic device.

    In your case, I found information in the following link that showing the installation in step-by-step manner.

    The key point for you is step 4, the installation of Linux integration. Please give it a try and update the result. I am interested if number 4 can resolve you problem.

    http://www.hyper-v-mart.com/Howto/Install_CentOS_5_VM_Step_by_Step.aspx

    ___________________________________________________ Naruphon blog: http://www.vm360degree.com

     
  • 2012年5月23日 上午 10:10
     
     
    登入以投票
    0

    Hi, The OS is already installed and running for years. So the guide you have showed is not relevent to the problem.

    It just happened one day all the OS with legency network adapter enabled is not working.

     
  • 2012年5月23日 上午 10:18
     
     
    登入以投票
    0
    Do you consider to install integration component for moving to synthetic device?  Or, give priority to resolve current setting only?

    ___________________________________________________ Naruphon blog: http://www.vm360degree.com

     
  • 2012年5月23日 上午 10:22
     
     
    登入以投票
    0

    Hi

    We are consider to slove the current problem asap