Peng Tao 6c03e2a265 factory: make vm templating work with vosck ...

As virtio v1.1 spec states:
The guest_cid configuration field MUST be fetched to determine the current CID when a VIRTIO_VSOCK_EVENT_TRANSPORT_RESET event is received.
Existing connections MUST be shut down when a VIRTIO_VSOCK_EVENT_TRANSPORT_RESET event is received.
Listen connections MUST remain operational with the current CID when a VIRTIO_VSOCK_EVENT_TRANSPORT_RESET event is received.

We should be able to use vm templating together with vsock easily, as
qemu already sends VIRTIO_VSOCK_EVENT_TRANSPORT_RESET event to guest.

Fixes: #1773
Signed-off-by: Peng Tao <bergwolf@hyper.sh>

2019-06-06 02:19:42 -07:00

..

base

factory: Make factory status can show status of VMCache server

2019-04-10 11:03:14 +08:00

cache

cache: Call vm.Disconnect() when close vm

2019-05-23 12:29:55 +08:00

direct

factory: Make factory status can show status of VMCache server

2019-04-10 11:03:14 +08:00

grpccache

factory: Make factory status can show status of VMCache server

2019-04-10 11:03:14 +08:00

template

factory: make vm templating work with vosck

2019-06-06 02:19:42 -07:00

factory_test.go

factory: Add new factory option template_path

2019-04-19 11:31:18 +08:00

factory.go

factory: make vm templating work with vosck

2019-06-06 02:19:42 -07:00