[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 11 Nov 2021 08:14:11 +0000
From: "Wang, Wei W" <wei.w.wang@...el.com>
To: Stefano Garzarella <sgarzare@...hat.com>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
Stefan Hajnoczi <stefanha@...hat.com>,
"mst@...hat.com" <mst@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
"kys@...rosoft.com" <kys@...rosoft.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"Yamahata, Isaku" <isaku.yamahata@...el.com>,
"Nakajima, Jun" <jun.nakajima@...el.com>,
"Kleen, Andi" <andi.kleen@...el.com>,
Andra Paraschiv <andraprs@...zon.com>,
"Sergio Lopez Pascual" <slp@...hat.com>
Subject: RE: [RFC] hypercall-vsock: add a new vsock transport
On Wednesday, November 10, 2021 7:17 PM, Stefano Garzarella wrote:
> Adding Andra and Sergio, because IIRC Firecracker and libkrun emulates
> virtio-vsock with virtio-mmio so the implementation should be simple and also
> not directly tied to a specific VMM.
>
OK. This would be OK for KVM based guests.
For Hyperv and VMWare based guests, they don't have virtio-mmio support.
If the MigTD (a special guest) we provide is based on virtio-mmio, it would not be usable to them.
Thanks,
Wei
Powered by blists - more mailing lists