deploy: cb54c2d

Author: sboeuf

blog/cloud-hypervisor-v24.0-released/index.html

@@ -1,4 +1,5 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on</title><link>https://www.cloudhypervisor.org/blog/</link><description>Recent content in Blog on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Tue, 06 Oct 2020 08:49:55 +0000</lastBuildDate><atom:link href="https://www.cloudhypervisor.org/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Achieving Bare Metal Performance Within a Virtual Machine</title><link>https://www.cloudhypervisor.org/blog/achieving-bare-metal-performance-within-a-virtual-machine/</link><pubDate>Thu, 19 May 2022 08:00:00 +0000</pubDate><guid>https://www.cloudhypervisor.org/blog/achieving-bare-metal-performance-within-a-virtual-machine/</guid><description>There are use cases for which a workload needs to access specific hardware such as accelerators, GPU or network adapters to maximise potential performance. And since these workloads run inside virtual machines (VM) for security reasons, the challenge is to make this hardware available from within the VM, but without degrading the performance that can be achieved from bare metal.
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on</title><link>https://www.cloudhypervisor.org/blog/</link><description>Recent content in Blog on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><lastBuildDate>Tue, 06 Oct 2020 08:49:55 +0000</lastBuildDate><atom:link href="https://www.cloudhypervisor.org/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloud Hypervisor v24.0 Released!</title><link>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v24.0-released/</link><pubDate>Fri, 27 May 2022 08:00:00 +0000</pubDate><guid>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v24.0-released/</guid><description>This release has been tracked through the v24.0 project.
+Bypass Mode for virtio-iommu # virtio-iommu specification describes how a device can be attached by default to a bypass domain. This feature is particularly helpful for booting a VM with guest software which doesn&amp;rsquo;t support virtio-iommu but still need to access the device. Now that Cloud Hypervisor supports this feature, it can boot a VM with Rust Hypervisor Firmware or OVMF even if the virtio-block device exposing the disk image is placed behind a virtual IOMMU.</description></item><item><title>Achieving Bare Metal Performance Within a Virtual Machine</title><link>https://www.cloudhypervisor.org/blog/achieving-bare-metal-performance-within-a-virtual-machine/</link><pubDate>Thu, 19 May 2022 08:00:00 +0000</pubDate><guid>https://www.cloudhypervisor.org/blog/achieving-bare-metal-performance-within-a-virtual-machine/</guid><description>There are use cases for which a workload needs to access specific hardware such as accelerators, GPU or network adapters to maximise potential performance. And since these workloads run inside virtual machines (VM) for security reasons, the challenge is to make this hardware available from within the VM, but without degrading the performance that can be achieved from bare metal.
 VFIO, the Ideal Choice # This is a mature framework allowing a PCI device to be bound to the vfio-pci driver instead of the default driver it is usually attached to.</description></item><item><title>Cloud Hypervisor v23.1 Released!</title><link>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v23.1-released/</link><pubDate>Mon, 09 May 2022 14:24:16 +0000</pubDate><guid>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v23.1-released/</guid><description>This is a bug fix release. The following issues have been addressed:
 Add some missing seccomp rules Remove virtio-fs filesystem entries from config on removal Do not delete API socket on API server start (#4026) Reject virtio-mem resize if the guest doesn&amp;rsquo;t activate the device Fix OpenAPI naming of I/O throttling knobs Download # See the GitHub Release for the release assets.</description></item><item><title>Cloud Hypervisor v23.0 Released!</title><link>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v23.0-released/</link><pubDate>Thu, 14 Apr 2022 08:42:28 +0000</pubDate><guid>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v23.0-released/</guid><description>This release has been tracked through the v23.0 project.
 vDPA Support # A vDPA device has a datapath that complies with the virtio specification but with a vendor specific control path. The addition of --vdpa and the REST API equivalent allows the use of these devices with Cloud Hypervisor.
@@ -9,6 +10,4 @@ GDB Debug Stub Support # Cloud Hypervisor can now be used as debug target with G
 virtio-iommu Backed Segments # In order to facilitate hotplug devices that require being behind an IOMMU (e.g. QAT) there is a new option --platform iommu_segments=&amp;lt;list_of_segments&amp;gt; that will place all the specified segments behind the IOMMU.</description></item><item><title>Cloud Hypervisor v21.0 Released!</title><link>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v21.0-released/</link><pubDate>Thu, 20 Jan 2022 15:31:31 +0000</pubDate><guid>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v21.0-released/</guid><description>This release has been tracked through the v21.0 project.
 Efficient Local Live Migration (for Live Upgrade) # In order to support fast live upgrade of the VMM an optimised path has been added in which the memory for the VM is not compared from source to destination. This is activated by passing --local to the ch-remote send-migration command. This means that the live upgrade can complete in the order of 50ms vs 3s.</description></item><item><title>Cloud Hypervisor v20.2 Released!</title><link>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v20.2-released/</link><pubDate>Tue, 04 Jan 2022 17:57:10 +0000</pubDate><guid>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v20.2-released/</guid><description>This is a bug fix release. The following issues have been addressed:
 Don&amp;rsquo;t error out when setting up the SIGWINCH handler (for console resize) when this fails due to older kernel (#3456) Seccomp rules were refined to remove syscalls that are now unused Fix reboot on older host kernels when SIGWINCH handler was not initialised (#3496) Fix virtio-vsock blocking issue (#3497) Download # See the GitHub Release for the release assets.</description></item><item><title>Cloud Hypervisor v20.1 Released!</title><link>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v20.1-released/</link><pubDate>Mon, 13 Dec 2021 15:06:54 +0000</pubDate><guid>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v20.1-released/</guid><description>This is a bug fix release. The following issues have been addressed:
-Networking performance regression with virtio-net (#3450) Limit file descriptors sent in vfio-user support (#3401) Fully advertise PCI MMIO config regions in ACPI tables (#3432) Set the TSS and KVM identity maps so they don&amp;rsquo;t overlap with firmware RAM Correctly update the DeviceTree on restore Download # See the GitHub Release for the release assets.</description></item><item><title>Cloud Hypervisor v20.0 Released!</title><link>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v20.0-released/</link><pubDate>Thu, 02 Dec 2021 16:15:22 +0000</pubDate><guid>https://www.cloudhypervisor.org/blog/cloud-hypervisor-v20.0-released/</guid><description>v20.0 # This release has been tracked through the v20.0 project.
-Multiple PCI segments support # Cloud Hypervisor is no longer limited to 31 PCI devices. For both x86_64 and aarch64 architectures, it is now possible to create up to 16 PCI segments, increasing the total amount of supported PCI devices to 496.
-CPU pinning # For each vCPU, the user can define a limited set of host CPUs on which it is allowed to run.</description></item></channel></rss>
+Networking performance regression with virtio-net (#3450) Limit file descriptors sent in vfio-user support (#3401) Fully advertise PCI MMIO config regions in ACPI tables (#3432) Set the TSS and KVM identity maps so they don&amp;rsquo;t overlap with firmware RAM Correctly update the DeviceTree on restore Download # See the GitHub Release for the release assets.</description></item></channel></rss>