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

[Xen-devel] [Bug] Intel RMRR support with upstream Qemu

  • To: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • From: "Zhang, Xiong Y" <xiong.y.zhang@xxxxxxxxx>
  • Date: Fri, 21 Jul 2017 10:57:55 +0000
  • Accept-language: en-US
  • Cc: "Zhang, Xiong Y" <xiong.y.zhang@xxxxxxxxx>
  • Delivery-date: Fri, 21 Jul 2017 10:59:28 +0000
  • Dlp-product: dlpe-windows
  • Dlp-reaction: no-action
  • Dlp-version:
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: AdMCDFliQB9vwJzuRPKDdhnf3NXUCg==
  • Thread-topic: [Bug] Intel RMRR support with upstream Qemu

On an intel skylake machine with upstream qemu, if I add “rdm=strategy=host, policy=strict” to hvm.cfg, win 8.1 DomU couldn’t boot up and continues reboot.


Steps to reproduce this issue:

1)       Boot xen with iommu=1 to enable iommu

2)       hvm.cfg contain:



disk=[‘win8.1 img’]




3)       xl cr hvm.cfg


Conditions to reproduce this issue:

1)       DomU memory size > the top address of RMRR. Otherwise, this issue will disappear.

2)       rdm=” strategy=host,policy=strict” should exist

3)       Windows DomU.  Linux DomU doesn’t have such issue.

4)       Upstream qemu.  Traditional qemu doesn’t have such issue.


In this situation, hvmloader will relocate some guest ram below RMRR to high memory, and it seems window guest access an invalid address.

Could someone give me some suggestions on how to debug this ?



Xen-devel mailing list



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