From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chaitanya Deshpande Subject: Re: Query for running Xen on ARM Date: Wed, 30 May 2018 10:21:58 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1461336723690859892==" Return-path: Received: from us1-rack-dfw2.inumbo.com ([104.130.134.6]) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1fO4nw-00034O-5b for xen-devel@lists.xenproject.org; Wed, 30 May 2018 17:22:32 +0000 Received: by mail-ot0-x232.google.com with SMTP id l12-v6so22045155oth.6 for ; Wed, 30 May 2018 10:22:00 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" To: Julien Grall Cc: xen-devel@lists.xenproject.org, Stefano Stabellini List-Id: xen-devel@lists.xenproject.org --===============1461336723690859892== Content-Type: multipart/alternative; boundary="000000000000a1b017056d6f96ce" --000000000000a1b017056d6f96ce Content-Type: text/plain; charset="UTF-8" On Wed, May 30, 2018 at 9:44 AM, Julien Grall wrote: > Hi, > > On 05/30/2018 05:18 PM, Stefano Stabellini wrote: > >> I am not sure what the problem is. I would compared your partition table >> with a standard Linux distro UEFI image [1] to see if there are any >> important differences. Checkout the UEFI spec [2] section 13.3.1 onward >> to read the details of the partitions and filesystem requirements. >> > > I may have an idea of what's going on. Looking at the picture sent, The > disk you show seems to be the one used by your Ubuntu running in > VirtualBox. This seems to be confirmed by your previous e-mail where you > mention sda1. Am I right? > > Chaitanya - Yes you are absolutely right. I have Virtualbox on which I am running Ubuntu. And I have sda1 disk (bootable) which is FAT32 (1st partition for mapping fs0:). > You need to create that partition in the image used by QEMU. But likely > this will already be there if you use a pre-built image (e.g ubuntu or > else). I am assuming you were booting Linux using UEFI. > Chaitanya: I able to boot Linux through UEFI because I have root = rootfs.cpio which I created from buildroot. And in config file of Linux I have put INITRAMFS = "rootfs.cpio" . So do you want me to give root=/dev/sda1 while booting Linux on qemu? > > Cheers, > > -- > Julien Grall > Thanks, Chaitanya --000000000000a1b017056d6f96ce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, May 30, 2018 at 9:44 AM, Julien Grall <julien.grall@arm.com= > wrote:
Hi,

On 05/30/2018 05:18 PM, Stefano Stabellini wrote:
I am not sure what the problem is. I would compared your partition table with a standard Linux distro UEFI image [1] to see if there are any
important differences. Checkout the UEFI spec [2] section 13.3.1 onward
to read the details of the partitions and filesystem requirements.

I may have an idea of what's going on. Looking at the picture sent, The= disk you show seems to be the one used by your Ubuntu running in VirtualBo= x. This seems to be confirmed by your previous e-mail where you mention sda= 1. Am I right?

=C2=A0 =C2=A0Chaitanya - Yes you are absolutely right= . I have Virtualbox on which I am running Ubuntu.=C2=A0 And I have sda1 dis= k (bootable) which is FAT32=C2=A0
=C2=A0 =C2=A0(1st partition for= mapping fs0:).

=C2=A0
You need to create that partition in the image used by QEMU. But likely thi= s will already be there if you use a pre-built image (e.g ubuntu or else). = I am assuming you were booting Linux using UEFI.

<= /div>
=C2=A0 Chaitanya: I able to boot Linux through UEFI because I hav= e root =3D rootfs.cpio which I created from buildroot. And in config file o= f Linux I have put INITRAMFS =3D=C2=A0 =C2=A0 =C2=A0 =C2=A0 "rootfs.cp= io" . So do you want me to give root=3D/dev/sda1 while booting Linux o= n qemu?

Cheers,

--
Julien Grall

Thanks,
C= haitanya=C2=A0

--000000000000a1b017056d6f96ce-- --===============1461336723690859892== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cHM6Ly9saXN0 cy54ZW5wcm9qZWN0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hlbi1kZXZlbA== --===============1461336723690859892==--