xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Jitendra Kanitkar <jkanitkar@apm.com>,
	xen-devel@lists.xen.org, Sanjeev Pandita <spandita@apm.com>,
	Pranavkumar Sawargaonkar <psawargaonkar@apm.com>
Subject: Re: Pygrub on ARM64
Date: Thu, 25 Feb 2016 11:12:35 +0000	[thread overview]
Message-ID: <1456398755.6225.203.camel@citrix.com> (raw)
In-Reply-To: <1456397620.6225.196.camel@citrix.com>

On Thu, 2016-02-25 at 10:53 +0000, Ian Campbell wrote:
> On Thu, 2016-02-25 at 10:47 +0000, Ian Campbell wrote:
> > 
> > > 
> > > CentOS's first partition is fat to boot on efi systems, but it only
> > > contains the grub efi binary. All the other partitions are xfs. Does
> > > pygrub support it?
> > 
> > I don't know, but pygrub is normally pretty vocal in these situations
> > if it
> > doesn't ("cannot find partition" style message), here it is apparently
> > just
> > silently hanging, which is pretty odd.
> 
> Here is what I get though:
> 
> # wget http://mirror.centos.org/altarch/7/isos/aarch64/CentOS-7-aarch64.i
> mg.xz
> # xz -d CentOS-7-aarch64.img.xz
> # pygrub CentOS-7-aarch64.img 
> Traceback (most recent call last):
>   File "/usr/local/bin/pygrub", line 926, in <module>
>     raise RuntimeError, "Unable to find partition containing kernel"
> RuntimeError: Unable to find partition containing kernel
> 
> Which is much more like what I would normally expect (and matches your
> description of the image layout  think).
> 
> That was on a random x86_64 test box because that was all I had to hand,
> but I'd be pretty surprised if something like this behaved very
> differently on arm64. 

But running on both arm32 arm64 it does indeed spin taking 100% of the CPU.

My guess would be a bug in the file system parsing code, perhaps something
to do with alignment, which results in an infinite loop. The libfsimage
backends originally came from grub (1/legacy) and is therefore only really
has history on x86.

We certainly test pygrub on arm32 regularly, and I am sure it must have
worked on arm64 when I was adding arm64 support to osstest (which is
_still_ pending h/w to go into the colo!), so the basics (i..e simple
partition tables with ext* partitions) must be ok, so I would hazzard a
stab in the dark that the issue is in one of the things specific to these
images, i.e. either the FAT or the XFS backend (if there even is an XFS
backend, I didn't check).

Ian.


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

  reply	other threads:[~2016-02-25 11:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 10:22 Pygrub on ARM64 Sanjeev Pandita
2016-02-24 10:27 ` Ian Campbell
2016-02-24 11:05   ` Sanjeev Pandita
2016-02-24 12:08     ` Ian Campbell
2016-02-25  7:50       ` Sanjeev Pandita
2016-02-25  9:39         ` Ian Campbell
2016-02-25 10:35           ` Stefano Stabellini
2016-02-25 10:47             ` Ian Campbell
2016-02-25 10:53               ` Ian Campbell
2016-02-25 11:12                 ` Ian Campbell [this message]
2016-02-25 11:22                   ` Ian Campbell
2016-02-25 11:04           ` Sanjeev Pandita

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1456398755.6225.203.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=jkanitkar@apm.com \
    --cc=psawargaonkar@apm.com \
    --cc=spandita@apm.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).