From: Baoquan He <bhe@redhat.com>
To: A Kundu <avikalpa@yahoo.com>
Cc: kexec@lists.infradead.org, horms@verge.net.au
Subject: Re: kexec failure with Xen 4.19-rc4 and 4.20-dev on linux host
Date: Fri, 2 Aug 2024 11:36:18 +0800 [thread overview]
Message-ID: <ZqxUMgcEHakeFPaU@MiWiFi-R3L-srv> (raw)
In-Reply-To: <cebc7800-df78-4f90-9f8e-82e3f9120b6e@yahoo.com>
On 07/31/24 at 06:34pm, A Kundu wrote:
> I am experiencing issues using kexec to load Xen 4.17(debian's apt version),
> Xen 4.19-rc4 (compiled from source) and 4.20-dev (compiled from source) on a
> debian host.
You should CC this to XEN dev list so that XEN dev knows this and may
provide help. Not everyone is interested in and knows XEN.
>
> System information:
> $ uname -a
> Linux host 6.9.10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.9.10-1 (2024-07-19)
> x86_64 GNU/Linux
>
> $ kexec --version # compiled from source tarball with ./configure --with-xen
> kexec-tools 2.0.29
>
> Steps to reproduce:
>
> 1. Set variables:
>
> XEN_HYPERVISOR="/boot/xen.gz"
> XEN_CMD="dom0_mem=6G dom0_max_vcpus=6 dom0_vcpus_pin cpufreq=xen"
>
> 2. Attempt to load Xen 4.19-rc4:
>
> # kexec -l "$XEN_HYPERVISOR" --command-line="$XEN_CMD"
> Could not find a free area of memory of 0x3b6001 bytes...
> elf_exec_build_load_relocatable: ELF exec load failed
>
> 3. Attempt to load Xen 4.20-dev:
>
> # kexec -l "$XEN_HYPERVISOR" --command-line="$XEN_CMD"
> Could not find a free area of memory of 0x3f8001 bytes...
> elf_exec_build_load_relocatable: ELF exec load failed
>
> 4. Attempt to load Xen 4.17 (from debian rrepositories):
> # kexec -l /boot/xen-4.17-amd64.gz --command-line="$XEN_CMD"
> Could not find a free area of memory of 0x3b4001 bytes...
> elf_exec_build_load_relocatable: ELF exec load failed
>
> If you need any further information to investigate this problem,
> please let me know.
>
> PS: If I used apt's pacakged version (which might be compiled
> --without-xen),
> it shows,
>
> # kexec -l "$XEN_HYPERVISOR" --command-line="$XEN_CMD"
> Cannot determine the file type of /boot/xen-4.17-amd64.gz
>
> # kexec -l "$XEN_HYPERVISOR" --command-line="$XEN_CMD" --type=bzImage
> Cannot determine the file type of /boot/xen-4.17-amd64.gz
>
>
> Thank you for your attention to this matter.
>
> A Kundu
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2024-08-02 3:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <05395ed2-3bf3-4926-8e24-c2e7ff37ed26.ref@yahoo.com>
2024-07-30 4:02 ` [KEXEC] Lacking documentation and kexec failure with Xen 4.19-rc4 and 4.20-dev on linux host A Kundu
2024-07-31 13:04 ` A Kundu
2024-08-02 3:36 ` Baoquan He [this message]
2024-08-02 7:28 ` A Kundu
2024-08-02 7:28 ` A Kundu
2024-08-02 7:55 ` Jan Beulich
2024-08-02 7:55 ` Jan Beulich
2024-08-04 13:17 ` A Kundu
2024-08-04 13:17 ` A Kundu
2024-08-05 6:01 ` Jan Beulich
2024-08-05 6:01 ` Jan Beulich
2024-08-05 7:52 ` Juergen Gross
2024-08-05 7:52 ` Juergen Gross
2024-08-05 8:13 ` Jan Beulich
2024-08-05 8:13 ` Jan Beulich
2024-08-05 8:12 ` [KEXEC] Lacking documentation and " Juergen Gross
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=ZqxUMgcEHakeFPaU@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=avikalpa@yahoo.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.