From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.groups.io (mail02.groups.io [66.175.222.108]) by spool.mail.gandi.net (Postfix) with ESMTPS id 0273B7803E5 for ; Thu, 14 Sep 2023 07:24:06 +0000 (UTC) DKIM-Signature: a=rsa-sha256; bh=rgR0YBdWYmh0qEtZvcoFX8/MWoI/87/BkZPcrA4ZeDs=; c=relaxed/simple; d=groups.io; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:In-Reply-To:Precedence:List-Subscribe:List-Help:Sender:List-Id:Mailing-List:Delivered-To:Reply-To:List-Unsubscribe-Post:List-Unsubscribe:Content-Type:Content-Disposition; s=20140610; t=1694676245; v=1; b=xAzu9PfFUr+nlXUcUcXFBdLpWg3GfyEekmygOzygR3G8KoR/opWp4HWddjMRNHaCX7f9E1q8 rwopOWpdzseQP8ILsCi31Eh6ShCzjHKtnQdBRurNew3lVXKnruFsCVnM9Px7Jcd9llC4YyL/NBD 21p/b0t4x4Uhr5h36qwitAh0= X-Received: by 127.0.0.2 with SMTP id 69XCYY7687511xdJT5X9HAXA; Thu, 14 Sep 2023 00:24:05 -0700 X-Received: from mail-wm1-f47.google.com (mail-wm1-f47.google.com [209.85.128.47]) by mx.groups.io with SMTP id smtpd.web11.6398.1694676244954558579 for ; Thu, 14 Sep 2023 00:24:05 -0700 X-Received: by mail-wm1-f47.google.com with SMTP id 5b1f17b1804b1-40037db2fe7so6407735e9.0 for ; Thu, 14 Sep 2023 00:24:04 -0700 (PDT) X-Gm-Message-State: mLjUC9dBIWbhZhJ9LT3wKXDKx7686176AA= X-Google-Smtp-Source: AGHT+IGdpI724Ccm9SB93cO/aG91/y2l4aUotiG5uYesz80v+pFyPG4E8kssbuovydH7BHVNCplYDA== X-Received: by 2002:a05:600c:108b:b0:401:cc0f:f866 with SMTP id e11-20020a05600c108b00b00401cc0ff866mr3978170wmd.12.1694676243366; Thu, 14 Sep 2023 00:24:03 -0700 (PDT) X-Received: from localhost (cst2-173-16.cust.vodafone.cz. [31.30.173.16]) by smtp.gmail.com with ESMTPSA id m10-20020a7bcb8a000000b00402f7b50517sm1136431wmi.40.2023.09.14.00.24.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 14 Sep 2023 00:24:02 -0700 (PDT) Date: Thu, 14 Sep 2023 09:24:02 +0200 From: "Andrew Jones" To: Laszlo Ersek Cc: edk2-devel-groups-io , Andrei Warkentin , Ard Biesheuvel , Gerd Hoffmann , Jiewen Yao , Jordan Justen , Sunil V L Subject: Re: [edk2-devel] [PATCH 3/3] OvmfPkg/RiscVVirt/README: document direct kernel boot Message-ID: <20230914-cf5605139eaeecd33cba1d2a@orel> References: <20230913105551.12680-1-lersek@redhat.com> <20230913105551.12680-4-lersek@redhat.com> MIME-Version: 1.0 In-Reply-To: <20230913105551.12680-4-lersek@redhat.com> Precedence: Bulk List-Subscribe: List-Help: Sender: devel@edk2.groups.io List-Id: Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io Reply-To: devel@edk2.groups.io,ajones@ventanamicro.com List-Unsubscribe-Post: List-Unsubscribe=One-Click List-Unsubscribe: Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GND-Status: LEGIT Authentication-Results: spool.mail.gandi.net; dkim=pass header.d=groups.io header.s=20140610 header.b=xAzu9PfF; dmarc=none; spf=pass (spool.mail.gandi.net: domain of bounce@groups.io designates 66.175.222.108 as permitted sender) smtp.mailfrom=bounce@groups.io On Wed, Sep 13, 2023 at 12:55:51PM +0200, Laszlo Ersek wrote: > Direct (fw_cfg) kernel boot works on the RiscVVirt firmware platform too; > I've tested it after extracting the kernel, initrd, and kernel command > line from "openSUSE-Tumbleweed-RISC-V-E20-efi.riscv64.raw". Document this > type of boot, because at least historically, fw_cfg kernel boot was > implemented differently between OVMF and ArmVirtQemu. Thanks: Drew, Sunil. > > Cc: Andrei Warkentin > Cc: Andrew Jones > Cc: Ard Biesheuvel > Cc: Gerd Hoffmann > Cc: Jiewen Yao > Cc: Jordan Justen > Cc: Sunil V L > Signed-off-by: Laszlo Ersek > --- > OvmfPkg/RiscVVirt/README.md | 33 +++++++++++++++++++- > 1 file changed, 32 insertions(+), 1 deletion(-) > > diff --git a/OvmfPkg/RiscVVirt/README.md b/OvmfPkg/RiscVVirt/README.md > index 1dba1a26af2d..47b97dd64a2f 100644 > --- a/OvmfPkg/RiscVVirt/README.md > +++ b/OvmfPkg/RiscVVirt/README.md > @@ -75,8 +75,39 @@ Below example shows how to boot openSUSE Tumbleweed E20. > Currently, `acpi=off` is recommended unless you are developing ACPI support > yourself. > > +3) Running QEMU with direct kernel boot > + > + The following example boots the same guest, but loads the kernel image and > + the initial RAM disk (which were extracted from > + `openSUSE-Tumbleweed-RISC-V-E20-efi.riscv64.raw`) from the host filesystem. > + It also sets the guest kernel command line on the QEMU command line. > + > + CMDLINE=(root=UUID=76d9b92d-09e9-4df0-8262-c1a7a466f2bc > + systemd.show_status=1 > + ignore_loglevel > + console=ttyS0 > + earlycon=uart8250,mmio,0x10000000) > + > + qemu-system-riscv64 \ > + -M virt,pflash0=pflash0,pflash1=pflash1,acpi=off \ > + -m 4096 -smp 2 \ > + -serial mon:stdio \ > + -device virtio-gpu-pci -full-screen \ > + -device qemu-xhci \ > + -device usb-kbd \ > + -device virtio-rng-pci \ > + -blockdev node-name=pflash0,driver=file,read-only=on,filename=RISCV_VIRT_CODE.fd \ > + -blockdev node-name=pflash1,driver=file,filename=RISCV_VIRT_VARS.fd \ > + -netdev user,id=net0 \ > + -device virtio-net-pci,netdev=net0 \ > + -device virtio-blk-device,drive=hd0 \ > + -drive file=openSUSE-Tumbleweed-RISC-V-E20-efi.riscv64.raw,format=raw,id=hd0 \ > + -kernel Image-6.5.2-1-default \ > + -initrd initrd-6.5.2-1-default \ > + -append "${CMDLINE[*]}" > + > ## Test with your own OpenSBI binary > -Using the above QEMU command line, **RISCV_VIRT_CODE.fd** is launched by the > +Using the above QEMU command lines, **RISCV_VIRT_CODE.fd** is launched by the > OpenSBI binary that is bundled with QEMU. You can build your own OpenSBI binary > as well: > Reviewed-by: Andrew Jones -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#108639): https://edk2.groups.io/g/devel/message/108639 Mute This Topic: https://groups.io/mt/101334266/7686176 Group Owner: devel+owner@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io] -=-=-=-=-=-=-=-=-=-=-=-