External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-12-22 05:35:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

vmm: memory_manager: don't set backing_file for virtio_mem regions

Browse Source 
The memory region that is associated with the hotpluggable part of
a virtio-mem zone isn't backed by the file specified in the
MemoryZoneConfig. The file is used only for the fixed part of the
zone. When you try to restore a snapshot with virtio-mem, the
backing file is used for all its regions. This results in the
following error:

  VmRestore(MemoryManager(GuestMemoryRegion(MappingPastEof)))

This patch sets backing_file only for the fixed part of a virtio-mem
zone.

Fixes: #6337

Signed-off-by: Alexandru Matei <alexandru.matei@uipath.com>
This commit is contained in:
Alexandru Matei 2024-03-28 14:58:10 +02:00
parent d3e4f9cc1b
commit 79c69801b4
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
vmm/src/memory_manager.rs
View File

@ -671,7 +671,11 @@ impl MemoryManager {
for zone_config in zones_config { for zone_config in zones_config {
if guest_ram_mapping.zone_id == zone_config.id { if guest_ram_mapping.zone_id == zone_config.id {
let region = MemoryManager::create_ram_region( let region = MemoryManager::create_ram_region(
&zone_config.file, if guest_ram_mapping.virtio_mem {
&None
} else {
&zone_config.file
},
guest_ram_mapping.file_offset, guest_ram_mapping.file_offset,
GuestAddress(guest_ram_mapping.gpa), GuestAddress(guest_ram_mapping.gpa),
guest_ram_mapping.size as usize, guest_ram_mapping.size as usize,