From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web10.43258.1684303154453579138 for ; Tue, 16 May 2023 22:59:15 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Ch7zGIHP; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1684303153; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=foUIkjjPsAPJfmpecfGm+qdDsghXUK86IG+0PjU6/U4=; b=Ch7zGIHPJPZkkTu/bzMRzcY3KZcKIfoH1LaYfURpCzTLUufWfulyyKDqYsc5XjbNNX61r0 meXhSYZva+k6HcnznLXipieXqr4Ww4Vcsae6dnY5+LAygwRZKvduiM2W2VjgWQvXl04uZ/ yPNLU7AFkU4Nzgiz5n94oakDGJXTaE4= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-74-g4MO4Be8NGewyszFBM9-jA-1; Wed, 17 May 2023 01:59:10 -0400 X-MC-Unique: g4MO4Be8NGewyszFBM9-jA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id C5A6E185A790; Wed, 17 May 2023 05:59:09 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.130]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6AAE840C6EC4; Wed, 17 May 2023 05:59:09 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id A221118007A1; Wed, 17 May 2023 07:59:07 +0200 (CEST) Date: Wed, 17 May 2023 07:59:07 +0200 From: "Gerd Hoffmann" To: devel@edk2.groups.io, f.ebner@proxmox.com Cc: Jordan Justen , Pawel Polawski , Jiewen Yao , Oliver Steffen , Ard Biesheuvel , Thomas Lamprecht Subject: Re: [edk2-devel] [PATCH v2 3/4] OvmfPkg/PlatformInitLib: dynamic mmio window size Message-ID: <2jjqzc74i2v4q5bwcpcjcsjl3k5yww3chlr2zmtxznizietybu@y6cwtukhhoqn> References: <20221004134728.55499-1-kraxel@redhat.com> <20221004134728.55499-4-kraxel@redhat.com> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 > > 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