Xen

Clock issues

Usually Xen will try to sync the clocks of Dom0 and the DOMUs, however this might not work as expected. In order to make a DomU maintain the clock on its own, one has to set /proc/sys/xen/independent_wallclock to 1.

Upgrading Xen server from Ubuntu 7.10 to 8.04

See http://sebastian.marsching.com/blog/archives/89-Making-Xen-work-on-Ubuntu-8.04-Hardy-Heron.html

Upgrading Xen DomU from Ubuntu 8.04 (hardy) to 10.04 (lucid)

Using a special IP setup with Xen

See http://wiki.hetzner.de/index.php/9_IP_Adressen_mit_Ubuntu (German only)

Bad network perfomance in Xen DomU

If you are using a routed networking setup with Xen, you might encounter a bad network performance for the Xen DomU: The solution is to disable tx checksums for the virtual ethernet device: They are not needed as their are no physical errors on a virtual interface that only connects to another virtual interface in the Dom0. To disable tx checksums the following line can be added to /etc/network/interfaces

post-up  ethtool -K eth0 tx off

This line has to be added within the definition of the corresponding interface and eth0 has to be replaced by the name of this interface.

Please note that this solution will not work with Ubuntu, if /usr is in the DomU is stored on its own partition: You will have to deactivate the ifup and ifdown hooks in /etc/udev/rules.d/85-ifupdown.rules because ethtool lies in /usr/sbin and /usr is not yet mounted when this hooks are executed. Deactivating this hooks probably won't hurt as the interfaces will be brought up by /etc/init.d/networking and you are unlikely to use a hotplugged interface within a Xen DomU. In newer Ubuntu releases (e.g. 10.04 - lucid lynx) this is not so easy, as the the network interfaces are managed by upstart. Therefore you have to copy ethtool to the root partion and use the corresponding path in the post-up script.


CategoryEnglish CategoryLinux

Linux/Xen (last edited 2017-03-16 16:25:34 by SebastianMarsching)