[virt-manager PATCH] man: fix default value for filesystem accessmode option
Commit 85307b9bd2971cfc972c976c78e411f018647861 changed the default value for 'accessmode' from 'passthrough' to 'mapped', but forgot to update the documentation in the man page. Signed-off-by: Jonathon Jongsma --- man/virt-install.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man/virt-install.rst b/man/virt-install.rst index 85070314..d70c37ca 100644 --- a/man/virt-install.rst +++ b/man/virt-install.rst @@ -1202,7 +1202,7 @@ Some example suboptions: ``accessmode`` or ``mode`` The access mode for the source directory from the guest OS. Only used with -QEMU and type=mount. Valid modes are 'passthrough' (the default), 'mapped', +QEMU and type=mount. Valid modes are 'mapped' (the default), 'passthrough', or 'squash'. See libvirt domain XML documentation for more info. ``source`` -- 2.34.1
[virt-manager][PATCH] Update domain title/description on corresponding event
If a domain is edited outside of virt-manager (e.g. via virsh edit) then this is reflected in the GUI (in the domain HW details tab). However, if domain title or description is updated outside of virt-manager (virsh desc) then this change is not reflected. This is simply because the corresponding event emitted by libvirt is not listened to. Signed-off-by: Michal Privoznik --- virtManager/connection.py | 1 + 1 file changed, 1 insertion(+) diff --git a/virtManager/connection.py b/virtManager/connection.py index 68a37ea6..6585fef6 100644 --- a/virtManager/connection.py +++ b/virtManager/connection.py @@ -765,6 +765,7 @@ class vmmConnection(vmmGObject): _add_domain_xml_event("VIR_DOMAIN_EVENT_ID_DEVICE_ADDED", 19) _add_domain_xml_event("VIR_DOMAIN_EVENT_ID_AGENT_LIFECYCLE", 18, self._domain_agent_lifecycle_event) +_add_domain_xml_event("VIR_DOMAIN_EVENT_ID_METADATA_CHANGE", 23) try: _check_events_disabled() -- 2.34.1