>>> On 28.09.17 at 16:36, <honz...@microsoft.com> wrote: >> -----Original Message----- >>From: Jan Beulich [mailto:jbeul...@suse.com] >>Sent: Thursday, September 28, 2017 5:39 PM >>To: Hongjiang Zhang <honz...@microsoft.com> >>Cc: xen-de...@lists.xenproject.org; Juergen Gross <jgr...@suse.com> >>Subject: RE: [Xen-devel] Only 1 CPU was detected >> >>>>> On 28.09.17 at 11:32, <honz...@microsoft.com> wrote: >>>> -----Original Message----- >>>>From: Jan Beulich [mailto:jbeul...@suse.com] >>>>Sent: Thursday, September 28, 2017 4:38 PM >>>>To: Hongjiang Zhang <honz...@microsoft.com> >>>>Cc: xen-de...@lists.xenproject.org; Juergen Gross <jgr...@suse.com> >>>>Subject: Re: [Xen-devel] Only 1 CPU was detected >>>> >>>>>>> On 28.09.17 at 09:22, <honz...@microsoft.com> wrote: >>>>> See the attachment. >>>> >>>>With >>>> >>>>(XEN) ACPI Error (tbxfroot-0218): A valid RSDP was not found [20070126] >>>> >>>>I wonder if you're trying to use xen.gz on an EFI system. Is so, you want to >>> use >>>>xen.efi there instead if firmware doesn't set up enough compatibility things >>> in >>>>EFI Mode, or enable CSM if an option like this is provided by firmware >>>>setup. >>>> >>> I cannot use xen.efi. It reports "error: invalid arch-dependent ELF magic" >> >>Are you using a 32-bit EFI by chance? >> > I don't think so. I used "file xen.efi" to check and it indicates it is > x86_64: > root@lis-f2334:~# file /boot/xen-4.8-amd64.efi > /boot/xen-4.8-amd64.efi: PE32+ executable (EFI application) x86-64 (stripped > to > external PDB), for MS Windows
The question was about your firmware, not xen.efi. The latter can only be built as a 64-bit binary right now. Hence ... > Shall I build xen by myself? ... no, unless you would first invest quite a bit of work into getting Xen to also build as a 32-bit EFI binary (and this of course would help only if indeed your EFI implementation is a 32-bit one). Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
