The installer will create the disk image and partition it. If you do
not successfully run to the installer, "xm create -c xxxx" will not
work. The script gives bad instructions when an error occurs.
The Xen hypervisor takes 32MB of RAM (I think), so you have to make
sure that your dom0 gets less than 224MB. I gave mine 192MB, with
the following in grub.conf:
kernel /xen.gz-2.6.15-1.2054_FC5 dom0_mem=196608
In my opinion, the xenguest-install.py method isn't very good at this
point.
- The installer gives poor feedback when something goes wrong, like
when memory is too low.
- pygrub crashes if your terminal emulation is a little weird
- It creates a whole disk image instead of importing partitions.
This makes it difficult to access domU filesystems from dom0, but
this is often necessary for management.
- It doesn't provide an option for creating images on LVM volumes.
An easier solution might be to use the FC5 image from
jailtime.org.
If you use the images from their site, keep in mind that you have to
use a kernel from outside of the image; the kernel would have to be
readable from your dom0.
If you use the stock FC5-xenU kernel, it does not have the xennet
driver compiled in. You would have to install the kernel-xenU
package onto the domU disk image to provide the necessary driver
(assuming the disk image is mounted at /mnt/tmp):
yum --installroot=/mnt/tmp install kernel-xenU
And add the following to the domU's /etc/modprobe.conf:
alias eth0 xennet
Or you could use a kernel from xensource that has the xennet driver
compiled into the kernel. I don't know why the developers decided to
take the driver out of the kernel. Pretty much everyone would want
networking on their domU machines, and adding it in this way is just
more complicated.
Thank you for suggestive advise.
but, I have been still working on the issue.
I tried to use a ready made image from
jailtime.org,
but still it does not work.
Why os.path.isfile(self.kernel) fails?
--- Okajima, Jun. Tokyo, Japan.
-------------
[root@localhost okajima]# xm create -c fedora.fc5.xen.cfg
Using config file "fedora.fc5.xen.cfg".
Warning: The nics option is deprecated. Please use an empty vif entry instead:
vif = [ '' ]
Error: Error creating domain: Kernel image does not exist:
/boot/vmlinuz-2.6.16-1.2080_FC5xenU
[root@localhost okajima]# ls -la /boot/vmlinuz-2.6.16-1.2080_FC5xenU
-rw-r--r-- 1 root root 1232494 Mar 28 18:38 /boot/vmlinuz-2.6.16-1.2080_FC5xenU
[root@localhost okajima]# md5sum /boot/vmlinuz-2.6.16-1.2080_FC5xenU
242c2a1cfeb924481ba57e983cbe801e /boot/vmlinuz-2.6.16-1.2080_FC5xenU
[root@localhost okajima]# ls -l /usr/lib/xen/boot/
total 160
-rwxr-xr-x 1 root root 153797 Mar 9 14:20 hvmloader
[root@localhost okajima]# md5sum /usr/lib/xen/boot/hvmloader
2bbd4cf936aa8bde3ab6b6fe31362ff0 /usr/lib/xen/boot/hvmloader
[root@localhost okajima]# cat fedora.fc5.xen.cfg
kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xenU"
#kernel = "/boot/vmlinuz-2.6-xenU"
memory = 128
name = "fedora.fc5"
nics = 1
dhcp = "dhcp"
disk = ['file:/home/okajima/fedora.fc5.img,sda1,w',
'file:/home/okajima/fedora.swap,sda2,w']
root = "/dev/sda1 ro"
[root@localhost okajima]# grep -3 -ir "Kernel image does not exist"
/usr/lib/python2.4/site-packages/
*
Binary file /usr/lib/python2.4/site-packages/xen/xend/image.pyo matches
--
/usr/lib/python2.4/site-packages/xen/xend/image.py- # Set params and call
buildDomain().
/usr/lib/python2.4/site-packages/xen/xend/image.py-
/usr/lib/python2.4/site-packages/xen/xend/image.py- if not
os.path.isfile(self.kernel):
/usr/lib/python2.4/site-packages/xen/xend/image.py: raise VmError('Kernel
image does not
exist: %s' % self.kernel)
/usr/lib/python2.4/site-packages/xen/xend/image.py- if self.ramdisk and not
os.path.isfile
(self.ramdisk):
/usr/lib/python2.4/site-packages/xen/xend/image.py- raise VmError('Kernel
ramdisk does not
exist: %s' % self.ramdisk)
/usr/lib/python2.4/site-packages/xen/xend/image.py- if len(self.cmdline) >=
MAX_GUEST_CMDLINE:
Binary file /usr/lib/python2.4/site-packages/xen/xend/image.pyc matches
[root@localhost okajima]#