Bug 854658

Summary: libvirtd (qemu:///session) can't find a disk, even though it really exists
Product: [Fedora] Fedora Reporter: Richard W.M. Jones <rjones>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: berrange, clalancette, itamar, jforbes, jyang, laine, libvirt-maint, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-17 09:07:03 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Richard W.M. Jones 2012-09-05 09:49:29 EDT
Description of problem:

I'm pretty sure this is a libvirt bug, although it might be a qemu
thing.  But killing the user libvirtd process fixes it, so that seems
to indicate libvirt.

Launching libguestfs gives:

libguestfs: error: could not create appliance through libvirt: internal error process exited while connecting to monitor: qemu-system-x86_64: -drive file=/home/rjones/d/libguestfs/.guestfs-1000/root.2801,if=none,id=drive-scsi0-0-1-0,format=raw,cache=unsafe: could not open disk image /home/rjones/d/libguestfs/.guestfs-1000/root.2801: No such file or directory

This file *does* exist.  libvirt (or something) just cannot "see" it
for some reason.  This state persists until the user libvirtd program
is killed, and then everything starts working again.

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

libvirt-0.10.0-1.fc19.x86_64

How reproducible:

Happened twice so far, on two separate days.

Steps to Reproduce:
1. Unknown, but keep starting up libguestfs and you'll hit it eventually.
Comment 1 Richard W.M. Jones 2012-09-17 09:07:03 EDT
I'm going to put this down to the buggy libvirt 0.10.0
release.  Certainly libvirt from git nor libvirt 0.10.1
seems to suffer from this any more.