Strange IP behaviour after creating VM with template
I have a Windows 2008 Hyper-V R2 cluster.
I create a VM through VMM 2008 R2 with Windows 2008 Std SP2 x64 as operating system.
NIC is a Synthetic Network Adapter
Configured this system with all available MS updates, Virtual Guest Services, IP, firewall and RDP settings. The VM behaves as expected after rebooting the server.
I have created a template from this server.
When I create a new VM from this template and I want to set IP adres, Subnet Mask, Default Gateway and DNS servers, the server is not accessible after a reboot.
IPCONFIG /ALL is showing a APIPA address, while all information is still set on the properties of the NIC.
When I do the following:
- Open command prompt on VM
- SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
- Start Devmgmt.msc
- Show hidden devices
- Uninstall all NICs
- Scan for hardware changes
- Reconfigure IP settings on newly found NIC
After reboot, the default gateway is missing.
I found a workaround the works as follows:
- Add 2nd NIC to template (also synthetic)
- Removed first NIC from template
- Created new VM from template
- Open command prompt on VM
- SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
- Start Devmgmt.msc
- Show hidden devices
- Uninstall all NICs
- reboot VM
- Reconfigure IP settings on newly found NIC
Rebooted the server several times without any IP issue anymore.
Any ideas to resolve this issue?
Answers
- Hi,
It’s suggested to initial a new post in the specialized VMM forum to solve this problem in a timely manner. They are the best resource for this kind of problem. For your reference:
System Center Virtual Machine Manager
http://social.technet.microsoft.com/Forums/en-US/category/virtualmachinemanager
Network config anomoly from template created VM
http://social.technet.microsoft.com/forums/en-US/virtualmachinemanager/thread/2214d858-e1ba-44b4-a738-17ae482f086d/
Thanks.
Mervyn
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tngfb@microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer bybertdereus Monday, November 09, 2009 11:26 AM
All Replies
- Hi,
It’s suggested to initial a new post in the specialized VMM forum to solve this problem in a timely manner. They are the best resource for this kind of problem. For your reference:
System Center Virtual Machine Manager
http://social.technet.microsoft.com/Forums/en-US/category/virtualmachinemanager
Network config anomoly from template created VM
http://social.technet.microsoft.com/forums/en-US/virtualmachinemanager/thread/2214d858-e1ba-44b4-a738-17ae482f086d/
Thanks.
Mervyn
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact tngfb@microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer bybertdereus Monday, November 09, 2009 11:26 AM
- Hi Mervyn,
Thanks for your reply.
I will try the suggestion to keep the NIC unconfigured (only DHCP) during the installation.
The only difference will be the VLAN, because I haven't got a DHCP server in the first used VLAN.
I will let you know the results.
Regards,
Bert - Hi Mervyn,
That did the trick.
I configured a new VM and placed it in VLAN with a DHCP server.
Installed all the windows updates. Shut it down and created a template from this server.
Next I create a new virtual machine from this template and placed it in VLAN (new server VLAN) without a DHCP server.
Configured IP and rebooted the server several times, without losing IP settings.
Thank you for your quick reply.
Regards,
Bert - Hi Bert,
Glad to hear you have resolved the problem. If you have more questions in the future, you’re welcomed to this forum.
Thanks.
This posting is provided "AS IS" with no warranties, and confers no rights.
