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

Re: [Xen-users] Unable to boot Xen on Hikey



I just got it to work. As that link said I disabled USB_DWC2 in the kernel and now it boots! I hope it works fine later. Thanks.

--
Saeed Mirzamohammadi
Ph.D. candidate
Computer Science Department
University of California, Irvine


On Tue, Aug 29, 2017 at 12:22 PM, Saeed Mirzamohammadi <saeed@xxxxxxx> wrote:
This is my Xen output when building with Xen 4.8. I stops after printing these:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 000000007a029000
(XEN) Loading ramdisk from boot module @ 000000000ae00000
(XEN) Allocating 1:1 mappings totalling 512MB for dom0:
(XEN) BANK[0] 0x00000040000000-0x00000060000000 (512MB)
(XEN) Grant table range: 0x00000005c00000-0x00000005c5e000
(XEN) Loading zImage from 000000007a029000 to 0000000040080000-0000000040ce8400
(XEN) Loading dom0 initrd from 000000000ae00000 to 0x0000000048200000-0x0000000048a00000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading dom0 DTB to 0x0000000048000000-0x000000004800aec1
(XEN) Scrubbing Free RAM on 1 nodes using 8 CPUs
(XEN) ..done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-x' three times to switch input to Xen)
(XEN) Freed 276kB init memory.
(XEN) traps.c:2505:d0v0 HSR=0x92000061 pc=0xffffffc0003f86ac gva=0xffffff800024000c gpa=0x00000021fc000c
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thanks,


--
Saeed Mirzamohammadi
Ph.D. candidate
Computer Science Department
University of California, Irvine


On Tue, Aug 29, 2017 at 12:21 PM, Saeed Mirzamohammadi <saeed@xxxxxxx> wrote:
I tried RELEASE-4.9.0 and RELEASE-4.8.0 and RELEASE-4.7.3. None of them boots. There were little differences. Xen 4.8 printed one line more and stopped:
~~~~~~~~~~~
.......
(XEN) Freed 268kB init memory.
(XEN) Hardware Dom0 shutdown: rebooting machine
~~~~~~~~~~~
Xen 4.9 rebooted after it failed to boot.

Do you think the issue is with the Xen version?

This is how I build Xen:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cd xen/xen
export CROSS_COMPILE=aarch64-linux-gnu-
export ARCH=arm64
export XEN_TARGET_ARCH=arm64
make defconfig
make -j8
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`

Should I make specific config for HiKey?

And in this link: https://lists.gt.net/xen/devel/433472, they could boot the system by disabling the USB_DWC2 in the kernel. I tried modifying the .config file directly and disabling the ones related to USB_DWC2  (commenting the line out) but when I tried rebuilding the kernel it restarted generating the .config file. So I couldn't apply this comment.


--
Saeed Mirzamohammadi
Ph.D. candidate
Computer Science Department
University of California, Irvine


On Tue, Aug 29, 2017 at 2:57 AM, Roger Pau Monné <roger.pau@xxxxxxxxxx> wrote:
On Sun, Aug 27, 2017 at 07:00:06PM -0700, Saeed Mirzamohammadi wrote:
> Hi,
>
> I'm following instructions on https://wiki.xenproject.org/wiki/HiKey and
> https://github.com/Jeeppler/xen-note/blob/master/arm64/hikey/hikey-xen-centos.md
> .
>
> I'm trying to boot Xen on Hikey but Xen doesn't boot! I can boot the
> linux individually with startup.sh. This works fine but when I try to boot
> xen (typing 4 and then xen), I get this output and nothing shows after:
>
> *Xen 4.7.0-rc (c/s Mon May 23 12:07:20 2016 +0100 git:8478c94) EFI loader*
> *Using configuration file 'xen.cfg'*
> *hi6220-hikey.dtb: 0x000000007acaf000-0x000000007acba6e0*
> *Image: 0x000000007a039000-0x000000007aca1400*
>
>
> My Xen version is: 4.7.0.rc4 and my dom0 is: android-hikey-linaro-4.1. I

Why use 4.7.0-rc4? First of all 4.7 is quite old, and then why pick a
release candidate and not 4.7.3 if you really need to use 4.7?

Roger.



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
https://lists.xen.org/xen-users

 


Rackspace

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