You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried creating SEV-SNP VMs with kernel 6.11, qemu 9.2 and libvirt 10.5.0. The memory set by libvirt is 4GB, but the memory consumed by the VM is about 7GB. I used the pmap to see the memory consumed by qemu process and found out that the allocated memory is 4911700(KB) and the RSS is 494956(KB). So I want to know is it normal that about 3GB memory is consumed by the system when I started the SEV-SNP VM and the how to estimate the memory consumption for each SEV-SNP VM. By the way, all the consumed memory is in buff/cache area. THX
Add. We found that the unused pages of VMs are set as public when the system boots, so most of the pages are public. That makes the openVSwitch process allocates more memory when the openVSwitch tries to access the private pages. According to the document, that is the lazy mode of memory validation, which I thought has not been introduced to the current vision of SEV-SNP. So I want to confirm that whether the lazy validation mode has been merged into kernel and qemu and is set as the
default validation mode.
The text was updated successfully, but these errors were encountered:
I tried creating SEV-SNP VMs with kernel 6.11, qemu 9.2 and libvirt 10.5.0. The memory set by libvirt is 4GB, but the memory consumed by the VM is about 7GB. I used the pmap to see the memory consumed by qemu process and found out that the allocated memory is 4911700(KB) and the RSS is 494956(KB). So I want to know is it normal that about 3GB memory is consumed by the system when I started the SEV-SNP VM and the how to estimate the memory consumption for each SEV-SNP VM. By the way, all the consumed memory is in buff/cache area. THX
Add. We found that the unused pages of VMs are set as public when the system boots, so most of the pages are public. That makes the openVSwitch process allocates more memory when the openVSwitch tries to access the private pages. According to the document, that is the lazy mode of memory validation, which I thought has not been introduced to the current vision of SEV-SNP. So I want to confirm that whether the lazy validation mode has been merged into kernel and qemu and is set as the
default validation mode.
The text was updated successfully, but these errors were encountered: