mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2024-10-27 23:23:09 +00:00
475040b29e
Upon a virtio reset, the driver expects that available and used indexes will be reset to 0. That's why we need to reset these values from the VMM for any virtio device that might get reset. This issue was not detected before because the Vec<Queue> maintained through VirtioPciDevice or MmioDevice was never updated from the virtio device thread after the device had been actived. For this reason, upon reset, both available and used indexes were already at the value 0. The issue arose when trying to reset a device after the VM was restored. That's because during the restore, each queue is assigned with the right available and used indexes before it is passed to the device through the activate function. And that's why upon reset, each queue was still assigned with these indexes while it should have been reset to 0. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> |
||
|---|---|---|
| .. | ||
| transport | ||
| vhost_user | ||
| vsock | ||
| block.rs | ||
| console.rs | ||
| device.rs | ||
| iommu.rs | ||
| lib.rs | ||
| mem.rs | ||
| net_util.rs | ||
| net.rs | ||
| pmem.rs | ||
| queue.rs | ||
| rng.rs | ||