Thank you Andrew for the response. I am taking the pygrub route, and
have specified in my xen config file that "disk = [ 'phy:/dev/
hdc,xvda,w', 'phy:/dev/VolGroup00/xm_fc5_001_lv,xvda2,w' ]". The
kernel starts up fine, but when Red Hat nash starts to run, no volume
groups are found. When i mount /dev/VolGroup00/xm_fc5_001_lv and 'cd'
into the /dev/ directory, the only files that appear when I do an
'ls' are mapper and VolGroup00, both of which are directories. I
think that my problem has to do with specifying a correct value for
my 'disk' variable in the xen config file. I have included all of the
important information concerning this issue on my website. As always,
thanks for the help!
Also, if there was simply a way you could tell Anaconda to treat a
logical volume as a partition on which to install a standard FC
operating system all my problems would be solved. I just specified xm-
fc5-001_lv as my root partition and used my existing FC6 boot
partition for my /boot kernels+data.
The errors and extra info can be found at http://www.duke.edu/~jyw2/
xenerrors.html
Justin Wickett
Duke 2010
http://www.duke.edu/~jyw2
On Jan 6, 2007, at 11:32 AM, Andrew Cathrow wrote:
So looking at your xen config on your web page we see this
kernel = "/boot/vmlinuz-2.6.18-1.2257.fc5xen" #initrd = "/boot/
initrd-2.6.18-1.2257.fc5xen.img" memory = "400" name = "xm-fc5-001"
disk = [ 'phy:/dev/VolGroup00/xm_fc5_001_lv,xvda,w' ] root = "/dev/
hda2/dev/VolGroup00/xm_fc5_001_lv ro" vif = [ '' ] #vif =
[ 'mac=00:17:3f:23:67:v2, bridge=xenbr0', ] uuid = "34998936-
a8a1-4252-81cc-3109181e8111" #vnc = 1 #vncunused = 1 vcpus=4 extra
= "4" on_reboot = 'restart' on_crash = 'restart' Looking at your
disk configuration in that file disk = [ 'phy:/dev/VolGroup00/
xm_fc5_001_lv,xvda,w' ] So you're using /dev/VolGroup00/
xm_fc6_001_lv as your disk in your guest domain. and that will
appear to the guest as /dev/xvda So the root line is wrong. After
the kernel is loaded it'll look inside the guest domain for /dev/
hda2/dev/VolGroup00/xm_fc5_001_lv which doesn't exist. Typically
you'd not have the kernel, initrd and root lines in the xen config.
You'd use a bootloader. Remove those lines and add the following
bootloader="/usr/bin/pygrub" Then start the domain with xm create -
c domain-name This will give you a console with a cut down version
of grub (that reads /boot/grub/grub.conf from your guest's xvda
device. This presumes that you've got the xenU kernel installed in
the guest domain. On Sat, 2007-01-06 at 00:27 -0500, Justin Wickett
wrote:
~jyw2/xenerrors.html
-- Andrew Cathrow Red Hat, Inc. (678) 733 0452 - Mobile (404) 437
6178 - Home Office acathrow@xxxxxxxxxx
--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen
