Re: [Xen-users] Error: Boot loader didn't return any data [pygrub boot debian wheezy alpha1 netinst ISO]

[Richie <listmail@xxxxxxxxxxxx>]

On 7/2/2012 1:29 AM, Mark van Dijk wrote:
> Op Fri, 29 Jun 2012 09:24:24 +0100
> Ian Campbell<Ian.Campbell@xxxxxxxxxx>  schreef:
>
> > > $ sudo xm create -c wheezytest.cfg
> > > Using config file "./wheezytest.cfg".
> > > Error: Boot loader didn't return any data!
> > Are there any details in /var/log/xen/*?
> Derailing from the topic a little bit -- Ian, perhaps it is a good idea
> to suggest this (i.e. check the logs in /var/log/xen/) together with the
> "Boot loader didn't return any data!" message? We see that many people
> don't understand the error and think, "if the boot loader didn't return
> any data then the problem must be the boot loader!"
>
> How about a more descriptive error, for example:
>
> Error: Boot loader didn't return any data. This probably means the VM
> has crashed. Details can usually be found in /var/log/xen/.
>
> Your thoughts on this suggestion? Do share. :-)
>
> Mark

I had looked at and discarded /var/log/xen/xend.log (the only log 
written to) several times before I had realized that bootloader_args 
parameters were getting ignored completely.  Is there any level of 
syntax checking for the xm config files in that xm create could have 
complained about the use of "bootloader_args=" earlier in the process 
instead?
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users