[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory
From: |
Laszlo Ersek \(Red Hat\) |
Subject: |
[Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug |
Date: |
Thu, 21 Feb 2019 09:14:36 -0000 |
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 will force the BAR allocations into 32-bit address space.
Obviously, that makes it a lot easier to run out of the (much smaller)
32-bit MMIO aperture, but if you don't have PCI(E) devices with large
MMIO BARs, then it should work (e.g. it should totally work in your
present use case).
And then you should be able to increase the DIMM hotplug area
significantly, without running out of the GPA range covered by 39
physical address bits:
//
// There's nothing more to do; the amount of memory above 4GB fully
// determines the highest address plus one. The memory hotplug area (see
// below) plays no role for the firmware in this case.
//
"This case" beeing (Pci64Size == 0).
Hope this helps.
--
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:
Invalid
Bug description:
with qemu 2.9 it hangs at the efi stage when memory-hotplug is enabled
and it has a virtio-net devices
the ovmf images where compiled from https://github.com/tianocore/edk2
(current master)
reproducer:
qemu-system-x86_64 -drive
'if=pflash,unit=0,format=raw,readonly,file=./OVMF_CODE.fd' -drive
'if=pflash,unit=1,format=raw,file=./my_OVMF_VARS.fd' -smp 1 -vga std
-netdev 'type=tap,id=mynet' -device 'virtio-net-pci,netdev=mynet'
-display sdl -nodefaults -m 'size=1G,slots=256,maxmem=1024G'
interestingly, it works when you do the following:
- omit the virtio-net-pci device
- use seabios
- use less maxmem, e.g. 512G
qemu was compiled from source (v2.9.0) with following options:
./configure --target-list=x86_64-softmmu --disable-xen --enable-gnutls
--enable-sdl --enable-linux-aio --enable-rbd --enable-libiscsi
--disable-smartcard --audio-drv-list="alsa" --enable
-spice --enable-usb-redir --enable-glusterfs --enable-libusb --disable-gtk
--enable-xfsctl --enable-numa --disable-strip --enable-jemalloc --enable-virtfs
--disable-libnfs --disable-fdt --disable-guest-agent --disable-guest-agent-msi
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1685242/+subscriptions
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, (continued)
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, Laszlo Ersek \(Red Hat\), 2019/02/18
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, flumm, 2019/02/20
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, flumm, 2019/02/20
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, flumm, 2019/02/20
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, flumm, 2019/02/20
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, flumm, 2019/02/20
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, flumm, 2019/02/20
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, flumm, 2019/02/20
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, Laszlo Ersek \(Red Hat\), 2019/02/20
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug, Laszlo Ersek \(Red Hat\), 2019/02/20
- [Qemu-devel] [Bug 1685242] Re: ovmf hangs at efi with virtio-net memory hotplug,
Laszlo Ersek \(Red Hat\) <=