[Bug 208635] XEN DOM0 not start on CURRENT

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Apr 8 15:01:38 UTC 2016


            Bug ID: 208635
           Summary: XEN DOM0 not start on CURRENT
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: ivan.uadm at gmail.com
                CC: freebsd-amd64 at FreeBSD.org
                CC: freebsd-amd64 at FreeBSD.org

Created attachment 169107
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=169107&action=edit
Screen at bug time

Hi there,

I start playing with FreeBSD DOM0 and recieve message on boot with XEN kernel
elf_xen_addr_calc_check: ERROR: ELF start or entries are out of bounds 
Panic on CPU 0:
Could not set up DOM0 guest OS

I use this manual http://wiki.xen.org/wiki/FreeBSD_Dom0 but I use ports and

$ uname -a: FreeBSD rnhv00 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r296485: Tue
Mar  8 07:04:36 UTC 2016    
root at releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

$ readelf -l /boot/kernel/kernel

Elf file type is EXEC (Executable file)
Entry point 0xffffffff802fc000
There are 6 program headers, starting at offset 64

Program Headers:
  Type           Offset             VirtAddr           PhysAddr
                 FileSiz            MemSiz              Flg    Align
  PHDR           0x0000000000000040 0xffffffff80200040 0xffffffff80200040
                 0x0000000000000150 0x0000000000000150  R E    0x8
  INTERP         0x0000000000000190 0xffffffff80200190 0xffffffff80200190
                 0x000000000000000d 0x000000000000000d  R      0x1
      [Requesting program interpreter: /red/herring]
  LOAD           0x0000000000000000 0xffffffff80200000 0xffffffff80200000
                 0x00000000013e7318 0x00000000013e7318  R E    0x200000
  LOAD           0x00000000013e7318 0xffffffff817e7318 0xffffffff817e7318
                 0x00000000001364a0 0x000000000060f4a8  RW     0x200000
  DYNAMIC        0x00000000013e7318 0xffffffff817e7318 0xffffffff817e7318
                 0x00000000000000d0 0x00000000000000d0  RW     0x8
  GNU_STACK      0x0000000000000000 0x0000000000000000 0x0000000000000000
                 0x0000000000000000 0x0000000000000000  RWE    0x8

 Section to Segment mapping:
  Segment Sections...
   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
   03     .dynamic .got.plt .data set_pcpu .bss 
   04     .dynamic 

You are receiving this mail because:
You are on the CC list for the bug.

More information about the freebsd-amd64 mailing list