HP BL680c XenServer Virtual Machine Installation 4.1.0 - Page 33

Red Hat Enterprise Linux 3, Red Hat Bugzilla

Page 33 highlights

Installing Linux VMs To prepare a Debian guest for cloning (see Section 4.6.3, "MAC address"), Ethernet name persistence must be disabled. For Debian Sarge VMs, name persistence is controlled through /etc/udev/persistent-net-generator.rules in the udev package. It can be disabled by removing the following symlink to that file by: rm -f /etc/udev/rules.d/z45_persistent-net-generator.rules 4.9.2. Red Hat Enterprise Linux 3 XenServer includes a custom port of the RHEL3.8 kernel with native Xen paravirtualized guest support. This kernel is installed during the P2V process for RHEL3.6-3.8 guests. Since the kernel is based on Linux 2.4, the following limitations apply: • Only 3 virtual network interfaces are supported. • VMs with multiple VCPUs cannot be suspended. If you wish to suspend these guests, you must reduce the number of VCPUs to 1 while the guest is halted. Before performing a P2V conversion from an existing RHEL3 installation, ensure that the /etc/fstab file in the guest contains an entry for the /boot mount point. This partition contains the files which are changed by the P2V process to give the resulting VM a para-virtual kernel. 4.9.3. Red Hat Enterprise Linux 4 XenServer includes a custom port of the RHEL 4.6 kernel with additional bug fixes and expanded Xen support. This kernel is used in the vendor installation templates of RHEL 4.1 and 4.4, but not in the RHEL 4.5 or 4.6 templates (since RHEL 4.5 is the first release with native Xen support). The issues below have been reported upstream to Red Hat and are already fixed in our kernel (which can be installed by using the /mnt/Linux/install.sh script in the built-in xs-tools.iso CD image): • During the resume operation on a suspended VM, allocations can be made that can cause swap activity which cannot be performed because the swap disk is still being reattached. (Red Hat Bugzilla 429103).) • The netfront driver in the RHEL 4.6 kernel has issues with the iptables firewall due to the use of checksum offloading. To work around this issue, disable checksum offload on the VIF associated with the device in the control domain of the XenServer Host on which your RHEL 4.6 VM runs. First determine the UUID of the VIF, by: xe vif-list vm-name-label=examplevm Then disable checksum offload on the VIF by: xe vif-param-set uuid=vif_uuid other_config:ethtool-tx=off • Only 3 virtual network interfaces are supported. • The 2.6.9-67.ELxen kernel can occasionally enter tickless mode when an RCU is pending. When this triggers, it is usually in synchronize_kernel() which means the guest essentially hangs until some external event (such as a SysRQ) releases it (Red Hat Bugzilla 427998) • Occasional kernel crash on boot in queue_work() (Red Hat Bugzilla 246586) 28

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44

Installing Linux VMs
28
To prepare a Debian guest for cloning (see Section 4.6.3, “MAC address”), Ethernet name persistence
must be disabled. For Debian Sarge VMs, name persistence is controlled through
/etc/udev/persis-
tent-net-generator.rules
in the udev package. It can be disabled by removing the following symlink
to that file by:
rm -f /etc/udev/rules.d/z45_persistent-net-generator.rules
4.9.2. Red Hat Enterprise Linux 3
XenServer includes a custom port of the RHEL3.8 kernel with native Xen paravirtualized guest support.
This kernel is installed during the P2V process for RHEL3.6-3.8 guests. Since the kernel is based on Linux
2.4, the following limitations apply:
Only 3 virtual network interfaces are supported.
VMs with multiple VCPUs cannot be suspended. If you wish to suspend these guests, you must reduce
the number of VCPUs to 1 while the guest is halted.
Before performing a P2V conversion from an existing RHEL3 installation, ensure that the
/etc/fstab
file
in the guest contains an entry for the
/boot
mount point. This partition contains the files which are changed
by the P2V process to give the resulting VM a para-virtual kernel.
4.9.3. Red Hat Enterprise Linux 4
XenServer includes a custom port of the RHEL 4.6 kernel with additional bug fixes and expanded Xen
support. This kernel is used in the vendor installation templates of RHEL 4.1 and 4.4, but not in the RHEL
4.5 or 4.6 templates (since RHEL 4.5 is the first release with native Xen support).
The issues below have been reported upstream to Red Hat and are already fixed in our kernel (which can
be installed by using the
/mnt/Linux/install.sh
script in the built-in
xs-tools.iso
CD image):
During the resume operation on a suspended VM, allocations can be made that can cause swap activity
which cannot be performed because the swap disk is still being reattached. (Red Hat Bugzilla
429103
).)
The netfront driver in the RHEL 4.6 kernel has issues with the iptables firewall due to the use of checksum
offloading. To work around this issue, disable checksum offload on the VIF associated with the device in
the control domain of the XenServer Host on which your RHEL 4.6 VM runs. First determine the UUID
of the VIF, by:
xe vif-list vm-name-label=examplevm
Then disable checksum offload on the VIF by:
xe vif-param-set uuid=vif_uuid other_config:ethtool-tx=off
Only 3 virtual network interfaces are supported.
The 2.6.9-67.ELxen kernel can occasionally enter tickless mode when an RCU is pending. When this
triggers, it is usually in synchronize_kernel() which means the guest essentially hangs until some external
event (such as a SysRQ) releases it (Red Hat Bugzilla
427998
)
Occasional kernel crash on boot in
queue_work()
(Red Hat Bugzilla
246586
)