Hi Steve,<br><br>Sorry to disturb you again. I was stuck on a pygrub error and I could not fix it myself.<br><br> STDERR follows.<br>Tue Feb 8 20:23:14 2011 [VMM][I]: Traceback (most recent call last):<br>Tue Feb 8 20:23:14 2011 [VMM][I]: File "/usr/bin/pygrub", line 682, in ?<br>
Tue Feb 8 20:23:14 2011 [VMM][I]: chosencfg = run_grub(file, entry, fs)<br>Tue Feb 8 20:23:14 2011 [VMM][I]: File "/usr/bin/pygrub", line 536, in run_grub<br>Tue Feb 8 20:23:14 2011 [VMM][I]: g = Grub(file, fs)<br>
Tue Feb 8 20:23:14 2011 [VMM][I]: File "/usr/bin/pygrub", line 203, in __init__<br>Tue Feb 8 20:23:14 2011 [VMM][I]: self.read_config(file, fs)<br>Tue Feb 8 20:23:14 2011 [VMM][I]: File "/usr/bin/pygrub", line 397, in read_config<br>
Tue Feb 8 20:23:14 2011 [VMM][I]: raise RuntimeError, "couldn't find bootloader config file in the image provided."<br>Tue Feb 8 20:23:14 2011 [VMM][I]: RuntimeError: couldn't find bootloader config file in the image provided.<br>
Tue Feb 8 20:23:14 2011 [VMM][I]: No handlers could be found for logger "xend"<br>Tue Feb 8 20:23:14 2011 [VMM][I]: Error: Boot loader didn't return any data!<br><br><br>My VM template:<br><br>NAME = ttylinux<br>
CPU = 0.1<br>MEMORY = 64<br>OS = [ bootloader = "/usr/bin/pygrub" ]<br><br>DISK = [ image = "tty"]<br><br>DISK = [<br> type = swap,<br> size = 5120,<br> target = sdb ]<br><br>DISK = [<br>
type = fs,<br> size = 4096,<br> format = ext3,<br> save = yes,<br> target = sdc<br> ]<br><br>NIC = [ BRIDGE = "xenbr0", MAC = "00:16:3E:02:03:05" ]<br>FEATURES=[ acpi="no" ]<br>
<br>GRAPHICS = [<br> type = "vnc",<br> listen = "127.0.0.1",<br> port = "5916" ]<br><br>CONTEXT = [<br> hostname = "$NAME",<br> ip_public = "192.168.0.16",<br>
netmask = "255.255.252.0",<br> gateway = "192.168.0.245",<br> ns = "192.168.1.9",<br> files = "/opt/cloud/one/images/init.sh",<br> #target = "hdc",<br>
root_pubkey = "id_rsa.pub",<br> root_pubkey = "id_rsa.pub",<br> username = "oneadmin",<br> user_pubkey = "id_rsa.pub"<br>]<br><br>REQUIREMENTS = "HYPERVISOR=\"xen\""<br>
<br>I had some errors with #target = "hdc", and I commented it out. Have you faced any errors like this? I could not find nothing useful from xend.log<br><br>Thanks,<br>Anoop<br><br><br><div class="gmail_quote">
On Sat, Feb 5, 2011 at 1:56 AM, anoop Lekshmanan <span dir="ltr"><<a href="mailto:anpl1980@gmail.com">anpl1980@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Steve, Thank you so much!<div><br></div><div>I was really stuck here and you saved me. </div><div><br></div><div>:)</div><div><br></div><div>Thanks,</div><div>Anoop<div><div></div><div class="h5"><br><br><div class="gmail_quote">
On Sat, Feb 5, 2011 at 1:38 AM, Steven Timm <span dir="ltr"><<a href="mailto:timm@fnal.gov" target="_blank">timm@fnal.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><br>
This is my template for running a Xen VM out of the image repository.<br>
[timm@fcl002 ~/OpenNebula]$ cat cloudlvs_xen.one<br>
NAME = <a href="http://cloudlvs.fnal.gov" target="_blank">cloudlvs.fnal.gov</a><br>
CPU = 2<br>
VCPU = 2<br>
MEMORY = 2048<br>
<br>
#OS = [<br>
# kernel = /vmlinuz,<br>
# initrd = /initrd.img,<br>
# root = sda1,<br>
# kernel_cmd = "ro xencons=tty console=tty1"]<br>
<br>
OS = [ bootloader = "/usr/bin/pygrub" ]<br>
<br>
DISK = [ image = "cloudlvs-persist-xen.img" ]<br>
<br>
DISK = [<br>
type = swap,<br>
size = 5120,<br>
target = sdb ]<br>
<br>
DISK = [<br>
type = fs,<br>
size = 4096,<br>
format = ext3,<br>
save = yes,<br>
target = sdc,<br>
bus = scsi ]<br>
<br>
#NIC = [ NETWORK = "FermiCloud" ]<br>
NIC = [ BRIDGE = "xenbr0", MAC = "00:16:3E:02:03:05" ]<br>
<br>
FEATURES=[ acpi="no" ]<br>
<br>
GRAPHICS = [<br>
type = "vnc",<br>
listen = "127.0.0.1",<br>
port = "5916" ]<br>
<br>
CONTEXT = [<br>
hostname = "$NAME",<br>
ip_public = "131.225.154.207",<br>
netmask = "255.255.254.0",<br>
gateway = "131.225.154.1",<br>
ns = "131.225.8.120",<br>
files = "/cloud/images/OpenNebula/templates/init.sh /home/timm/OpenNebula/k5login",<br>
target = "hdc",<br>
root_pubkey = "id_dsa.pub",<br>
username = "opennebula",<br>
user_pubkey = "id_dsa.pub"<br>
]<br>
<br>
REQUIREMENTS = "HYPERVISOR=\"xen\""<br>
<br>
--------------<br>
<br>
and here is the declaration of my image in the image repo.<br>
<br>
[timm@fcl002 ~/OpenNebula]$ oneimage show 56<br>
IMAGE INFORMATION<br>
ID : 56<br>
NAME : cloudlvs-persist-xen.img<br>
TYPE : OS<br>
REGISTER TIME : 02/03 17:02:52<br>
PUBLIC : No<br>
PERSISTENT : Yes<br>
SOURCE : /var/lib/one/image-repo/d75ce946cc408f9db71bdf14ba6eecd5d20750a5<br>
STATE : used<br>
RUNNING_VMS : 1<br>
<br>
IMAGE TEMPLATE<br>
BUS=scsi<br>
DESCRIPTION=cloudlvs xen<br>
DEV_PREFIX=sd<br>
NAME=cloudlvs-persist-xen.img<br>
PATH=/cloud/images/OpenNebula/images/cloudlvs-persist-xen.img<br>
TYPE=OS<br>
<br>
<br>
For Xen you are best to try to mount / as sda and that's what<br>
this os template will do.<br>
<br>
Steve<div><div></div><div><br>
<br>
<br>
<br>
On Fri, 4 Feb 2011, Steven Timm wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
The error you are getting is probably due to a malformed ramdisk<br>
for your Xen kernel. Likely what is happening is that the ramdisk<br>
is trying to load the real scsi device as sda1 rather than the xenblk<br>
block device. Try to replace the ramdisk and see if you do any better.<br>
I had this same error a while ago and building a ramdisk on a xen<br>
VM that was installed statically is what it took for me to make it work.<br>
<br>
Also, just so you know, when you say KERNEL = /boot/vmlinuz....<br>
etc, then the kernel and ramdisk have to be in that location<br>
on your VM host, not inside the LVM you are trying to boot.<br>
If you want to use the kernel/ramdisk inside the xen virtual machine<br>
then you should use pygrub, which is what I use.<br>
<br>
Steve<br>
<br>
<br>
On Sat, 5 Feb 2011, anoop Lekshmanan wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I get this error on loading ttylinux or any other image in to Xen Node and<br>
LVM, I have tried native kernel as well, but that did not work.<br>
<br>
device-mapper: uevent: version 1.0.3<br>
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:<br>
<a href="mailto:dm-devel@redhat.com" target="_blank">dm-devel@redhat.com</a><br>
device-mapper: dm-raid45: initialized v0.2594l<br>
Kernel panic - not syncing: Attempted to kill init!<br>
<br>
My VM template:<br>
<br>
NAME = test<br>
CPU = 1<br>
MEMORY = 256<br>
OS = [<br>
KERNEL = /boot/vmlinuz-2.6.18-194.32.1.el5xen,<br>
INITRD = /boot/initrd-2.6.18-194.32.1.el5xen.img,<br>
ROOT = /dev/vg00/lv-one--0<br>
#BOOTLOADER = /usr/bin/pygrub,<br>
#KERNEL_CMD = "ro"<br>
]<br>
<br>
DISK = [<br>
IMAGE = "ttylin",<br>
#source = "/dev/vg00/xenvm01",<br>
target = "hdb",<br>
readonly = "no" ]<br>
<br>
NIC = [ NETWORK = "Small network" ]<br>
<br>
FEATURES=[ acpi="no" ]<br>
<br>
GRAPHICS=[<br>
AUTOPORT=yes,<br>
KEYMAP=en-us,<br>
LISTEN=127.0.0.1,<br>
PORT=5901,<br>
TYPE=vnc ]<br>
<br>
#CONTEXT = [<br>
# hostname = "$NAME",<br>
# ip_public = "192.168.0.16",<br>
# files = "/opt/cloud/one/images/init.sh<br>
/opt/cloud/one/.ssh/id_rsa.pub",<br>
# target = "hdc",<br>
# root_pubkey = "id_rsa.pub",<br>
# username = "oneadmin",<br>
# user_pubkey = "id_rsa.pub"<br>
<br>
VM deployment file generated:<br>
<br>
name = 'one-65'<br>
#O CPU_CREDITS = 256<br>
memory = '256'<br>
kernel = '/boot/vmlinuz-2.6.18-194.32.1.el5xen'<br>
ramdisk = '/boot/initrd-2.6.18-194.32.1.el5xen.img'<br>
root = '/dev//dev/vg00/lv-one--0'<br>
disk = [<br>
'tap:aio:/opt/cloud/one/var//65/images/disk.0,hdb,w',<br>
]<br>
vif = [<br>
' mac=02:00:c0:a8:1e:06,ip=192.168.30.6,bridge=xenbr0',<br>
]<br>
vfb = ['type=vnc,vnclisten=127.0.0.1,vncdisplay=1,keymap=en-us']<br>
<br>
<br>
<br>
I am trying to load this in to LVM and ONE creates the LV successfully and<br>
VM state ins "RUNN"<br>
<br>
Any help would be appreciated.<br>
<br>
Thanks,<br>
Anoop<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
-- <br>
------------------------------------------------------------------<br>
Steven C. Timm, Ph.D (630) 840-8525<br>
<a href="mailto:timm@fnal.gov" target="_blank">timm@fnal.gov</a> <a href="http://home.fnal.gov/%7Etimm/" target="_blank">http://home.fnal.gov/~timm/</a><br>
Fermilab Computing Division, Scientific Computing Facilities,<br>
Grid Facilities Department, FermiGrid Services Group, Group Leader.<br>
Lead of FermiCloud project.<br>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br>