Re: [Xen-users] WARNING:root:Unknown image directive recordfail

[Christian Mayorga <cmayorga@xxxxxxxxx>]

Hi Alexander,

Thanks a lot for your help it let me to find out the problem and it was basicly the .cfg file and exactly what you said:

"Xen has 2 ways (at least 2, relevant now) to load your DomU's kernel and
 initrd. One is using the directives "kernel" and "ramdisk". The other 
is using "bootloader = /usr/bin/pygrub". Both ways are mutually 
exclusive: they never used both, if one is used the other one is 
ommited."

 I think that "kernel" and "ramdisk" are mutually exclusive with "bootloader"

After make the change in the .cfg file the VM started without problem.

I hope this helps for other people going thru the same problem.

Cheers,
Christian

On Thu, Nov 29, 2012 at 7:39 PM, Alexandre Kouznetsov <alk@xxxxxxxxxx> wrote:

Hello, Christian.

Please consider to quote original message in a more conventional way. I almost missed yous answers.


El 29/11/12 04:52, Christian Mayorga escribió:

http://www.magicspace.eu/linux/fix-pygrub-booting-of-debian-squeeze/

I already change this one and I got the following output from pygrub:
@server02:/$ sudo /usr/bin/pygrub /dev/VolGroup00/VM01
Using <class 'grub.GrubConf.
Grub2ConfigFile'> to parse /grub/grub.cfg
WARNING:root:Unknown directive load_video

[...]

Than that is not the cause, although the symptom is similar.

http://www.virtualzone.de/2012/06/ubuntu-vm-not-starting-on-xenserver.html

in my xen installation I dont have the command referenced in the blog:

xe-edit-bootloader -n your_vm_name -p 1

xe-edit-bootloader must be some wrapper, not installed on your system.

In Dom0, mount the logical volume where your DomU's "/" resides, inspect your grub.cfg file contents. Follow the recommendation and remove or comment out any "submenu" section you find. Do a backup of grub.cfg file before that, for reference.

If you use "bootloader = /usr/bin/pygrub", it's better to comment out
"kernel" and "ramdisk" directives. The .cfg file parser will surely find
it's way, but it might be confusing to human eyes and easer to make
mistakes.

what do you mean with "The .cfg file parser will surely

find it's way"? Can you please explain?

Xen has 2 ways (at least 2, relevant now) to load your DomU's kernel and initrd. One is using the directives "kernel" and "ramdisk". The other is using "bootloader = /usr/bin/pygrub". Both ways are mutually exclusive: they never used both, if one is used the other one is ommited.

Your config file specifies both ways, which can be confusing. The Xen control system parse that config file when the DomU is started. It seems that the parser is smart enough to take into account only one way to load the kernel: if "bootloader" is specified, than "kernel" and "ramdisk" are omitted.

But, it's a good idea to comment out this unused directives. Even if they are overridden anyway, the humans who read the configs are easily confused by this kind of things, better avoid them.

Greetings.

--
Alexandre Kouznetsov


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users