Return-Path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 06990986321 for ; Mon, 17 Oct 2022 09:19:30 +0000 (UTC) From: "zouqian (D)" Date: Mon, 17 Oct 2022 09:19:24 +0000 Message-ID: <2ce711eafa994d7281bb8ae9cc7dfcc0@huawei.com> MIME-Version: 1.0 Subject: [virtio-comment] [Resend] about reserving virtio device ID for QingTian Box (virtio-qtbox) devices Content-Language: zh-CN Content-Type: multipart/alternative; boundary="_000_2ce711eafa994d7281bb8ae9cc7dfcc0huaweicom_" To: "Michael S. Tsirkin" , Cornelia Huck Cc: "virtio-comment@lists.oasis-open.org" , "Gonglei (Arei)" , "Longpeng (Mike, Cloud Infrastructure Service Product Dept.)" List-ID: --_000_2ce711eafa994d7281bb8ae9cc7dfcc0huaweicom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Huawei Cloud is one of the famous public cloud providers, and its hyperviso= r is named QingTian. We plan to support the QingTian Box (virtio-qtbox) tha= t provides some guest-aware features ( for high performance, security, etc.= ) in the future, and at least one of them is already in development. The d= ata transmission is based on the Virtio, so we want to reserve a device id = ( 43 ) for the virtio-qtbox. virtio-qtbox can help user carve out some resources (e.g. vcpu, mem, pci_de= v) from the VM and then use these resources to start a sandbox for the user= . The usage quite likes the software enclave which Nitro already supported,= but we have much wider usage, for example, running unikernel + app (e.g. O= SV + Redis) in the sandbox, it would provide much better performance than t= he traditional os. Since virtio-qtbox is developed for virtualization scenarios to isolate res= ources, it supports live migration and crashes recovery. virtio-qtbox lower= s the technical threshold for implementing resource isolation in VMs and he= lps users have a more efficient and secure development platform based on cl= oud services. Any comments will be appreciated. issue: https://github.com/oasis-tcs/virtio-spec/issues/127 mail-list: https://lists.oasis-open.org/archives/virtio-comment/202112/msg0= 0030.html https://lists.oasis-open.org/archives/virtio-comment/202112/msg00047.html --_000_2ce711eafa994d7281bb8ae9cc7dfcc0huaweicom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Huawei Cloud = is one of the famous public cloud providers, and its hypervisor is named Qi= ngTian. We plan to support the QingTian Box (virtio-qtbox) that provides some guest-aware features ( for high performance, security, = etc. ) in the future, and at least one of them is already in development. T= he data transmission is based on the Virtio, so we want to reserve a device= id ( 43 ) for the virtio-qtbox.

 

virtio-qtbox = can help user carve out some resources (e.g. vcpu, mem, pci_dev) from the V= M and then use these resources to start a sandbox for the user. The usage quite likes the software enclave which Nitro alrea= dy supported, but we have much wider usage, for example, running unikernel = + app (e.g. OSV + Redis) in the sandbox, it would provide much bett= er performance than the traditional os.

 

Since virtio-= qtbox is developed for virtualization scenarios to isolate resources, it su= pports live migration and crashes recovery. virtio-qtbox lowers the technical threshold for implementing resource isolation in VMs = and helps users have a more efficient and secure development platform based= on cloud services.

 

Any comments = will be appreciated.

 

issue: https://git= hub.com/oasis-tcs/virtio-spec/issues/127

mail-list: https://lists.oasis-open.org/archives/virtio-comment/202112/msg00030.html

ht= tps://lists.oasis-open.org/archives/virtio-comment/202112/msg00047.html=

 

--_000_2ce711eafa994d7281bb8ae9cc7dfcc0huaweicom_--