mirror of
https://github.com/virt-manager/virt-manager.git
synced 2024-12-31 17:17:56 +03:00
b4189a925b
The virtiofs in domcapabilities is used as a proxy to tell us whether libvirt is new enough to allow bare memory access mode=shared', So We enable/disable this checkbox according to it. When we configure shared memory access, If the 'memfd' is available in domcaps, We configure VM to use it as memory backend because it doesn't need addtional host setup for vhost-user devices, Otherwise use 'file' as backend. If all of numa nodes explicitly defined memAccess=shared, We mark this checkbox as checked even if virtiofs isn't exposed in domcapabilities. In this case: - It doesn't matter what the value of access mode of memoryBacking is because access mode of memoryBacking will be overridden per numa node by memAccess attribute. - Although the checkbox is disabled, the checked checkbox presents actual status about shared memory access to users. Signed-off-by: Lin Ma <lma@suse.com> |
||
|---|---|---|
| .. | ||
| about.ui | ||
| addhardware.ui | ||
| addstorage.ui | ||
| asyncjob.ui | ||
| clone.ui | ||
| connectauth.ui | ||
| console.ui | ||
| createconn.ui | ||
| createnet.ui | ||
| createpool.ui | ||
| createvm.ui | ||
| createvol.ui | ||
| delete.ui | ||
| details.ui | ||
| fsdetails.ui | ||
| gfxdetails.ui | ||
| host.ui | ||
| hostnets.ui | ||
| hoststorage.ui | ||
| manager.ui | ||
| migrate.ui | ||
| netlist.ui | ||
| oslist.ui | ||
| preferences.ui | ||
| snapshots.ui | ||
| snapshotsnew.ui | ||
| storagebrowse.ui | ||
| vmwindow.ui | ||
| vsockdetails.ui | ||
| xmleditor.ui | ||