xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Chaitanya Deshpande <chaitanyagd11@gmail.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, Julien Grall <julien.grall@arm.com>
Subject: Re: Query for running Xen on ARM
Date: Tue, 29 May 2018 21:50:35 -0700	[thread overview]
Message-ID: <CA+a_UndZ_7E9JNBPwVsfAjPP4PPwx2ter87q9ioDnEE5PiNS_g@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1805291305050.5563@sstabellini-ThinkPad-X260>


[-- Attachment #1.1: Type: text/plain, Size: 3773 bytes --]

Hi Stefano,

I have created W95 FAT32 partition as my first partition (Bootable) but
still I unable to see fs0: in the list.

Please find attached copy of the screen shot with this Email.

Please can you help me.

Thanks,
Chaitanya

On Tue, May 29, 2018 at 1:06 PM, Stefano Stabellini <sstabellini@kernel.org>
wrote:

> FS0: is mapped to the first partition on your disk, that needs to be
> formatted with the FAT filesystem. Do you have a FAT partition on your
> disk?
>
> On Tue, 29 May 2018, Chaitanya Deshpande wrote:
> > Hi Stefano, Julien,
> > I am able to solve that problem. Now the problem I am facing is my qemu
> is unable to find file system from EFI.
> >
> > Please find attached copy with this Email.
> >
> > No fs0: in mapping table. (Only BLK0: and BLK1:)
> >
> > Thanks,
> > Chaitanya
> >
> > On Tue, May 29, 2018 at 7:35 AM, Julien Grall <julien.grall@arm.com>
> wrote:
> >       (+Stefano)
> >
> >       On 27/05/18 18:48, Chaitanya Deshpande wrote:
> >             Hi,
> >
> >
> >       Hello Chaitanya,
> >
> >             I am Chaitanya, pursuing my master’s degree from Portland
> State University in Embedded Systems.
> >
> >             I have started working on Xen Project and I am beginner in
> this field.
> >
> >             I have followed all the steps which are given in this link –
> >
> >             https://wiki.xenproject.org/wiki/Xen_ARM_with_
> Virtualization_Extensions/qemu-system-aarch64
> >
> >             https://wiki.xenproject.org/wiki/Xen_ARM_with_
> Virtualization_Extensions#Building_Xen_on_ARM
> >
> >
> >             1) I have used buildroot(rootfs.cpio) for building Linux.
> >
> >             2) I have succeeded in booting Linux on Qemu
> (qemu-system-.aarch64)
> >
> >             3) Used make dist-xen XEN_TARGET_ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu-  for cross compiling and
> >             getting Xen binary.
> >
> >             4) My root is root - root=/dev/sda1
> >
> >
> >       May I ask why the root is different from the example in the wiki
> page? Are you using a different setup for the disk
> >       (e.g no virtio)?
> >
> >
> >
> >             After running the  last step UEFI Prompt opens and it gives
> me this error.
> >
> >
> >       What do you mean? Which last step?
> >
> >
> >             error: no such device: root.
> >
> >
> >       This is coming from UEFI, right?
> >
> >
> >             Press any key to continue...
> >             EFI stub: Booting Linux Kernel...
> >
> >
> >       This is booting Linux and not Xen. It is also trying to using ACPI
> rather than DT. Would it be possible for you to
> >       drop to the UEFI shell and try to boot by hand?
> >
> >             EFI stub: Using DTB from configuration table
> >             EFI stub: Exiting boot services and installing virtual
> address map...
> >             [   11.231789] acpi PNP0A08:00: Bus 0000:00 not present in
> PCI namespace
> >             [   41.972816] NMI watchdog: BUG: soft lockup - CPU#1 stuck
> for 23s! [swapper/0:1]
> >             [  229.940369] NMI watchdog: BUG: soft lockup - CPU#0 stuck
> for 23s! [swapper/0:1]
> >             [  257.939966] NMI watchdog: BUG: soft lockup - CPU#0 stuck
> for 23s! [swapper/0:1]
> >             [  290.035395] NMI watchdog: BUG: soft lockup - CPU#3 stuck
> for 23s! [swapper/0:1]
> >             [  303.595373] kvm [1]: error: no compatible GIC node found
> >             [  303.619405] kvm [1]: error initializing Hyp mode: -19
> >
> >             I am unable to find the root cause of this issue. Please can
> anyone help me with this.
> >
> >
> >       Cheers,
> >
> >       --
> >       Julien Grall
> >
> >
> >
> >
>

[-- Attachment #1.2: Type: text/html, Size: 5208 bytes --]

[-- Attachment #2: Qemu_UEFI.png --]
[-- Type: image/png, Size: 187933 bytes --]

[-- Attachment #3: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-05-30  4:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-27 17:48 Query for running Xen on ARM Chaitanya Deshpande
2018-05-29 14:35 ` Julien Grall
2018-05-29 14:44   ` Chaitanya Deshpande
2018-05-29 20:06     ` Stefano Stabellini
2018-05-30  4:50       ` Chaitanya Deshpande [this message]
2018-05-30 16:18         ` Stefano Stabellini
2018-05-30 16:44           ` Julien Grall
2018-05-30 17:21             ` Chaitanya Deshpande
2018-05-30 17:22           ` Chaitanya Deshpande
2018-05-29 15:54   ` Chaitanya Deshpande

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=CA+a_UndZ_7E9JNBPwVsfAjPP4PPwx2ter87q9ioDnEE5PiNS_g@mail.gmail.com \
    --to=chaitanyagd11@gmail.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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).