Fedora xen - May 2006 - Fedora 5 xen dom0 , trying to boot ubuntu 5.10 domU

I''m starting to go nuts I have tried this several ways and
can''t get my
domainU to boot up, I am using Fedora 5 as dom0 and trying to boot up ubuntu
5.10.  I installed ubuntu to a seperate harddrive then mounted the harddrive
and did a cp -ax to a new file for my domU filesystem edited the fstab. My
fedora dom0 is using lvm and I am not in the ubuntu installation, here are
my output of my domain file and error......, any help would be appreciated.
My goasl is to load mutiple distros to play with which I think will be
neat.  THANKS.

Domain::::
#  -*- mode: python; -*-
#============================= =============================================#
Python configuration setup for ''xm create''.
# This script sets the parameters used when a domain is created using
''xm
create''.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#===========================================================================

#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.16-1.2096_FC5xen0"

# Optional ramdisk.
#ramdisk = "/boot/initrd- 2.6.15-1.2054_FC5.img"

# The domain build function. Default is ''linux''.
#builder=''linux''

# Initial memory allocation (in megabytes) for the new domain.
memory = 128

# A name for your domain. All domains must have different names.
name = "Ubuntu1"

# List of which CPUS this domain is allowed to use, default Xen picks
#cpus = ""         # leave to Xen to pick
#cpus = "0"        # all vcpus run on CPU0
#cpus = "0-3,5,^1" # run on cpus 0,2,3,5

# Number of Virtual CPUS to use, default is 1
#vcpus = 1

#----------------------------------------------------------------------------
# Define network interfaces.

# By default, no network interfaces are configured.  You may have one
created
# with sensible defaults using an empty vif clause:
#
# vif = [ '''' ]
#
# or optionally override backend, bridge, ip, mac, script, type, or vifname:

#
vif = [ ''mac=00:16:3e:00:00:11, bridge=xenbr0'' ]
#
# or more than one interface may be configured:
#
# vif = [ '''', ''bridge=xenbr1'' ]

#vif = [ '''' ]

#----------------------------------------------------------------------------

# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.

disk = [''file:/xen-home/ubuntu/ubuntu.img,sda1,w'',
''file:/xen-home/ubuntu/swap.img,sda5,w'']

#----------------------------------------------------------------------------

# Define to which TPM instance the user domain should communicate.
# The vtpm entry is of the form
''instance=INSTANCE,backend=DOM''
# where INSTANCE indicates the instance number of the TPM the VM
# should be talking to and DOM provides the domain where the backend
# is located.
# Note that no two virtual machines should try to connect to the same
# TPM instance. The handling of all TPM instances does require
# some management effort in so far that VM configration files (and thus
# a VM) should be associated with a TPM instance throughout the lifetime
# of the VM / VM configuration file. The instance number must be
# greater or equal to 1.
#vtpm = [ ''instance=1,backend=0'' ]

#----------------------------------------------------------------------------

# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the
domain''s
# IP config doesn''t, e.g. in ifcfg-eth0 or via DHCP.
# You can use ''extra'' to set the runlevel and custom
environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).

# Set if you want dhcp to allocate the IP address.
dhcp="dhcp"
# Set netmask.
#netmask# Set default gateway.
#gateway# Set the hostname.
#hostname= "vm%d" % vmid

# Set root device.
root = ''/dev/sda1 ro''

# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = '' 169.254.1.0 ''
# Root directory on the nfs server.
#nfs_root   = ''/full/path/to/root/directory''

# Sets runlevel 4.
extra = "4"

#----------------------------------------------------------------------------

# Configure the behaviour when a domain exits.  There are three
''reasons''
# for a domain to stop: poweroff, reboot, and crash.  For each of these you
# may specify:
#
#   "destroy",        meaning that the domain is cleaned up as normal;
#   "restart",        meaning that a new domain is started in place of
the
old
#                     one;
#   "preserve",       meaning that no clean-up is done until the
domain is
#                     manually destroyed (using xm destroy, for example); or

#   "rename-restart", meaning that the old domain is not cleaned up,
but is
#                     renamed and a new domain started in its place.
#
# The default is
#
#   on_poweroff = ''destroy''
#   on_reboot   = ''restart''
#   on_crash    = ''restart''
#
# For backwards compatibility we also support the deprecated option restart
#
# restart = ''onreboot'' means on_poweroff =
''destroy''
#                            on_reboot   = ''restart''
#                            on_crash    = ''destroy''
#
# restart = ''always''   means on_poweroff =
''restart''
#                            on_reboot   = ''restart''
#                            on_crash    = ''restart''
#
# restart = ''never''    means on_poweroff =
''destroy''
#                            on_reboot   = ''destroy''
#                            on_crash    = ''destroy''

#on_poweroff = ''destroy''
#on_reboot   = ''restart''
#on_crash    = ''restart''

#===========================================================================
error::::
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
 [<c011c50c>] panic+0x3c/0x190
 [<c03c6a5c>] mount_block_root+0x19c/0x1aa
 [<c03c6ab3>] mount_root+0x49/0x4e
 [<c03c6b78>] prepare_namespace+0xc0/0xf1
 [<c0102267>] init+0x23e/0x2fe
 [<c0102029>] init+0x0/0x2fe
 [<c01029ad>] kernel_thread_helper+0x5/0xb

On Tue, 2 May 2006 11:46:39 -0500 Tom wrote:
TB> VFS: Cannot open root device "sda1" or unknown-block(0,0)
TB> Please append a correct "root=" boot option
TB> Kernel panic - not syncing: VFS: Unable to mount root fs on
TB> unknown-block(0,0)

This error is caused by this line:

TB> kernel = "/boot/vmlinuz-2.6.16-1.2096_FC5xen0"

You need a xenU kernel, not a xen0 kernel.