From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCHv9 0/9] Xen: extend kexec hypercall for use with pv-ops kernels Date: Mon, 21 Oct 2013 13:56:09 +0100 Message-ID: <52652469.2040703@citrix.com> References: <1381251310-29449-1-git-send-email-david.vrabel@citrix.com> <20131018184031.GA12658@router-fw-old.local.net-space.pl> <5261C0D0.4090606@cantab.net> <20131021121940.GY3626@debian70-amd64.local.net-space.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20131021121940.GY3626@debian70-amd64.local.net-space.pl> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Daniel Kiper Cc: Daniel Kiper , Keir Fraser , David Vrabel , Jan Beulich , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 21/10/13 13:19, Daniel Kiper wrote: > On Sat, Oct 19, 2013 at 12:14:24AM +0100, David Vrabel wrote: >> On 18/10/2013 19:40, Daniel Kiper wrote: >>> On Tue, Oct 08, 2013 at 05:55:01PM +0100, David Vrabel wrote: >>>> The series (for Xen 4.4) improves the kexec hypercall by making Xen >>>> responsible for loading and relocating the image. This allows kexec >>>> to be usable by pv-ops kernels and should allow kexec to be usable >>>> from a HVM or PVH privileged domain. >>> >>> I could not load panic image because Xen crashes in following way: >>> >>> (XEN) ----[ Xen-4.4-unstable x86_64 debug=y Tainted: C ]---- >> [...] >>> (XEN) Xen call trace: >>> (XEN) [] kimage_free+0x67/0xd2 >>> (XEN) [] do_kimage_alloc+0x29c/0x2f0 >>> (XEN) [] kimage_alloc+0xb1/0xe6 >>> (XEN) [] do_kexec_op_internal+0x68e/0x789 >>> (XEN) [] do_kexec_op+0xe/0x12 >>> (XEN) [] syscall_enter+0xeb/0x145 >> >> The appended patch should fix this crash which only occurs if there's an >> error in do_kimage_alloc(). > > Patch had wrapped lines. I hope that I fixed it properly. > I cannot load panic kernel. kexec fails with following message: > > kexec_load failed: Cannot assign requested address This is -EADDRINVALID which means one of a) the entry point isn't within a segment. b) one of the segments is not page aligned. c) one of the segments is not within the crash region. But the segments kexec has constructed all looked fine to me (and similar to the segments I see). I'm afraid I cannot reproduce either of your failures. Are you sure you've built everything correctly? In particular has kexec-tools been built against the correct version of Xen headers? David