[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] build problems


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Justin Ferguson <jnferguson@xxxxxxxxx>
  • Date: Wed, 30 Dec 2009 02:27:56 -0700
  • Delivery-date: Wed, 30 Dec 2009 01:28:17 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=qaJDDvpPqLRse1guy923mxS70AoT0JSG12sMPd+ne8sbSzxzhRtookeKMxDsYhJMRA cImYMc7hlSY45/yEDMmj4icWr+wX7/ezkhDRxcMzYq7f8x5EXpptevLF+45EFsz6FYEp /hBM+2Grx3ZeD7mFC1IQzGzC1jtl4WMzpmD60=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> IIRC grub2 (which is what you appear to be using) strips the image name
> itself, while grub1/legacy did not. I think you need a placeholder
> command line argument to work around this, perhaps a "." , e.g.
> "multiboot /boot/xen-3.4.gz . dom0_mem" and "module /boot/vmlinuz-... .
> root=etc..."
>
> I've not used grub2 myself though and I'm not sure if this relates the
> the magic error you refer too.

grub2 is a first for me as well, and for anyone who might stumble upon
this thread with this problem-- this was the fix. It must be an issue
where the structure used doesn't match the data and the magic member
ends up pointing to the wrong spot (or something similar).

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.