From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, f.ebner@proxmox.com
Cc: Jordan Justen <jordan.l.justen@intel.com>,
Pawel Polawski <ppolawsk@redhat.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Oliver Steffen <osteffen@redhat.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [edk2-devel] [PATCH v2 3/4] OvmfPkg/PlatformInitLib: dynamic mmio window size
Date: Wed, 17 May 2023 07:59:07 +0200 [thread overview]
Message-ID: <2jjqzc74i2v4q5bwcpcjcsjl3k5yww3chlr2zmtxznizietybu@y6cwtukhhoqn> (raw)
In-Reply-To: <f073645f-7078-70b3-474c-962977104965@proxmox.com>
On Tue, May 16, 2023 at 04:00:55PM +0200, Fiona Ebner wrote:
>
> Am 04.10.22 um 15:47 schrieb Gerd Hoffmann:
> > In case we have a reliable PhysMemAddressWidth use that to dynamically
> > size the 64bit address window. Allocate 1/8 of the physical address
> > space and place the window at the upper end of the address space.
> >
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>
> Hi,
> a user recently reported that their Ubuntu 18.04 VM failed to boot after
> upgrading to our package based on edk2-stable202302 [0]. While the guest
> does reach GRUB, the disk attached via virtio-scsi-pci could not be
> found anymore. The user also reported that after changing the bus to
> pvscsi, the VM booted again, but the virtual NIC attached via
> virtio-net-pci did not work. Changing to e1000 made that work too.
So the system makes it successfully though the firmware boot phase,
but then the kernel fails to initialize the virtio devices, correct?
> Happy to provide more information and relevant parts of debug logs.
Kernel logs should give a clue what is going on.
take care,
Gerd
next prev parent reply other threads:[~2023-05-17 5:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 13:47 [PATCH v2 0/4] OvmfPkg: make better use of physical address space Gerd Hoffmann
2022-10-04 13:47 ` [PATCH v2 1/4] OvmfPkg/PlatformInitLib: qemu cpuid physbits detection Gerd Hoffmann
2022-10-04 13:47 ` [PATCH v2 2/4] OvmfPkg/PlatformInitLib: detect physical address space Gerd Hoffmann
2023-03-16 13:58 ` f.ebner
2023-03-16 14:37 ` Gerd Hoffmann
2023-03-17 11:34 ` [edk2-devel] " Fiona Ebner
2023-03-17 14:01 ` Gerd Hoffmann
2023-03-20 14:20 ` Fiona Ebner
2023-03-20 15:58 ` Gerd Hoffmann
2022-10-04 13:47 ` [PATCH v2 3/4] OvmfPkg/PlatformInitLib: dynamic mmio window size Gerd Hoffmann
2023-03-15 8:54 ` [edk2-devel] " joeyli
2023-03-15 9:28 ` Gerd Hoffmann
2023-05-16 14:00 ` Fiona Ebner
2023-05-17 5:59 ` Gerd Hoffmann [this message]
2023-05-17 13:38 ` [edk2-devel] " Fiona Ebner
2023-05-22 11:12 ` Gerd Hoffmann
2023-05-22 13:36 ` Fiona Ebner
2022-10-04 13:47 ` [PATCH v2 4/4] OvmfPkg/PciHotPlugInitDxe: reserve more mmio space Gerd Hoffmann
2022-10-04 15:57 ` Laszlo Ersek
2022-10-05 5:01 ` Gerd Hoffmann
2022-10-06 8:50 ` Laszlo Ersek
2022-10-07 21:49 ` [edk2-devel] [PATCH v2 0/4] OvmfPkg: make better use of physical address space Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2jjqzc74i2v4q5bwcpcjcsjl3k5yww3chlr2zmtxznizietybu@y6cwtukhhoqn \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox