Bug 1590653 - Host hang on shut down, while the states of the guests are not detect correctly
Summary: Host hang on shut down, while the states of the guests are not detect correctly
Keywords:
Status: CLOSED DUPLICATE of bug 1589970
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-13 06:57 UTC by Frank Büttner
Modified: 2019-05-21 14:58 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-21 14:58:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The journal log of the host shut down. (161.49 KB, text/x-vhdl)
2018-06-13 06:57 UTC, Frank Büttner
no flags Details

Description Frank Büttner 2018-06-13 06:57:00 UTC
Created attachment 1450804 [details]
The journal log of the host shut down.

Description of problem:
When the kvm host get an shut down command, then the running guest are also powered off. This will work, as it must. But after the shut down of the guest, libvirt don't receive the results clearly. 

Version-Release number of selected component (if applicable):
libvirt-client-4.1.0-2.fc28.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Let an vm run
2. shot down the host

Actual results:
The host is hanging for 290 seconds on shut down, until the script times out.


Expected results:
That the host don't hang.


Additional info:
The vm  itself will do an clear power off.

Comment 1 Ben Cotton 2019-05-02 21:35:20 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Cole Robinson 2019-05-21 14:58:41 UTC

*** This bug has been marked as a duplicate of bug 1589970 ***


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