Site Alert(s):
- We are currently experiencing issues with the display of certain articles. We are working to resolve this as soon as possible. We apologize for the inconvenience.
Archive:
XenServer 5.5 Update 1 Upgrade Causes Virtual Machines to Lose Network Connectivity
- CTX123691
- Created On Dec 21, 2009
- Updated On Dec 22, 2010
- 18 found this helpful
- Article
- Topic : Networking
This article is no longer maintained, its content refers to a discontinued product and may be out of date. Refer to the
Discontinued Product Lifecycle
or Active Citrix Product pages for more
information on support schedules.
Summary
This document explains how a Windows virtual machine (VM) can lose its network connectivity, after an upgrade of XenTools with Update 1 for XenServer 5.5. Windows Vista and Windows Server 2008 VMs that have all of the following characteristics will be affected:
• XenTools installations that were upgraded from XenServer 5.5 to XenServer 5.5 Update 1.
• Interfaces enabled for both IPv4 and IPv6.
• A static IPv4 address configured.
Note: IPAddress and SubnetMask are multi-string values and should have corresponding entries. Make sure there are no entries relating to IPv6 addresses or masks (IPv6 masks are actually prefix lengths) and make sure that each IPv4 address has a corresponding mask.
This screen capture displays the IPv6 setting:
Requirements
Basic knowledge of XenServer and Windows
Procedures
Below are 2 Scenarios with steps to resolve the issue before you have installed XenServer 5.5 Update 1 XenTools and after you have installed XenServer 5.5 Update 1 XenTools:
Scenario 1
This scenario explains the steps required if you have not installed the XenServer 5.5 Update 1 XenTools on a Windows Vista or Windows 2008 VM that currently has XenServer 5.5 XenTools installed.
1. Install XenTools but do not reboot the VM.
2. Use the registry editor and locate the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\xennet\nics" key.
3. Each key under nics will have an associated MAC address for each VIF.
4. Locate the "IPAddress" value and double click to edit.
5. The value contains two lines, one the IPv4 address of the interface and one an IPv6 address.
6. Delete the IPv6 address on the second line and leave the IPv4 address.
7. Under SubnetMask key, delete the corresponding subnet value for IPv6.
8. Reboot the VM.
9. VM Networking, VIFs, and XenTools drivers should work as expected.
Scenario 2
This scenario explains the steps required if you have already installed the XenServer 5.5 Update 1 XenTools on a Windows Vista or Windows 2008 VM and are currently experiencing the issue.
1. Install the XenTools and reboot the VM.
2. Use the registry editor and locate the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces" key.
3. Look at settings under each GUID to find the corresponding IPAddress and SubnetMask values.
4. Edit both the "IPAddress” and “SubnetMask" value.
5. The value contains two lines, one the IPv4 address of the interface and one an IPv6 address.
6. Delete the IPv6 address on the second line and leave the IPv4 address.
7. Under SubnetMask key delete the corresponding subnet value for IPv6
8. Reboot the VM.
9. VM Networking, VIFs, and XenTools drivers should work as expected.
Note: IPAddress and SubnetMask should have single entries. After removing the IPv6 address from IPAddress delete the corresponding subnet mask value for IPv6 from SubnetMask.
More Information
Upgrades to Windows 7 and Windows 2008 R2 VMs are not supported. Support for Windows 7 and Windows 2008 R2 was provided with the release of XenServer 5.5 Update 1.
