[virt-tools-list] Refreshing Storage Pool {Scanned}

[Ritchie P. Fraser]

Hi Cole,

Distro + Version: Ubuntu Server 12.04 LTS

$ virsh version

    Compiled against library: libvir 0.9.8
    Using library: libvir 0.9.8
    Using API: QEMU 0.9.8
    Running hypervisor: QEMU 1.0.0

Will restarting libvirt affect / kill all other currently the running VM's (servers)?

Ritchie

-----Original Message-----
From: Cole Robinson [mailto:crobinso at redhat.com] 
Sent: 10 March 2014 15:41
To: Ritchie P. Fraser; virt-tools-list at redhat.com
Subject: Re: [virt-tools-list] Refreshing Storage Pool {Scanned}

On 03/10/2014 11:33 AM, Ritchie P. Fraser wrote:
> Hello,
> 
>  
> 
> I am having issues getting KVM / QEMU / libvirt refreshing one of my 
> storage pools.
> 
>  
> 
> I have SAN storage volumes connected through multipath iscsi on the 
> host in /dev/mapper - All GOOD so far
> 
>  
> 
>                 $ ls -l /dev/mapper
> 
>  
> 
>                 total 0
> 
>                 crw------- 1 root root 10, 236 Feb 20 17:31 control
> 
>                 lrwxrwxrwx 1 root root       8 Mar 10 13:24 mpath-a -> ../dm-5
> 
>                 lrwxrwxrwx 1 root root       8 Mar 10 13:24 mpath-b -> ../dm-4
> 
>                 lrwxrwxrwx 1 root root       8 Mar 10 13:24 mpath-c -> ../dm-2
> 
>                 lrwxrwxrwx 1 root root       8 Mar 10 13:24 mpath-d -> ../dm-11
> 
>  
> 
> I list the storage pools on the KVM / QEMU / visrh host ...
> 
>  
> 
>                 $ virsh pool-list
> 
>  
> 
>                 Name                 State      Autostart
> 
>                 -----------------------------------------
> 
>                 archive              active     yes
> 
>                 multipath_iscsi      active     yes
> 
>  
> 
> ... and then list the volumes in the multipath_iscsi storage pool ...
> 
>  
> 
>                 $ virsh vol-list multipath_iscsi
> 
>                
> 
>                 Name                 Path
> 
>                 -----------------------------------------
> 
>                 dm-5                 /dev/mapper/mpath-a
> 
>                 dm-4                 /dev/mapper/mpath-b
> 
>                 dm-2                 /dev/mapper/mpath-c
> 
>  
> 
> I see thet my NEW SAN volume does not show up in the listed volumes, 
> so I refresh the storage pool and re-list ...
> 
>  
> 
>                 $ virsh pool-refresh multipath_iscsi
> 
>                 $ virsh vol-list multipath_iscsi
> 
>                
> 
>                 Name                 Path
> 
>                 -----------------------------------------
> 
>                 dm-5                 /dev/mapper/mpath-a
> 
>                 dm-4                 /dev/mapper/mpath-b
> 
>                 dm-2                 /dev/mapper/mpath-c
> 
>  
> 
> Uh Oh!, No new volume listed in the storage pool
> 
>  
> 
> *Is there anything else I should be doing?*
> 
>  
> 
> The host is seeing the additional multipath iscsi volume so, there is 
> nothing wrong with the volume, iscsi, multipath setup... I just can 't 
> get virsh to "add it to the storage pool"
> 
>  

Please provide your distro + version, and libvirt version.

If you restart libvirt, does it notice the new storage volume?

- Cole

--
This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.