Bug 1813667
Summary: | shutdown of a VM system takes 90 seconds longer due to spice-vdagentd.service | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ed Greshko <ed.greshko> | ||||
Component: | spice-vdagent | Assignee: | Christophe Fergeau <cfergeau> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 32 | CC: | alon, awilliam, bugzilla, cfergeau, hdegoede, kparal, marcandre.lureau, mcrha, sandmann, victortoso, y9t7sypezp | ||||
Target Milestone: | --- | Keywords: | CommonBugs | ||||
Target Release: | --- | Flags: | kparal:
fedora_prioritized_bug?
|
||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | https://fedoraproject.org/wiki/Common_F32_bugs#vm-vdagent-shutdown | ||||||
Fixed In Version: | spice-vdagent-0.20.0-2.fc32 spice-vdagent-0.20.0-2.fc31 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-03-28 00:15:25 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1705306 | ||||||
Attachments: |
|
Description
Ed Greshko
2020-03-15 10:59:22 UTC
I should have also added that the qemu/kvm VM is running on an F31 system. Simply booting and then shutting down the VM with the newer version of spice-vdagent will demonstrate the problem. I can confirm this with a clean install of F32 Beta Workstation into a libvirt VM. Every system shutdown is delayed by 90 seconds due to spice-vdagent (see screenshot). It's not just during system shutdown, each stopping of the service takes 90 seconds (times out). Also "dnf downgrade spice-vdagent" takes +90 seconds. $ sudo systemctl status spice-vdagentd ● spice-vdagentd.service - Agent daemon for Spice guests Loaded: loaded (/usr/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: enabled) Active: active (running) since Mon 2020-03-16 17:00:11 CET; 30s ago TriggeredBy: ● spice-vdagentd.socket Process: 1123 ExecStart=/usr/sbin/spice-vdagentd $SPICE_VDAGENTD_EXTRA_ARGS (code=exited, status=0/SUCCESS) Main PID: 1131 (spice-vdagentd) Tasks: 1 (limit: 3451) Memory: 1.1M CPU: 21ms CGroup: /system.slice/spice-vdagentd.service └─1131 /usr/sbin/spice-vdagentd Mar 16 17:00:11 f32 systemd[1]: Starting Agent daemon for Spice guests... Mar 16 17:00:11 f32 systemd[1]: Started Agent daemon for Spice guests. Mar 16 17:00:13 f32 spice-vdagentd[1131]: opening vdagent virtio channel Mar 16 17:00:13 f32 spice-vdagentd[1131]: Set max clipboard: 104857600 Mar 16 17:00:13 f32 spice-vdagentd[1131]: Set max clipboard: 104857600 $ time sudo systemctl stop spice-vdagentd Warning: Stopping spice-vdagentd.service, but it can still be activated by: spice-vdagentd.socket real 1m30.218s user 0m0.021s sys 0m0.019s $ time sudo systemctl start spice-vdagentd real 0m1.565s user 0m0.041s sys 0m0.041s $ sudo systemctl status spice-vdagentd ● spice-vdagentd.service - Agent daemon for Spice guests Loaded: loaded (/usr/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: enabled) Active: active (running) since Mon 2020-03-16 17:02:19 CET; 16min ago TriggeredBy: ● spice-vdagentd.socket Process: 1747 ExecStart=/usr/sbin/spice-vdagentd $SPICE_VDAGENTD_EXTRA_ARGS (code=exited, status=0/SUCCESS) Main PID: 1751 (spice-vdagentd) Tasks: 1 (limit: 3451) Memory: 964.0K CPU: 16ms CGroup: /system.slice/spice-vdagentd.service └─1751 /usr/sbin/spice-vdagentd Mar 16 17:02:19 f32 systemd[1]: Starting Agent daemon for Spice guests... Mar 16 17:02:19 f32 systemd[1]: Started Agent daemon for Spice guests. Mar 16 17:02:19 f32 spice-vdagentd[1751]: opening vdagent virtio channel Mar 16 17:02:19 f32 spice-vdagentd[1751]: Set max clipboard: 104857600 Mar 16 17:02:19 f32 spice-vdagentd[1751]: Set max clipboard: 104857600 [kparal@f32 ~]$ sudo systemctl status spice-vdagentd ● spice-vdagentd.service - Agent daemon for Spice guests Loaded: loaded (/usr/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: enabled) Active: active (running) since Mon 2020-03-16 17:00:11 CET; 30s ago TriggeredBy: ● spice-vdagentd.socket Process: 1123 ExecStart=/usr/sbin/spice-vdagentd $SPICE_VDAGENTD_EXTRA_ARGS (code=exited, status=0/SUCCESS) Main PID: 1131 (spice-vdagentd) Tasks: 1 (limit: 3451) Memory: 1.1M CPU: 21ms CGroup: /system.slice/spice-vdagentd.service └─1131 /usr/sbin/spice-vdagentd Mar 16 17:00:11 f32 systemd[1]: Starting Agent daemon for Spice guests... Mar 16 17:00:11 f32 systemd[1]: Started Agent daemon for Spice guests. Mar 16 17:00:13 f32 spice-vdagentd[1131]: opening vdagent virtio channel Mar 16 17:00:13 f32 spice-vdagentd[1131]: Set max clipboard: 104857600 Mar 16 17:00:13 f32 spice-vdagentd[1131]: Set max clipboard: 104857600 [kparal@f32 ~]$ time sudo systemctl stop spice-vdagentd Warning: Stopping spice-vdagentd.service, but it can still be activated by: spice-vdagentd.socket real 1m30.218s user 0m0.021s sys 0m0.019s [kparal@f32 ~]$ time sudo systemctl start spice-vdagentd [sudo] password for kparal: real 0m1.565s user 0m0.041s sys 0m0.041s [kparal@f32 ~]$ time sudo systemctl status spice-vdagentd ● spice-vdagentd.service - Agent daemon for Spice guests Loaded: loaded (/usr/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: enabled) Active: active (running) since Mon 2020-03-16 17:02:19 CET; 16min ago TriggeredBy: ● spice-vdagentd.socket Process: 1747 ExecStart=/usr/sbin/spice-vdagentd $SPICE_VDAGENTD_EXTRA_ARGS (code=exited, status=0/SUCCESS) Main PID: 1751 (spice-vdagentd) Tasks: 1 (limit: 3451) Memory: 964.0K CPU: 16ms CGroup: /system.slice/spice-vdagentd.service └─1751 /usr/sbin/spice-vdagentd Mar 16 17:02:19 f32 systemd[1]: Starting Agent daemon for Spice guests... Mar 16 17:02:19 f32 systemd[1]: Started Agent daemon for Spice guests. Mar 16 17:02:19 f32 spice-vdagentd[1751]: opening vdagent virtio channel Mar 16 17:02:19 f32 spice-vdagentd[1751]: Set max clipboard: 104857600 Mar 16 17:02:19 f32 spice-vdagentd[1751]: Set max clipboard: 104857600 $ time sudo systemctl stop spice-vdagentd Warning: Stopping spice-vdagentd.service, but it can still be activated by: spice-vdagentd.socket real 1m30.207s user 0m0.020s sys 0m0.019s It doesn't happen with spice-vdagent-0.19.0-5.fc32.x86_64 inside the VM. F32 host: qemu-ui-spice-app-4.2.0-5.fc32.x86_64 spice-glib-0.37-6.fc32.x86_64 spice-gtk3-0.37-6.fc32.x86_64 spice-server-0.14.3-1.fc32.x86_64 spice-vdagent-0.20.0-1.fc32.x86_64 F32 guest: qemu-ui-spice-app-4.2.0-5.fc32.x86_64 spice-glib-0.37-6.fc32.x86_64 spice-gtk3-0.37-6.fc32.x86_64 spice-server-0.14.3-1.fc32.x86_64 spice-vdagent-0.20.0-1.fc32.x86_64 Eh, the terminal log got copied twice over and intermingled (sorry), but you get the gist. Starting the service is immediate, no problem is reported, but shutting it down takes 90 seconds. Created attachment 1670611 [details]
system shutdown screenshot
Yep, I'm seeing this in virt-manager VM's as well. Not on baremetal. We've failed to stop https://bodhi.fedoraproject.org/updates/FEDORA-2020-6ff500948d from reaching stable updates :-/ Proposing as a Prioritized Bug. This is a very bad experience for anyone using F32 in VMs. Christophe, any chance you can look into this soon, or revert to the previous version? As a workaround, you can install the previous version. Unfortunately, it is not in an F32 repo, so: $ dnf repoquery spice-vdagent --releasever=31 --location $ wget http://path.to.mirror # dnf downgrade spice-vdagent-0.19.0-4.fc31.x86_64.rpm NB: dnf will appear to stall while systemctl attempts to kill the running spice-vdagentd. You can "watch" from another terminal tab: $ ps -ef | grep spice Tested in an F32 VM. Thanks for the report, we are working on a fix for this upstream: issue: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/18 current merge request: https://gitlab.freedesktop.org/spice/linux/vd_agent/-/merge_requests/7 As soon as a fix is merged, I'll make new builds. *** Bug 1814758 has been marked as a duplicate of this bug. *** Awesome, thanks Victor. It would be great if you could make it before the final version of Fedora 32, so that the problem is not embedded in F32 Live images forever. Nominating for a freeze exception. FEDORA-2020-45698e4ed9 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-45698e4ed9 Fix Verified and Karma Given (In reply to Fedora Update System from comment #12) > FEDORA-2020-45698e4ed9 has been submitted as an update to Fedora 32. > https://bodhi.fedoraproject.org/updates/FEDORA-2020-45698e4ed9 Awesome, thank you. The service now exits properly. FEDORA-2020-45698e4ed9 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-45698e4ed9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-45698e4ed9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-8c234611fd has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8c234611fd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8c234611fd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-45698e4ed9 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-8c234611fd has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. |