[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] DomU in it's own LVM partition fails to boot CentOS 5.2 Dom0/U
You need a ramdisk configured. For instance to kickstart a Centos DomU I have: kernel = "/etc/xen/centos52_x86_install.vmlinuz" ramdisk = "/etc/xen/centos52_x86_install.initrd.img" extra = "ks=http://192.168.42.60/ks-xen-hit42.cfg" Where the vmlinuz and initrd files are from the images/xen directory from the Centos install media. After the installation is complete comment out the kernel, ramdisk and extra entries and add bootloader="/usr/bin/pygrub" to the config file. On Sat, 2009-01-24 at 13:19 -0500, Peter Hoose wrote: > I'm trying to do what I think would be relatively simple but can't > seem to make it work. Essentially I want to create several domU's > running CentOS each with it's own LVM partition for increased > performance over image files. > > Initially I did a test with image files and everything went fine, I > booted the supplied initrd and vmlinuz images installed CentOS from > http, etc... However, the performance of image files is pretty slow > for what I intend to use this for (Web/DB servers). So I wanted to do > the same thing but in a dedicated partition. Problem is, when I do > this and try to install via http, the disk doesn't show up in the > installer, it just shows a "#". This appears to be expected when using > a dedicated partition and the solution seems to be to copy an image to > my partition and go that route. I tried this 2 different ways: 1: > jailtime image 2: copy of my dom0 OS. For the jailtime image using the > supplied config file with my disk substituted: > > kernel = "/var/lib/xen/boot/CentOS/CentOS_5_x64_vmlinuz" > name = "guest01" > memory = "1024" > disk = [ 'phy:/dev/VolGroup00/guest01,xvda1,w', ] > vif = [ 'bridge=xenbr0', ] > vcpus=1 > root="/dev/xvda1" > extra = "fastboot" > on_reboot = 'restart' > on_crash = 'restart' > > I get the following error: > > VFS: Cannot open root device "xvda1" 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) > > When I try to copy my own OS the file copy takes forever (only 20G) > and my load average starts creeping up to 3+, which I assume may have > to do with the fact that I'm running cp -ax / /mnt/guest01 which may > loop copying /mnt/guest01 to itself or something similar? Or maybe > this is expected and I'm just impatient :) > > Anyways, long story short, is there a way to install to a partition > via HTTP like with disk images? If not, what am I doing wrong using > the prebuilt images? > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |