Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1335617 - print generic error to user if qemu fails without printing any error
print generic error to user if qemu fails without printing any error
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt (Show other bugs)
7.3
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Pavel Hrdina
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-12 12:25 EDT by David Jaša
Modified: 2016-11-03 14:45 EDT (History)
8 users (show)

See Also:
Fixed In Version: libvirt-2.0.0-1.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-03 14:45:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2577 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2016-11-03 08:07:06 EDT

  None (edit)
Description David Jaša 2016-05-12 12:25:37 EDT
Description of problem:
bug 1328898 comment 19 is a good example of unhelpful error reporting by virt-manager - instead of providing full error by libvirt when starting domain, virt-manager truncates this useful output and print irrelevant python trackebacks instead. A good reproducer for this can be attempt to start domain with nfs-backed disk with virt_use_nfs SELinux boolean set to off.

Version-Release number of selected component (if applicable):
virt-manager-1.3.2-1.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. make VM unstartable, e.g. by using file on nfs to back it's disk and set 'virt_use_nfs' SELinux boolean to off
2. start domain in virt-manager
3.

Actual results:
virt-manager produces unintelligible python traceback (for people not familiar with virt-manager/python/qemu stack)

Expected results:
virt-manager says that VM failed to start because of error in uderlying layers and it should print at least the same error as 'virsh start $DOMAIN' would

Additional info:
Comment 1 Pavel Hrdina 2016-05-26 06:22:21 EDT
Virt-manager prints exactly what it receive from libvirt, we don't truncate anything.  There is only a bug in libvirt, in case that qemu fails without any error we will print qemu command line instead of same sane error message.
Comment 2 Pavel Hrdina 2016-05-30 03:35:27 EDT
So after some testing I've found out that we for a long time doesn't print command line to user if qemu fails without any error.

If there is no error we prints only the libvirt part without any explanation:

"error: internal error: process exited while connecting to monitor:"

The only fix that should improve the error message is in this case to print some generic error explaining what happened.
Comment 3 Pavel Hrdina 2016-06-08 07:58:00 EDT
Upstream commit:

commit 407c6909bc887d77b2c8617fbe6b542d48afec5b
Author: Pavel Hrdina <phrdina@redhat.com>
Date:   Wed Jun 8 12:03:38 2016 +0200

    qemu_process: don't print empty line if qemu exits without any error
Comment 5 lijuan men 2016-07-18 05:00:52 EDT
verify the bug

version:
libvirt-2.0.0-2.el7.x86_64
qemu-kvm-rhev-2.6.0-13.el7.x86_64
kernel-3.10.0-470.el7.x86_64

steps:
1.prepare a guest with nfs disk
2.set virt_use_nfs as off
[root@localhost ~]# setsebool virt_use_nfs off
3.start the guest
[root@localhost ~]# virsh start bios
error: Failed to start domain bios
error: internal error: qemu unexpectedly closed the monitor: 2016-07-18T07:45:34.842844Z qemu-kvm: -drive file=/opt/test/admin.qcow2,format=qcow2,if=none,id=drive-ide0-0-0: Could not open '/opt/test/admin.qcow2': Permission denied
4.use virt-manager to start the guest
the error info is the same as step 3
Comment 7 errata-xmlrpc 2016-11-03 14:45:10 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2577.html

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