Bug 453488 - can't reuse guest name without restarting virt-manager
can't reuse guest name without restarting virt-manager
Product: Fedora
Classification: Fedora
Component: virt-manager (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Berrange
Fedora Extras Quality Assurance
: 453009 (view as bug list)
Depends On:
Blocks: F10Target
  Show dependency treegraph
Reported: 2008-06-30 20:06 EDT by Jens Petersen
Modified: 2009-04-03 06:35 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-04-03 06:35:24 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 Jens Petersen 2008-06-30 20:06:27 EDT
Description of problem:
If I install a guest under virt-manager and then delete it and install another
guest under the same name in virt-manager: the console for the new guest refuses
to appear.  Workaround is to quit virt-manager and start it again and voila.

How reproducible:
every time

Steps to Reproduce:
1. install a guest OS (call it "rawhide1")
2. later delete rawhide1 from virt-manager
3. try to reinstall "rawhide1" as a new guest
Actual results:
3. Press Finish in install setup does not bring up console window for rawhide1
 (I think it flashes up and then disappears.)  Pressing Finish again and a message
  appears saying it is already running.

Expected results:
3. new console to appear normally

Additional info:
It is annoying having to restart virt-manager for this.
Comment 1 Cole Robinson 2008-12-01 14:44:37 EST
*** Bug 453009 has been marked as a duplicate of this bug. ***
Comment 2 Jens Petersen 2009-04-01 02:13:36 EDT
I think this may be fixed in 0.6.1 or earlier.
Comment 3 Mark McLoughlin 2009-04-03 06:35:24 EDT
Okay, this was filed against F9, but since it's fixed in rawhide and easy to work around, I'm closing the bug. Thanks Jens.

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