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.web12.4959.1645782215287187771 for ; Fri, 25 Feb 2022 01:43:35 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=XQ0xyJAK; 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=1645782214; 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=Qp8RdaMCjynb5gjGdM2KSdKjMOL9utsj/9vDCUCm5cw=; b=XQ0xyJAK24NbIynrCfxPE8INsJJl4WETh7NR6EW02dt6f39gNNs1A+X2Vl7VEKoXsR+Duc 8dvIXieMIranCgcWTYg9pshtS0GoZUYQF6p1ZERaUOKiLbl8zV2YL/RSZbce5dMjJsMGE2 rlJDOXtqrP1+QcRtJn8IU/dj4SNkCAs= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-336-RsEngowAO_2GriQHS4lh-A-1; Fri, 25 Feb 2022 04:43:30 -0500 X-MC-Unique: RsEngowAO_2GriQHS4lh-A-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id CDA73800425; Fri, 25 Feb 2022 09:43:29 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.195.81]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 925FB7FE84; Fri, 25 Feb 2022 09:43:29 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id DA4B718003BE; Fri, 25 Feb 2022 10:43:27 +0100 (CET) Date: Fri, 25 Feb 2022 10:43:27 +0100 From: "Gerd Hoffmann" To: sebastien.boeuf@intel.com Cc: devel@edk2.groups.io, jiewen.yao@intel.com, jordan.l.justen@intel.com Subject: Re: [PATCH v3 7/7] OvmfPkg: CloudHv: Add README Message-ID: <20220225094327.kddrna6g2bcpz3dk@sirius.home.kraxel.org> References: MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Feb 24, 2022 at 03:28:26PM +0100, sebastien.boeuf@intel.com wrote: > From: Sebastien Boeuf > > Add some documentation to the CloudHv target in order to clarify how to > use it and what to expect from it. > > Signed-off-by: Sebastien Boeuf > --- > OvmfPkg/CloudHv/README | 66 ++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 66 insertions(+) > create mode 100644 OvmfPkg/CloudHv/README > > diff --git a/OvmfPkg/CloudHv/README b/OvmfPkg/CloudHv/README > new file mode 100644 > index 0000000000..b5ef2a8be6 > --- /dev/null > +++ b/OvmfPkg/CloudHv/README > @@ -0,0 +1,66 @@ > + > +CloudHv is a port of OVMF for the Cloud Hypervisor project. > + > +The Cloud Hypervisor project > +---------------------------- > + > +Cloud Hypervisor is a Virtual Machine Monitor that runs on top of KVM. The > +project focuses on exclusively running modern, cloud workloads, on top of a > +limited set of hardware architectures and platforms. Cloud workloads refers to > +those that are usually run by customers inside a cloud provider. This means > +modern operating systems with most I/O handled by paravirtualised devices > +(i.e. virtio), no requirement for legacy devices, and 64-bit CPUs. > + > +https://github.com/cloud-hypervisor/cloud-hypervisor > + > +Design > +------ > + > +Based on Cloud Hypervisor's motto to reduce the emulation as much as possible, > +the project logically decided to support the PVH boot specification as the only > +way of booting virtual machines. That includes both direct kernel boot and OVMF > +firmware which must be generated as PVH ELF binaries. > +PVH allows information like location of ACPI tables and location of guest RAM > +ranges to be shared without the need of an extra emulated device like a CMOS. > + > +Features > +-------- > + > +* Serial console > +* EFI shell > +* virtio-pci > + > +Build > +----- > + > +The way to build the CloudHv target is as follows: > + > +OvmfPkg/build.sh -p OvmfPkg/CloudHv/CloudHvX64.dsc -a X64 -b DEBUG > + > +Usage > +----- > + > +Assuming Cloud Hypervisor is already built, one can start a virtual machine as > +follows: > + > +./cloud-hypervisor \ > + --cpus boot=1 \ > + --memory size=1G \ > + --kernel Build/CloudHvX64/DEBUG_GCC5/FV/CLOUDHV.fd \ > + --disk path=/path/to/disk.raw > + > +Releases > +-------- > + > +In edk2-stable202202, CloudHv is generated as data-only binary. > +Starting with edk2-stable202205, CloudHv is generated as a PVH ELF binary to > +reduce the amount of emulation needed from Cloud Hypervisor. > +For TDX, things are handled differently and PVH is not used, which is why the > +firmware is always generated as a data-only binary. > + > ++-------------------+----------------+-------------+ > +| CloudHv | non-TDX | TDX | > ++-------------------+----------------+-------------+ > +| edk2-stable202202 | Data binary | Data binary | > +| edk2-stable202205 | PVH ELF binary | Data binary | > ++-------------------+----------------+-------------+ Hmm, but current edk2 code has no support for tdx, correct? I'd suggest to drop the tdx references then. take care, Gerd