Bug 506263 - Attempting to display a remote VM being viewed by another user hangs virt-manager
Attempting to display a remote VM being viewed by another user hangs virt-man...
Product: Virtualization Tools
Classification: Community
Component: virt-manager (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Cole Robinson
Depends On:
  Show dependency treegraph
Reported: 2009-06-16 09:45 EDT by Stephen Gallagher
Modified: 2010-05-05 16:25 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-05 16:25:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stephen Gallagher 2009-06-16 09:45:33 EDT
Description of problem:
Connecting to a remote libvirtd with virt-manager and attempting to view the console of a running VM being viewed already by another user causes virt-manager to hang until it is forcibly killed.

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Create a VM on a remote libvirt instance. Start that VM.
2. From one machine, remotely connect to that libvirt instance and view the VM. This should work as expected.
3. From a second machine, while the first machine is still viewing the VM, attempt to remotely connect and view that same VM. This will lock up virt-manager.
Actual results:
virt-manager is locked and must be killed to proceed.

Expected results:
Either the second client should receive a notice that the VM is currently being viewed and is inaccessible, or the second client should be able to also view the VM.

Additional info:
Comment 1 Cole Robinson 2010-05-05 16:25:39 EDT
Hmm, seems to work fine here on F12. This bug is pretty old and I haven't heard other similar complaints, so maybe it's no longer an issue. Closing as WORKSFORME, but if you can reproduce with a current fedora version, please reopen and assign to the correct product so we can follow up from there.

Note You need to log in before you can comment on or make changes to this bug.