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

Re: [Xen-devel] [PATCH 0/2] Handle xen_platform_pci=0 case

Il 22/11/2013 16:13, Anthony PERARD ha scritto:

Here is a little series that attempt to fix the issue regarding
xen_platform_pci=0 not been handled.

There are two patches, the first one adds an option to specifies the QEMU
machine that a user wants and we handle the xen_platform_pci=0 case using the
new option.

The new options "qemu_machine_override" will help if one want to try a q35
based device model. Otherwise, it will be used by libxl to switch to the "pc"
machine instead of the "xenfv" one when necessary, as the only difference
between both (since QEMU 1.6) is the presence of the xen-platform pci device.


Anthony PERARD (2):
   libxl: adding support to use -machine option of QEMU.
   libxl: Handle xen_platform_pci=0 case with qemu-xen.

  tools/libxl/libxl_dm.c      | 31 +++++++++++++++++++++++++++++--
  tools/libxl/libxl_types.idl |  1 +
  tools/libxl/xl_cmdimpl.c    |  3 +++
  3 files changed, 33 insertions(+), 2 deletions(-)

Tested with upstream qemu 1.6 from staging:
vi Config.mk
QEMU_UPSTREAM_URL ?= git://xenbits.xen.org/staging/qemu-upstream-unstable.git

With xen_platform_pci=0 Fedora19 hvm domU gave me kernel panic on boot.
xl create -vvv, xl dmesg and serial domUs boot (with calltrace) logs on attachments.

With xen_platform_pci=1 boot correctly.

Attachment: FEDORA19-xl-dmesg.txt
Description: Text document

Attachment: FEDORA19-serial.log
Description: Text document

Attachment: FEDORA19-xl-create.log.txt
Description: Text document

Xen-devel mailing list



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