Red Hat Bugzilla – Bug 215342
blktap should error out if disk image is not found prior to starting domain
Last modified: 2010-10-22 02:55:33 EDT
Description of problem:
blktap doesn't tell you if your disk image file doesn't exist which can confuse
users as the domain starts, but doesn't find the root device.
Version-Release number of selected component (if applicable):
xen-3.0.3-3 (although I looked at current CVS as of 11/13, and the fix is not in
IBM also provided the upstream changeset that fixes this: 12322:d173b32f54ab
I'll attach the patch.
Created attachment 141068 [details]
Fix for blktap missing file
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Is there anything IBM can do to help get this fixed?
QE ack for RHEL5.1. Straightforward to test.
This is now built into xen-3.0.3-29.el5 in dist-5E-qu-candidate. To test try
- Create a VM config file with a single disk backed by a file & using tap:aio:
- In the 'disks' config line, insert a delibrate typo in the disk filename
- Try to start the guest
A friendly error message should be displayed and the guest should not start.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.