Installation guide

“ default=X” (where X is a number starting at '0') to correspond to the entry with your kernel-xen
line. The numbering starts at '0' so if your kernel-xen entry is the second entry you would enter '1' as
the default,for example “ default=1” .
36.7. Wrong kernel image error - non-PAE kernel on a PAE plat form
If you to boot a non-PAE kernel, para-virtualized guest the error message below will display. It
indicates you are trying to run a guest kernel on your Hypervisor which at this time is not supported.
The Xen hypervisor presently only supports PAE and 64 bit para-virtualized guest kernels.
# xm create -c va-base
Using config file "va-base".
Error: (22, 'Invalid argument')
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] ERROR (XendDomainInfo:202) Domain
construction failed
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 195, in create vm.initDomain()
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1363, in initDomain raise VmError(str(exn))
VmError: (22, 'Invalid argument')
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] DEBUG (XendDomainInfo:1449)
XendDomainInfo.destroy: domid=1
[2006-12-14 14:55:46 xend.XendDomainInfo 3874] DEBUG (XendDomainInfo:1457)
XendDomainInfo.destroyDomain(1)
If you need to run a 32 bit or non-PAE kernel you will need to run your guest as a fully-virtualized
virtual machine. The rules for hypervisor compatibility are:
para-virtualized guests must match the architecture type of your hypervisor. To run a 32 bit PAE
guest you must have a 32 bit PAE hypervisor.
to run a 64 bit para-virtualized guest your Hypervisor must be a 64 bit version too.
fully virtualized guests your hypervisor must be 32 bit or 64 bit for 32 bit guests. You can run a 32
bit (PAE and non-PAE) guest on a 32 bit or 64 bit hypervisor.
to run a 64 bit fully virtualized guest your hypervisor must be 64 bit too.
36.8. Fully-virt ualized 64 bit guest fails t o boot
If you have moved the configuration file to a Red Hat Enterprise Linux 5 causing your fully-virtualized
guest to fail to boot and present the error, Your CPU does not support long mode. Use a
32 bit distribution. This problem is caused by a missing or incorrect pae setting. Ensure you
have an entry “ pae=1” in your guest's configuration file.
36.9. A missing localhost ent ry causes virt -manager t o fail
The virt-manager application may fail to launch and display an error such as “ Unable to open
a connection to the Xen hypervisor/daemon” . This is usually caused by a missing
localhost entry in the /etc/hosts file. Verify that you indeed have a localhost entry and if it is
missing from /etc/hosts and insert a new entry for localhost if it is not present. An incorrect
/etc/hosts may resemble the following:
⁠Chapt er 36 . T roubleshoot ing
34 5