[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] default storage pool will not start



On 08/01/2010 01:15 PM, Albert Hopkins wrote:
<snip>
Gentoo Linux x64 (Gentoo doesn't really have "versions" per-se)

Cool, no worries. It's been a while since I ran Gentoo, but I still remember the gist of it. :)

Lets do some investigation, using the info you've provided.

Looking at the previous listing, it seems like the "default" storage pool hasn't been changed much, and is still pointing to its default location (/var/lib/libvirt/images).

Can you please cat it's definition file, so we can confirm:

  $ sudo virsh pool-dumpxml default

Let's also check if any virtual machine thinks it's using the missing file.

  $ sudo grep -r "gstable.qcow2" /etc/libvirt/qemu

If that doesn't shed any light, let's try a debugging approach.

  a) Stop the libvirt daemon
  b) Change into the superuser account (ie $ sudo su -)
  c) Turn on maximum logging environment variables for libvirt:

     # export LIBVIRT_DEBUG=1
     # export LIBVIRT_LOG_FILTERS="1:default"
# export LIBVIRT_LOG_OUTPUTS="1:file:/var/log/libvirt/libvirt_debug.log"

     Start the libvirtd daemon directly from the command line,
     so it picks up the environment variables
     # libvirt

  d) Wait a few seconds for it to start up properly and for the
     log file /var/log/libvirt/libvirt_debug.log to stop growing
     fast, then Control-C to terminate it.

  e) Do a grep in the log file for the image name, and see if
     this sheds any useful info:

     $ sudo grep gstable.qcow2 /var/log/libvirt/libvirt_debug.log

Hoping that something in the above has helped find out what the problem is?

Regards and best wishes,

Justin Clift


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]