Bug 1402196 - There is no info "guest in not running" after forcing off the guest which has no display but reserve the serial device on rhel6.9
Summary: There is no info "guest in not running" after forcing off the guest which has...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.9
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 02:47 UTC by mxie@redhat.com
Modified: 2017-12-06 10:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:42:01 UTC
Target Upstream Version:


Attachments (Terms of Use)
screenshot (35.65 KB, image/png)
2016-12-07 02:47 UTC, mxie@redhat.com
no flags Details
virt-manager-debug.log (7.84 KB, text/plain)
2016-12-07 02:48 UTC, mxie@redhat.com
no flags Details
lxc (19.41 KB, image/png)
2016-12-07 08:54 UTC, mxie@redhat.com
no flags Details
lxc.log (11.26 KB, text/plain)
2016-12-07 08:55 UTC, mxie@redhat.com
no flags Details

Description mxie@redhat.com 2016-12-07 02:47:57 UTC
Created attachment 1228797 [details]
screenshot

Description of problem:
There is no info "guest in not running" after forcing off the guest which has no display but reserve the serial device on rhel6.9


Version-Release number of selected component (if applicable):
kernel-2.6.32-676.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.497.el6.x86_64
libvirt-0.10.2-62.el6.x86_64
virt-manager-0.9.0-33.el6.x86_64


How reproducible:
100%

Steps to Reproduce:
1.Prepare a shutdown guest in virt-manager
2.Open guest's hardware details page, remove the display (VNC or Spice)
3.Make sure there is serial device in the guest
4.Power on the guest and observe the guest's console, you will see the black screen and some post info (at first time, maybe there is info showing "graphical console not configured for guest", close the guest window and open this guest again, you will see guest console is black) 
5.Force off the guest, but guest console is still black and there is no info "guest in not running" ,pls refer to screenshot
6.Observe the guest status in virt-manager and guest's power button, prove that guest has been shutted off
7.Close the guest window and open this guest again, there will be info "guest in not running" showing in the guest console


Actual results:
As above description

Expected results:
There is info "guest in not running" showing at first time after forcing off the guest which has no display but reserve the serial device 

Additional info:
1.Can't reproduce step5 's problem  on rhel7.3

virt-manager-1.4.0-2.el7.noarch
libvirt-2.0.0-10.el7.x86_64
qemu-kvm-rhev-2.6.0-29.el7.x86_64

Comment 1 mxie@redhat.com 2016-12-07 02:48:36 UTC
Created attachment 1228798 [details]
virt-manager-debug.log

Comment 2 mxie@redhat.com 2016-12-07 08:53:35 UTC
Also could reproduce the problem on LXC guest, pls refer to screenshot "lxc"and  "lxc.log"

Comment 3 mxie@redhat.com 2016-12-07 08:54:43 UTC
Created attachment 1228936 [details]
lxc

Comment 4 mxie@redhat.com 2016-12-07 08:55:07 UTC
Created attachment 1228937 [details]
lxc.log

Comment 11 Jan Kurik 2017-12-06 10:42:01 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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