Last night I remembered another tidbit:
In OVMF, you can entirely disable the 64-bit MMIO aperture.
-fw_cfg name=opt/ovmf/X-PciMmio64Mb,string=0
If you use the above switch, the firmware log should contain the
following message:
> GetFirstNonAddress: disabling 64-bit PCI host aperture
This w
* From "debug-nonworking.log":
> GetFirstNonAddress: Pci64Base=0x88 Pci64Size=0x8
> [...]
> PublishPeiMemory: mPhysMemAddressWidth=40 PeiMemoryCap=69644 KB
> [...]
> Type = Mem64; Base = 0x88; Length = 0x10; Alignment =
> 0xF
> Base = 0x88; Length
The reason why it behaves differently with machine types <= 2.4 is that
- up to and including qemu-2.4, the calculation of the DIMM hotplug area was
incorrect,
- in 2.5, the calculation was fixed,
- but for the migration compatibility of machine types <= 2.4, the old
calculation was preserved for
** Attachment added: "qemu-cmdline"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240132/+files/qemu-cmdline
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Title:
ovmf hangs
** Attachment added: "debug-nonworking.log"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240134/+files/debug-nonworking.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Titl
** Attachment added: "qemu-cmdline"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240133/+files/qemu-cmdline
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Title:
ovmf hangs
** Attachment added: "debug-working-222G.log"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240135/+files/debug-working-222G.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
** Attachment added: "debug-working-novirtio-net.log"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240137/+files/debug-working-novirtio-net.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.ne
** Attachment added: "debug-working-2.6.log"
https://bugs.launchpad.net/qemu/+bug/1685242/+attachment/5240136/+files/debug-working-2.6.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Ti
i see,
but is there a good reason why it did work with an older qemu version/machine
type (<= 2.6)
also my cpuinfo says physical bits 39 but i cannot use more maxmem than 222G
i attached the cpuinfo, cmdline, and debug logs for a nonworking invocation and
one for each working, with 222G, with ma
OVMF places the 64-bit PCI MMIO aperture after the memory hotplug area.
If you specify `-m maxmem=1024G`, then accessing 64-bit MMIO BARs of
PCI(e) devices, allocated from the aperture, will require at least 41
address bits. If you use KVM, and nested paging (EPT on Intel, NPT on
AMD) is enabled, a
Tested here with versions of pc-i440fx-XX and it didn't work here on
qemu-server 5.0-46, qemu 2.12.1-1
Didn't work.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Title:
ovmf hangs at efi w
i forgot:
it also works with
-machine pc-i440fx-2.6
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1685242
Title:
ovmf hangs at efi with virtio-net memory hotplug
Status in QEMU:
New
Bug descr
13 matches
Mail list logo
