[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [BUG?] qemuu only built with i386-softmmu


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Steven Haigh <netwiz@xxxxxxxxx>
  • Date: Fri, 5 Feb 2016 08:09:25 +1100
  • Delivery-date: Thu, 04 Feb 2016 21:09:48 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

Hi all,

Looking specifically at 4.6.0.

It seems that the Makefile for qemuu uses the following:
        $$source/configure --enable-xen --target-list=i386-softmmu \
                $(QEMU_XEN_ENABLE_DEBUG) \
                --prefix=$(LIBEXEC) \
                --libdir=$(LIBEXEC_LIB) \
                --includedir=$(LIBEXEC_INC) \
                --source-path=$$source \
                --extra-cflags="-I$(XEN_ROOT)/tools/include \
                -I$(XEN_ROOT)/tools/libxc/include \
                -I$(XEN_ROOT)/tools/xenstore/include \
                -I$(XEN_ROOT)/tools/xenstore/compat/include \
                $(EXTRA_CFLAGS_QEMU_XEN)" \
                --extra-ldflags="-L$(XEN_ROOT)/tools/libxc \
                -L$(XEN_ROOT)/tools/xenstore \
                $(QEMU_UPSTREAM_RPATH)" \
                --bindir=$(LIBEXEC_BIN) \
                --datadir=$(SHAREDIR)/qemu-xen \
                --localstatedir=$(localstatedir) \
                --disable-kvm \
                --disable-docs \
                --disable-guest-agent \
                --python=$(PYTHON) \
                $(CONFIG_QEMUU_EXTRA_ARGS) \
                --cpu=$(IOEMU_CPU_ARCH) \
                $(IOEMU_CONFIGURE_CROSS); \
        $(MAKE) all

As such, this only builds the 32 bit version of qemuu. It seems that
starting a HVM with more than 4Gb of RAM fails:

libxl: debug: libxl_event.c:691:libxl__ev_xswatch_deregister: watch
w=0xa4d188: deregister unregistered
xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x5b3a4
xc: detail: elf_parse_binary: memory: 0x100000 -> 0x15b3a4
xc: detail: VIRTUAL MEMORY ARRANGEMENT:
xc: detail:   Loader:   0000000000100000->000000000015b3a4
xc: detail:   Modules:  0000000000000000->0000000000000000
xc: detail:   TOTAL:    0000000000000000->000000017f000000
xc: detail:   ENTRY:    0000000000100600
xc: detail: PHYSICAL MEMORY ALLOCATION:
xc: detail:   4KB PAGES: 0x0000000000000200
xc: detail:   2MB PAGES: 0x00000000000005f7
xc: detail:   1GB PAGES: 0x0000000000000003
xc: detail: elf_load_binary: phdr 0 at 0x7ff67320f000 -> 0x7ff673260910
xc: error: Could not clear special pages (22 = Invalid argument):
Internal error
libxl: error: libxl_dom.c:1003:libxl__build_hvm: hvm building failed

In building my Xen 4.6.0 packages, I disable qemu-traditional and ONLY
build qemu-upstream - however as the value for i386-softmmu is not based
on variables, I'm not sure this makes a difference.

My question is, should this also build x86_64-softmmu as well as
i386-softmmu at a bare minimum?

-- 
Steven Haigh

Email: netwiz@xxxxxxxxx
Web: https://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.