From: Julien Grall <julien.grall@arm.com>
To: Feng Kan <fkan@apm.com>,
xen-devel@lists.xenproject.org, sstabellini@kernel.org
Cc: Ian Jackson <Ian.Jackson@citrix.com>,
nd@arm.com, Wei Liu <wei.liu2@citrix.com>
Subject: Re: xl create failure on arm64 with XEN 4.9rc6
Date: Thu, 25 May 2017 20:56:06 +0100 [thread overview]
Message-ID: <d9b23e37-3e28-82b3-155e-3d010ccf5e5d@arm.com> (raw)
In-Reply-To: <CAL85gmDY-dExU1i=nVeSYr0wkdDhXeFs3D7gxpb_uKNsDqPG4Q@mail.gmail.com>
(CC toolstack maintainers)
On 25/05/2017 19:58, Feng Kan wrote:
> Hi All:
Hello,
> This is not specifically against the XEN 4.9. I am using 4.12rc2
> kernel on arm64 platform. Started dom0 fine with ACPI enabled, but
> failed when creating the domU guest. Xen is built natively on the
> arm64 platform. Using the same kernel and ramdisk as dom0. Any idea as
> why it is stuck here
> would be greatly appreciated?
The first step would to try a stable release if you can. Also, it would
be useful if you provide information about the guest (i.e the
configuration) and your .config for the kernel.
I gave a try on Linux 4.12rc2 and I was not able to reproduce your error.
>
> xc: error: panic: xc_dom_boot.c:178: xc_dom_boot_domU_map: failed to
> mmap domU pages 0x450c2+0x2f3d [mmap, errno=22 (Invalid ar
> gument), chunksize 0x1000]: Internal error
> libxl: error: libxl_dom.c:679:libxl__build_dom: xc_dom_build_image
> failed: Invalid argument
> domainbuilder: detail: xc_dom_release: called
> libxl: error: libxl_create.c:1217:domcreate_rebuild_done: Domain
> 1:cannot (re-)build domain: -3
> libxl: debug: libxl_domain.c:1140:devices_destroy_cb: Domain 1:Forked
> pid 2477 for destroy of domain
> libxl: debug: libxl_create.c:1646:do_domain_create: Domain 0:ao
> 0x1ae10cb0: inprogress: poller=0x1ae10d40, flags=i
> libxl: debug: libxl_event.c:1869:libxl__ao_complete: ao 0x1ae10cb0:
> complete, rc=-3
> libxl: debug: libxl_event.c:1838:libxl__ao__destroy: ao 0x1ae10cb0: destroy
> libxl: debug: libxl_domain.c:871:libxl_domain_destroy: Domain 1:ao
> 0x1ae10cb0: create: how=(nil) callback=(nil) poller=0x1ae10d
> 40
>
> Seem to failed when mmapping pages for the ramdisk. I did some digging
> and the failure
> occurs during the IOCTL_PRIVCMD_MMAPBATCH_V2 call. It seems the
> 8192's page had a err code of -22.
-22 is -EINVAL. There are quite a few path return -EINVAL, did you try
to narrow the failure in the kernel?
The system have plenty of memory.
> Afterward, a null guest is created.
> As a side note, how do I get rid of it?
Normally the domain should be destroyed by the tools if the building failed.
You should be able to destroy it using 'xl domain domid' where domid is
the domain ID of the domain. If it does not work, then it means dom0 is
holding reference on some page belonging to that domain.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-25 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 18:58 xl create failure on arm64 with XEN 4.9rc6 Feng Kan
2017-05-25 19:56 ` Julien Grall [this message]
2017-05-26 0:37 ` Feng Kan
2017-05-26 12:40 ` Julien Grall
2017-05-26 22:22 ` Feng Kan
2017-05-28 17:12 ` Julien Grall
2017-05-30 17:41 ` Feng Kan
2017-05-31 13:04 ` Julien Grall
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=d9b23e37-3e28-82b3-155e-3d010ccf5e5d@arm.com \
--to=julien.grall@arm.com \
--cc=Ian.Jackson@citrix.com \
--cc=fkan@apm.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--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).