---
title: "Add a new vsock device to the VM"
method: PUT
path: "/vm.add-vsock"
---

# Add a new vsock device to the VM

`PUT /vm.add-vsock`

## Request body

- VsockConfig
  - `cid` integer, required — Guest Vsock CID
  - `socket` string, required — Path to UNIX domain socket, used to proxy vsock connections.
  - `iommu` boolean
  - `pci_segment` integer
  - `id` string

## Response `200`

The new device was successfully added to the VM instance.

- PciDeviceInfo — Information about a PCI device
  - `id` string, required
  - `bdf` string, required

## Other responses

- `204` — The new device was successfully (cold) added to the VM instance.
- `500` — The new device could not be added to the VM instance.

## Changes

- **2022-02-24** `2f0e5d4cc0d8` — 1 info
  - added the success response with the status `204`
- **2021-12-02** `31ed30e1025b` — 1 info
  - added the new optional request property `pci_segment`
- **2020-08-10** `8330c1bec628` — 1 breaking, 1 info
  - removed the success response with the status `204`
  - added the success response with the status `200`
- **2020-06-30** `02cee76958f3` — 1 breaking, 1 warning
  - added the new required request property `socket`
  - removed the request property `sock`
- **2020-05-26** `84b3b343d31c` — 1 info
  - endpoint added

[Full history](https://skmtc.dev/kata-containers/apis/cloud-hypervisor-api/changes/vm.add-vsock/put.md)

---

[API](https://skmtc.dev/kata-containers/apis/cloud-hypervisor-api.md) · [All operations](https://skmtc.dev/kata-containers/apis/cloud-hypervisor-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/kata-containers/cloud-hypervisor-api/revisions/c30c01a9fb80/schema)