Bug 1252201

Summary:	Feature Request: Allow virt-manager connection until libvirt-guests has shut down guests
Product:	[Community] Virtualization Tools	Reporter:	jamespharvey20
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED CANTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	crobinso, dyuan, rbalakri, tzheng, zhwang
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-10 21:41:11 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:

Description jamespharvey20 2015-08-11 00:51:07 UTC

If I'm on my own system running virt-manager, remotely connected via QEMU/KVM/ssh/openbsd-netcat to a server running KVM/libvirt/QEMU, and I run "systemd reboot/poweroff" on that server, my client socket to the server immediately closes.

Makes sense, unless libvirt-guests is gracefully shutting down guests.  In that case, it would be nice to delay shutting down the client socket until all the guests were shut down, so I could watch the vm shutdown process through the virtual console.

Comment 1 Cole Robinson 2016-04-10 21:41:11 UTC

I think the problem is that when you trigger the host shutdown, systemd shuts off the ssh daemon fairly soon, which is what kills your virt-manager connection. Libvirtd is still running, since it needs to be running for libvirt-guests service to work. So I don't think this is anything that can be fixed on the libvirt side