Bug 1147398 - qemu-system-x86_64: block.c bdrv_error_action: Assertion `error >= 0' failed.
Summary: qemu-system-x86_64: block.c bdrv_error_action: Assertion `error >= 0' failed.
Keywords:
Status: CLOSED DUPLICATE of bug 1147282
Alias: None
Product: Fedora
Classification: Fedora
Component: qemu
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fedora Virtualization Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-29 08:15 UTC by Markus Stockhausen
Modified: 2014-09-29 08:38 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-29 08:38:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Markus Stockhausen 2014-09-29 08:15:35 UTC
Description of problem:

Out company and others encountered the following sporadic qemu crash for VMs that are stored on NFS.

qemu-system-x86_64: block.c:2806: bdrv_error_action: Assertion `error >= 0' failed.
2014-06-30 08:40:11.686+0000: shutting down

Form reading the code at the mentioned location I assume there should be some
further details to find.

...
void bdrv_error_action(BlockDriverState *bs, BlockErrorAction action,
                       bool is_read, int error)
{
    assert(error >= 0);
    bdrv_emit_qmp_error_event(bs, QEVENT_BLOCK_IO_ERROR, action, is_read);
    if (action == BDRV_ACTION_STOP) {
        vm_stop(RUN_STATE_IO_ERROR);
        bdrv_iostatus_set_err(bs, error);
    }
}
...

Qemu is started with libvirt so these are the only logs I found. Any idea where to 
search next?

Version-Release number of selected component (if applicable):

Fedora 20, qemu 1.6.2

How reproducible:

once per month

Steps to Reproduce:

Don't know

Actual results:

VM crashes

Expected results:

vm continues to run, a more helpful error is shown.

Comment 1 Richard W.M. Jones 2014-09-29 08:38:23 UTC

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


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