Re: ports/Xen on CURRENT, error: ELF start or entries are out of bounds.
On Thu, 10 Mar 2016, brahmann wrote: > Hi all. > I'm trying to run XEN on latest current as dom0. > Did all by manual: http://wiki.xen.org/wiki/FreeBSD_Dom0 (except compiling > from git, cant compile tools, so just used ports xen/xen-tools/xen-kernel) > And stuck with such an error: > > --- > (XEN) elf_xen_addr_calc_check: ERROR: ELF start or entries are out of bounds. > Could not set up DOM0 guest OS > --- > > This only drops on console while xen kernel boots, all other strings are OK > according to manual. > Link to photo of speedy console log: http://imgur.com/a5b9CLE > If need details pls ask. > > Please, tell me where to look or what to do or at least guide me in the right > direction. Ed committed the fix to this a couple of days ago, as of r297242 this should be fixed. Roger. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: ports/Xen on CURRENT, error: ELF start or entries are out of bounds.
On Tue, 22 Mar 2016, Ed Maste wrote: > On 21 March 2016 at 10:50, Ed Maste wrote: > > On 17 March 2016 at 13:30, dfh0522 . wrote: > >> > >> I need to add WITHOUT_ELFCOPY_AS_OBJCOPY after r296096, > > > > Sorry for the trouble. > > > > I've submitted an ELF Tool Chain ticket > > (https://sourceforge.net/p/elftoolchain/tickets/524/) for this issue > > in elfcopy. I expect either Roger or I will have a fix in the next few > > days, but WITHOUT_ELFCOPY_AS_OBJCOPY will do for now. > > Kai has committed a potential fix for the ticket to the ELF Tool Chain > repo. I've made a patch for the FreeBSD contrib copy available for > testing at https://people.freebsd.org/~emaste/patches/elfcopy-lma.diff > . Thanks for the notice! I've tried the patch and it indeed fixes the issue seen on the FreeBSD kernel, here's the readelf output now: Program Headers: Type Offset VirtAddr PhysAddr FileSizMemSiz FlgAlign PHDR 0x0040 0x80200040 0x00200040 0x0150 0x0150 R E0x8 INTERP 0x0190 0x80200190 0x00200190 0x000d 0x000d R 0x1 [Requesting program interpreter: /red/herring] LOAD 0x 0x8020 0x0020 0x013ed618 0x013ed618 R E0x20 LOAD 0x013ee000 0x817ee000 0x017ee000 0x00135c38 0x0060fc40 RW 0x20 DYNAMIC0x013ee000 0x817ee000 0x017ee000 0x00d0 0x00d0 RW 0x8 GNU_STACK 0x 0x 0x 0x 0x RWE0x8 Roger. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: ports/Xen on CURRENT, error: ELF start or entries are out of bounds.
On 21 March 2016 at 10:50, Ed Maste wrote: > On 17 March 2016 at 13:30, dfh0522 . wrote: >> >> I need to add WITHOUT_ELFCOPY_AS_OBJCOPY after r296096, > > Sorry for the trouble. > > I've submitted an ELF Tool Chain ticket > (https://sourceforge.net/p/elftoolchain/tickets/524/) for this issue > in elfcopy. I expect either Roger or I will have a fix in the next few > days, but WITHOUT_ELFCOPY_AS_OBJCOPY will do for now. Kai has committed a potential fix for the ticket to the ELF Tool Chain repo. I've made a patch for the FreeBSD contrib copy available for testing at https://people.freebsd.org/~emaste/patches/elfcopy-lma.diff . ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: ports/Xen on CURRENT, error: ELF start or entries are out of bounds.
On 17 March 2016 at 13:30, dfh0522 . wrote: > > I need to add WITHOUT_ELFCOPY_AS_OBJCOPY after r296096, Sorry for the trouble. I've submitted an ELF Tool Chain ticket (https://sourceforge.net/p/elftoolchain/tickets/524/) for this issue in elfcopy. I expect either Roger or I will have a fix in the next few days, but WITHOUT_ELFCOPY_AS_OBJCOPY will do for now. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: ports/Xen on CURRENT, error: ELF start or entries are out of bounds.
> I've just noticied this issue, it's probably due to an issue with kernel > linking. It seems like the physical address specified in the ELF program > headers is wrong. I'm currently trying to bisect it in order to find the > commit that caused it, in the meantime I can confirm that r295683 and > older revisions should work fine. I need to add WITHOUT_ELFCOPY_AS_OBJCOPY after r296096, > $ readelf -l /boot/kernel/kernel # readelf -l /boot/kernel/kernel Elf file type is EXEC (Executable file) Entry point 0x802fb000 There are 6 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr FileSizMemSiz FlgAlign PHDR 0x0040 0x80200040 0x00200040 0x0150 0x0150 R E0x8 INTERP 0x0190 0x80200190 0x00200190 0x000d 0x000d R 0x1 [Requesting program interpreter: /red/herring] LOAD 0x 0x8020 0x0020 0x0147b978 0x0147b978 R E0x20 LOAD 0x0147b978 0x8187b978 0x0187b978 0x00134e40 0x0056e448 RW 0x20 DYNAMIC0x0147b978 0x8187b978 0x0187b978 0x00d0 0x00d0 RW 0x8 GNU_STACK 0x 0x 0x 0x 0x RWE0x8 Section to Segment mapping: Segment Sections... 00 01 .interp 02 .interp .hash .dynsym .dynstr .text .rodata set_sysctl_set set_sysinit_set set_sysuninit_set set_modmetadata_set set_kdb_dbbe_set set_ah_chips set_ah_rfs set_kbddriver_set set_sdt_providers_set set_sdt_probes_set set_sdt_argtypes_set set_cons_set set_gdb_dbgport_set usb_host_id set_vt_drv_set set_ratectl_set set_crypto_set set_ieee80211_ioctl_getset set_ieee80211_ioctl_setset set_scanner_set set_videodriver_set set_scterm_set set_scrndr_set set_vga_set kern_conf .eh_frame 03 .dynamic .got.plt .data set_pcpu .bss 04 .dynamic 05 # objcopy --version GNU objcopy 2.17.50 [FreeBSD] 2007-07-03 > With the non-working kernel? # readelf -l /boot/kernel.old/kernel Elf file type is EXEC (Executable file) Entry point 0x802fb000 There are 6 program headers, starting at offset 64 Program Headers: Type Offset VirtAddr PhysAddr FileSizMemSiz FlgAlign PHDR 0x0040 0x80200040 0x80200040 0x0150 0x0150 R E0x8 INTERP 0x0190 0x80200190 0x80200190 0x000d 0x000d R 0x1 [Requesting program interpreter: /red/herring] LOAD 0x 0x8020 0x8020 0x0147a418 0x0147a418 R E0x20 LOAD 0x0147a418 0x8187a418 0x8187a418 0x00134aa0 0x0056e0a8 RW 0x20 DYNAMIC0x0147a418 0x8187a418 0x8187a418 0x00d0 0x00d0 RW 0x8 GNU_STACK 0x 0x 0x 0x 0x RWE0x8 Section to Segment mapping: Segment Sections... 00 01 .interp 02 .interp .hash .dynsym .dynstr .text .rodata set_sysctl_set set_sysinit_set set_sysuninit_set set_modmetadata_set set_kdb_dbbe_set set_ah_chips set_ah_rfs set_kbddriver_set set_sdt_providers_set set_sdt_probes_set set_sdt_argtypes_set set_cons_set set_gdb_dbgport_set usb_host_id set_vt_drv_set set_ratectl_set set_crypto_set set_ieee80211_ioctl_getset set_ieee80211_ioctl_setset set_scanner_set set_videodriver_set set_scterm_set set_scrndr_set set_vga_set kern_conf .eh_frame 03 .dynamic .got.plt .data set_pcpu .bss 04 .dynamic 05 # objcopy --version objcopy (elftoolchain r3400M) Cheers, JH. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: ports/Xen on CURRENT, error: ELF start or entries are out of bounds.
WITHOUT_ELFCOPY_AS_OBJCOPY = 1 Cheers, JH ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: ports/Xen on CURRENT, error: ELF start or entries are out of bounds.
Hi! On 11.03.2016 15:50, Roger Pau Monné wrote: Hello, On Thu, 10 Mar 2016, brahmann wrote: Hi all. I'm trying to run XEN on latest current as dom0. Did all by manual: http://wiki.xen.org/wiki/FreeBSD_Dom0 (except compiling from git, cant compile tools, so just used ports xen/xen-tools/xen-kernel) And stuck with such an error: Yes, using the ports (xen-kernel/xen-tools) is the recommended way, I should update the wiki page in order to note this. --- (XEN) elf_xen_addr_calc_check: ERROR: ELF start or entries are out of bounds. Could not set up DOM0 guest OS --- This only drops on console while xen kernel boots, all other strings are OK according to manual. Link to photo of speedy console log: http://imgur.com/a5b9CLE If need details pls ask. I've just noticied this issue, it's probably due to an issue with kernel linking. It seems like the physical address specified in the ELF program headers is wrong. I'm currently trying to bisect it in order to find the commit that caused it, in the meantime I can confirm that r295683 and older revisions should work fine. Thanks for the fast reply, already has started normally on revision r295683. Just to confirm, can you paste the output of the following command: $ readelf -l /boot/kernel/kernel With the non-working kernel? Sorry, but this server already re-setuped to anpther project, i've did successful setup on other with r295683 revision. If you still need this - i can setup on other server with latest CURRENT. Thanks, Roger. Anyway, thank you for help! With Best Regards, brahmann ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: ports/Xen on CURRENT, error: ELF start or entries are out of bounds.
Hello, On Thu, 10 Mar 2016, brahmann wrote: > Hi all. > I'm trying to run XEN on latest current as dom0. > Did all by manual: http://wiki.xen.org/wiki/FreeBSD_Dom0 (except compiling > from git, cant compile tools, so just used ports xen/xen-tools/xen-kernel) > And stuck with such an error: Yes, using the ports (xen-kernel/xen-tools) is the recommended way, I should update the wiki page in order to note this. > --- > (XEN) elf_xen_addr_calc_check: ERROR: ELF start or entries are out of bounds. > Could not set up DOM0 guest OS > --- > > This only drops on console while xen kernel boots, all other strings are OK > according to manual. > Link to photo of speedy console log: http://imgur.com/a5b9CLE > If need details pls ask. I've just noticied this issue, it's probably due to an issue with kernel linking. It seems like the physical address specified in the ELF program headers is wrong. I'm currently trying to bisect it in order to find the commit that caused it, in the meantime I can confirm that r295683 and older revisions should work fine. Just to confirm, can you paste the output of the following command: $ readelf -l /boot/kernel/kernel With the non-working kernel? Thanks, Roger. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"