> On Wed, May 12, 2021 at 04:01:26PM +, Douglas, William wrote:
>> On Tue, May 11, 2021 at 02:05AM, Daniel P. Berrangé wrote:
>> > On Tue, Apr 27, 2021 at 02:39:46PM -0700, William Douglas wrote:
>> >> diff --git a/meson.build b/meson.build
>> >> index 951da67896..8c33efb25c 100644
>> >> --- a/
On Wed, May 12, 2021 at 04:01:26PM +, Douglas, William wrote:
> On Tue, May 11, 2021 at 02:05AM, Daniel P. Berrangé wrote:
> > On Tue, Apr 27, 2021 at 02:39:46PM -0700, William Douglas wrote:
> >> diff --git a/meson.build b/meson.build
> >> index 951da67896..8c33efb25c 100644
> >> --- a/meson.b
On Tue, May 11, 2021 at 02:05AM, Daniel P. Berrangé wrote:
> On Tue, Apr 27, 2021 at 02:39:46PM -0700, William Douglas wrote:
>> * On a 64-bit host Cloud-Hypervisor needs to support PVH and so can
>> emulate 32-bit mode but it isn't fully tested (a 64-bit kernel and
>> 32-bit userspace is fine,
On Tue, Apr 27, 2021 at 02:39:46PM -0700, William Douglas wrote:
> Cloud-Hypervisor is a KVM virtualization using hypervisor. It
> functions similarly to qemu and the libvirt Cloud-Hypervisor driver
> uses a very similar structure to the libvirt driver.
>
> The biggest difference from the libvirt
Cloud-Hypervisor is a KVM virtualization using hypervisor. It
functions similarly to qemu and the libvirt Cloud-Hypervisor driver
uses a very similar structure to the libvirt driver.
The biggest difference from the libvirt perspective is that the
"monitor" socket is seperated into two sockets one
