Bug 513958
| Summary: | VM disappears from virt-manager at end of installation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Sachin Prabhu <sprabhu> |
| Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
| Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.4 | CC: | clalance, jdenemar, lwang, xen-maint |
| Target Milestone: | rc | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-10-19 16:03:46 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sachin Prabhu
2009-07-27 10:17:20 UTC
I'm pretty sure this isn't a regression. This has always been the case with virt-manager, as far as I know. That is, at the end of installation, it just destroys the guest, and it's up to the user to start it manually. Note that the behavior for virt-install is different; virt-install *does* reboot guests at the end of installation. It's an unfortunate inconsistency in our tools, but since some people might be relying on the current behavior, we can't change it now. Can you please re-try with virt-manager from RHEL-5.3, and confirm that at the end of installation the behavior is the same as in RHEL-5.4? Chris Lalancette No matter if this is a regression or not, it's not a xen issue, since virt-manager sets 'on_reboot = destroy' for the guest being installed. And xend does what it's asked for and destroys the guest when it reboots. Changing component to virt-manager. On RHEL5.3, I confirmed that virt-manager keeps a guest on the list with 'Shutoff' state after the shutdown at the end of installation. However, on RHEL5.4, a guest disappears from the list on virt-manager after the installation and we can not reboot it with virt-manager. To show the guest on the virt-manager's list again, we have to re-connect to xen on the virt-manager. So I beleive this is a regression and it is too inconvenient for users to install guests with virt-manager. There is already a libvirt bug tracking the 'disappear after force-off issue'. Closing as DUP, please reopen if this is actually a separate issue. *** This bug has been marked as a duplicate of bug 508278 *** I'm not sure the root cause is same as bz508278, but this problem looks different so far because bz508278 reports that the problem occurs in RHEL5.3 as well. As far as my test, RHEL5.3 does NOT have this bz513958 problem at all. (In reply to comment #9) > I'm not sure the root cause is same as bz508278, but this problem looks > different so far because bz508278 reports that the problem occurs in RHEL5.3 as > well. As far as my test, RHEL5.3 does NOT have this bz513958 problem at all. Well, some of the comments in 508278 seem to suggest that it only happens under certain circumstances. So maybe your test method is one of those circumstances. In any case, please test the patch that we now have for 508278. If that doesn't fix it for you, please re-open this BZ. Chris Lalancette Fujtsu reported that the patch for bz508278 doesn't fix this problem. I also double-checked it with the patch and RHEL5.4 snapshot5, and the problem still occurs. There was activity, and another patch added to 508278 that specifically fixed the issue when using virt-manager. So closing as a dup (again :) ). If the issue is still present in 5.4, please open a separate bug report since this bug has become difficult to navigate. Please provide a clear indication of how to reproduce, the behavior you are seeing, and expected (correct) behavior. *** This bug has been marked as a duplicate of bug 508278 *** |