Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1320924

Summary: "Process exited prior to exec" when start guest with no enough space for qemu log and virtlogd is enabled.
Product: Red Hat Enterprise Linux 7 Reporter: Fangge Jin <fjin>
Component: libvirtAssignee: Erik Skultety <eskultet>
Status: CLOSED WONTFIX QA Contact: Yanqiu Zhang <yanqzhan>
Severity: low Docs Contact:
Priority: low    
Version: 7.3CC: dyuan, hhan, jsuchane, mzhan, xuzhang, yafu
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-04 15:17:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
libvirt log and virtlogd log none

Description Fangge Jin 2016-03-24 10:23:45 UTC
Created attachment 1139883 [details]
libvirt log and virtlogd log

Description of problem:
There is no enough disk space for qemu log, guest starts failed:
# virsh start rhel7.2
error: Failed to start domain rhel7.2
error: internal error: Process exited prior to exec: 

Version-Release number of selected component (if applicable):
libvirt-1.3.2-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Mount a disk with little space left on /var/log/libvirt/qemu
# df
/dev/sdb3                                                        12972     12952        20 100% /var/log/libvirt/qemu

2.Guest rhel7.2 has a log file existing in the directory:
# ls /var/log/libvirt/qemu/
rhel7.2.log  rhel7.2.log.0  test.out

3.
# virsh start rhel7.2
error: Failed to start domain rhel7.2
error: internal error: Process exited prior to exec:

4.Check guest log file, the last line is incomplete:
# tail -1 /var/log/libvirt/qemu
2016-03-24 10:15:31.579+0000: starting up libvirt version: 1.3.2, package: 1.el

5.If no qemu log file exits before guest starts, guest start with clear error message:
# ls /var/log/libvirt/qemu/

# virsh start rhel7.2
error: Failed to start domain rhel7.2
error: Unable to open file: /var/log/libvirt/qemu/rhel7.2.log: No space left on device


Actual results:
Guest start failed with error "Process exited prior to exec:"

Expected results:
Guest start failed with more clear error message.

Additional info:

Comment 2 Jaroslav Suchanek 2016-04-05 14:54:59 UTC
I guess anything can go wrong when the disk is out of space. Erik please have a look.

Comment 3 Erik Skultety 2019-01-04 15:17:38 UTC
If something like this happens, then you've got bigger problems than just confusing messages. If anything, an error is reported in the daemon's log too. Closing as WONTFIX since this is a big corner case.