[fedora-virt] virsh output discrepancy with vol-list

Shergill, Gurinder gurinder.shergill at hp.com
Thu Apr 11 13:10:46 UTC 2013


> -----Original Message-----
> From: Kashyap Chamarthy [mailto:kashyapc at fedoraproject.org]
> Sent: Thursday, April 11, 2013 4:09 AM
> To: Shergill, Gurinder
> Cc: virt at lists.fedoraproject.org
> Subject: Re: [fedora-virt] virsh output discrepancy with vol-list
> 
> On 04/11/2013 08:36 AM, Shergill, Gurinder wrote:
> > Hello,
> >
> > I am seeing following discrepancy with virsh output for volume list,
> which goes away when I restart the libvirtd daemon.
> >
> > Here virsh shows 4 volumes. Also, notice that first 2 volumes are
> duplicates.
> >
> > $ virsh vol-list --pool default
> > Name                 Path
> > -----------------------------------------
> > crab.vol.0.img       /var/lib/libvirt/images/crab.vol.0.img
> > crab.vol.0.img       /var/lib/libvirt/images/crab.vol.0.img
> > fish.vol.0.img       /var/lib/libvirt/images/fish.vol.0.img
> > fish.vol.1.img       /var/lib/libvirt/images/fish.vol.1.img
> >
> > However, none of the above volumes currently exist (as I had just
> deleted them using, again, using virsh).
> >
> > $ ll /var/lib/libvirt/images/
> > total 0
> >
> > Now, I restart libvirt. And, after that virsh output is fine.
> >
> > $ virsh vol-list --pool default
> > Name                 Path
> > -----------------------------------------
> >
> > Any idea what is going on here ? Is this a known issue ?
> 
> Not sure at the first glance.
> >
> > I am using Fedora 17.
> 
> Version of libvirt ?
> 
> I'm using this version & I can't reproduce it -- libvirt-1.0.4-
> 1.fc18.x86_64
> 
> Do you find the same issue with using --
> http://fedorapeople.org/groups/virt/virt-preview/
> 
> For further debugging:
> 
> Add the below in in libvirtd.log
> ====
> log_level = 1
> log_outputs = 1:file:/var/tmp/libvirtd.log ====
> 
> $ service libvirtd restart

I enabled the log output and set the level to 1, just like you suggested. Interestingly, the issue happened almost right away and, this time, I only had to create a guest from scratch.

$ virsh vol-list --pool default
Name                 Path                                    
-----------------------------------------
crab.vol.0.img       /var/lib/libvirt/images/crab.vol.0.img  
crab.vol.0.img       /var/lib/libvirt/images/crab.vol.0.img  
crab.vol.1.img       /var/lib/libvirt/images/crab.vol.1.img  
crab.vol.1.img       /var/lib/libvirt/images/crab.vol.1.img  
crab.vol.2.img       /var/lib/libvirt/images/crab.vol.2.img  
crab.vol.2.img       /var/lib/libvirt/images/crab.vol.2.img  
crab.vol.3.img       /var/lib/libvirt/images/crab.vol.3.img  
crab.vol.3.img       /var/lib/libvirt/images/crab.vol.3.img  

$ ll /var/lib/libvirt/images/
total 1248240
-rw-------. 1 root root 1271201792 Apr 10 21:53 crab.vol.0.img
-rw-------. 1 root root    2490368 Apr 10 21:47 crab.vol.1.img
-rw-------. 1 root root    2490368 Apr 10 21:47 crab.vol.2.img
-rw-------. 1 root root    2490368 Apr 10 21:47 crab.vol.3.img

Restarted libvirt ... and virsh gives correct information.

$ virsh vol-list --pool default
Name                 Path                                    
-----------------------------------------
crab.vol.0.img       /var/lib/libvirt/images/crab.vol.0.img  
crab.vol.1.img       /var/lib/libvirt/images/crab.vol.1.img  
crab.vol.2.img       /var/lib/libvirt/images/crab.vol.2.img  
crab.vol.3.img       /var/lib/libvirt/images/crab.vol.3.img  

> 
> Monitor the log for interesting info.
>

The log file is HUGE - about 400k lines ! ... any suggestions on what would classify as interesting info for this issue ?

Sunny



More information about the virt mailing list