Legacy Network Adapter issue
- Hi,
We have buy new server and installed windows2008 R2 & Hyper-v. We have import 2 VMs (windows 2008 + Linux) from old windows 2008 server to new server without any issue. But when I add legacy network adapter VM couldn't start. Error couldn't give more specifications.
I have re-installed Hyper-V role as well but no chance. Even created new VM and added new legacy network adapter but same issue.
Since we are unable to install integration service on linux we can't use synthetic adapter instead.
Anyone please help me out.
Thanks in advance.
回答
Hi Sanjay,
Sorry for the late.
For Windows Server 2008 VM, you can use synthetic network adapter as a workaround first, I will perform the further research on the issue. However, I am sorry to let you know that we don’t support Fedora Linux on Hyper-V, you may wait for other customer's experience sharing on this. Thanks for your understanding.
By the way, please try to create a new Windows Server 2008 VM to check whether you have the same issue, you can also try to create VMs with other VMs such as Windows XP to check whether they have the same issue.Vincent Hu
- 回答としてマークVincent HuMSFT, モデレータ2009年11月25日 8:22
すべての返信
Hi,
Let me have an analysis of your environment. If I misunderstand your concern, please feel free to let me know.
1. You installed Windows Server 2008 R2 on a new computer.
2. You import two VMs without any issues on the above computer.
3. When you tried to add legacy network adapter to the VMs, they can’t start.
In order to isolate the issue, please help me to collect the following information:
1. What’s the details of the error when you started the VMs?
2. Did you have any network adapter in the VM before you add the legacy network adapter?
3. Can you start the VM properly if you don’t add legacy network adapter to it?
4. Have you tried to add a synthetic network adapter? Did you encounter the same issue?
5. Please check whether you have any other errors related to Hyper-V in Event Viewer.
Vincent Hu
- <!-- /* Font Definitions */ @font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:536871559 0 0 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; mso-bidi-font-size:12.0pt; font-family:Verdana; mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times New Roman";} p.msolistparagraph, li.msolistparagraph, div.msolistparagraph {mso-style-name:msolistparagraph; mso-margin-top-alt:auto; margin-right:0in; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->
Hi,
You got my concern exactly.
1. What’s the details of the error when you started the VMs?
There isn’t any detailed error. It is just that the virtual machin name is quite unexpectedly. Event ID 14070 & 14072.
2. Did you have any network adapter in the VM before you add the legacy network adapter?
NO, even if you create new VM and assign Legacy adapter it won’t start.
3. Can you start the VM properly if you don’t add legacy network adapter to it?
Yes. If I remove legacy adapter VM starts without any error.
4. Have you tried to add a synthetic network adapter? Did you encounter the same issue?
Synthetic adapter is working fine but since we have Fedora on one VM it couldn’t work due to integration service installation problem.
5. Please check whether you have any other errors related to Hyper-V in Event Viewer.
No, I couldn’t find any other error then provided in the first point.
Thanks a Ton for your support. I really appreciate :)
- Vincent,
below is the exact error I am getting while starting VM with Legacy network adapter.
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 11/13/2009 2:13:51 AM
Event ID: 14070
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: P2070900
Description:
Virtual machine 'New Virtual Machine' (ID=B19719AC-1F43-4C4D-99F1-E24B7EDB87E7) has quit unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>14070</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2009-11-13T07:13:51.048828100Z" />
<EventRecordID>223</EventRecordID>
<Correlation />
<Execution ProcessID="2408" ThreadID="5520" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>P2070900</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
<Parameter0>New Virtual Machine</Parameter0>
<Parameter1>B19719AC-1F43-4C4D-99F1-E24B7EDB87E7</Parameter1>
</VmlEventLog>
</UserData>
</Event> - Microsoft Guys,
Is there anyone who can get out from this issue?
Thanks in advance. - Hi,
Is there any update?
Please Please Please - Vincent,
Can you please help me out from this issue. I am sure you can give me some resolutions or hint on the issue. Hi Sanjay,
Sorry for the late.
For Windows Server 2008 VM, you can use synthetic network adapter as a workaround first, I will perform the further research on the issue. However, I am sorry to let you know that we don’t support Fedora Linux on Hyper-V, you may wait for other customer's experience sharing on this. Thanks for your understanding.
By the way, please try to create a new Windows Server 2008 VM to check whether you have the same issue, you can also try to create VMs with other VMs such as Windows XP to check whether they have the same issue.Vincent Hu
- 回答としてマークVincent HuMSFT, モデレータ2009年11月25日 8:22
Vincent,
I am happy to see your positive reply.
Yes. I am using synthetic adapter with windows 2008 VM. Regarding the Legacy adapter even I have created new VM without attaching HDD, too not working. Since it is not giving details error I and probably you are quite unable to help me more.
Please let me know if there same issue occurred with other users as well as any solutions (Hint) or workaround in your mind.
Thanks a Ton dear. Really appreciate your you.
Hi,
I found a similar issue with yours, however, the cause is memory leak issues with HP QTPro service, so I’d like to confirm whether you are using HP Server.
Vincent Hu
- Hello Vincent,
Millions of thanks for your update.
I will get back to you with the H/W details. - Hi,
It is an assembled server. It is the SuperMicro Level 7.3 with the following components.
Intel Quad-Core Xeon e5420 processor
Windows 2008 Data Center Edition 64 Bit
X7DBN Motherboard motherboard Hi Sanjay,
Based on my experience, SuperMicro computer is not compatible with Hyper-V. The following post discussed the similar issue, you can refer to:
Supermicro SuperServer 7045A-WTB and Hyper-V
I guess there are some compatibility issue with your computer. By the way, if possible, please move the VMs to another computer to check whether you get the same issue. You may reinstall the system to do the same check.
Vincent Hu
