XenServer Release Notes

Release 4.1.0

This release of the XenServer product family contains the following new features:

This section details known issues with this beta release, and any workarounds which can be applied. Please report any other issues via your Citrix support representative.

CA-933: On machines with multiple disks, the XenServer boot loader is only written to the disk selected for installation.

For example, if you set the boot drive to the first disk, and then install XenServer Host on the second drive, and then subsequently change the system BIOS to assign the second drive to be the boot drive, it will fail to boot and properly renumber the disks. Installation to the second disk only works if the first disk has a boot loader already present which lets you boot off second disk, or if the BIOS permits you to boot directly off the second disk. Renumbering disks post-installation will not work. The only workaround is to manually edit menu.lst .

CA-4575, CA-5311: On servers with the ICH8 South Bridge chipset, XenServer might not detect the drive at installation due to a problem with the ata_piix driver. If you have this problem, set the machine's ATA/IDE mode in the Advanced section of the BIOS to use the Advanced Host Controller Interface (AHCI). This is usually set to off (legacy mode) by default. You might need to set the mode to "Native" to then access further SATA configuration options that allow selecting between AHCI, IDE, or RAID. It might also be available via Advanced->Drive Configuration->Disable Intel® RAID Technology and then Enable SATA AHCI mode. The Dell SAS 5/iR Controller in Dell 490 hosts exhibits this issue.

For more information, see http://www.intel.com/support/chipsets/imst/sb/cs-015988.htm.

CA-8767: Motherboards using the Intel 965 chipset with more than 2GB of memory may fail to boot successfully. This has been identified as a BIOS firmware issue, and appears to happen on any 64-bit operating systems (see Red Hat and Microsoft related bugs). To workaround this, downgrade your BIOS to version 1669, available from the Intel website.

CA-15337: When doing an upgrade or restoring from an upgrade, users should ensure that removable storage not in use by the XenServer installation is removed, in particular USB flash and hard drives. In particular, remote management tools like HP iLO or Dell RDAC may also cause a virtual USB device to appear in the host, so be sure to disable this functionality before upgrading your server.

CA-5785: The Acronis Rescue CD does not work in a VM. It uses CPU features that Xen does not yet support. A future release of Acronis will support Xen; please contact the vendor for details.

CA-6966: When using NFS ISO storage repositories, a hard mount is used to communicate with the server. This means that the control domain can hang if the remote NFS server becomes unreachable. The workaround is to use CIFS-based mounts instead.

CA-9208:  Citrix has seen data corruption issues using the iSCSI target provided by Adaptec SnapServers. This appears to be a problem with the SnapServer iSCSI implementation, and has been reproduced by Adaptec using a standard (non-XenServer) Linux distribution. We are currently working with Adaptec to find a solution to this problem. Until this issue is resolved, XenServer users are strongly encouraged to use NFS rather than iSCSI storage repositories when using SnapServer products. In general, when using network-based storage hardware, users should ensure the software and/or firmware on the devices being used is up to date, as recommended by the manufacturer.

CA-9772. The Windows PV drivers do not send a gratuitous ARP after live relocation if the guest has previously been hibernated. Note that hibernation is not a supported use-case, since direct suspension of a VM is supported instead.

CA-12866: Users should avoid attaching read-only VDIs to Windows VMs as this may result in unexpected behaviour and instability of the virtual machine. This includes NetApp snapshot VDIs; users wishing to attach a snapshot VDI to a Windows VM should first make a read-write copy of the snapshot using the vdi-copy CLI command

CA-13972: For XenServer 4.0, users were able to edit networking configuration files directly, and use the service network restart command to reconfigure networking on a host. This should not be done in XenServer 4.1 as the XenAPI has been extended to cover remote networking configuration. Please refer to the Administrator's Guide for details on how to setup networking using the CLI.

CA-14197: When upgrading a pool or server, users should not leave VMs suspended across the upgrade. Importantly, any suspended virtual machine with a CD drive attached (with the Tools ISO or a local physical drive, for example) will not be resumable after upgrade. To get the virtual machine back into a usable state, one would have to perform a "Force Shutdown" of the suspended VM.

This section describes some of the more detailed changes from v4.0.1 to v4.1.0, categorized by the broad area in which the change was made.