[
https://issues.apache.org/jira/browse/CLOUDSTACK-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764137#comment-13764137
]
Wei Zhou commented on CLOUDSTACK-3565:
--------------------------------------
Storage pool can be changed to persistent by following steps
(1) dump storage pool configuration
virsh pool-dumpxml 72301816-c94a-3ad4-a1fd-7a1749c56171
>/etc/libvirt/storage/72301816-c94a-3ad4-a1fd-7a1749c56171.xml
(2) define the storage pool using configuration file
virsh pool-define /etc/libvirt/storage/72301816-c94a-3ad4-a1fd-7a1749c56171.xml
Testing result:
[root@cs-kvm012 ~]# virsh pool-info 72301816-c94a-3ad4-a1fd-7a1749c56171
Name: 72301816-c94a-3ad4-a1fd-7a1749c56171
UUID: 72301816-c94a-3ad4-a1fd-7a1749c56171
State: running
Persistent: no
Autostart: no
Capacity: 7.28 TiB
Allocation: 1.02 TiB
Available: 6.25 TiB
[root@cs-kvm012 ~]# virsh pool-dumpxml 72301816-c94a-3ad4-a1fd-7a1749c56171
>/etc/libvirt/storage/72301816-c94a-3ad4-a1fd-7a1749c56171.xml
[root@cs-kvm012 ~]# virsh pool-define
/etc/libvirt/storage/72301816-c94a-3ad4-a1fd-7a1749c56171.xml
Pool 72301816-c94a-3ad4-a1fd-7a1749c56171 defined from
/etc/libvirt/storage/72301816-c94a-3ad4-a1fd-7a1749c56171.xml
[root@cs-kvm012 ~]# virsh pool-info 72301816-c94a-3ad4-a1fd-7a1749c56171
Name: 72301816-c94a-3ad4-a1fd-7a1749c56171
UUID: 72301816-c94a-3ad4-a1fd-7a1749c56171
State: running
Persistent: yes
Autostart: no
Capacity: 7.28 TiB
Allocation: 1.02 TiB
Available: 6.25 TiB
> Restarting libvirtd service leading to destroy storage pool
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-3565
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3565
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> Affects Versions: 4.2.0
> Environment: KVM
> Branch 4.2
> Reporter: Rayees Namathponnan
> Assignee: Marcus Sorensen
> Priority: Blocker
> Labels: documentation
> Fix For: 4.2.0
>
>
> Steps to reproduce
> Step 1 : Create cloudstack step in kvm
> Step 2 : From kvm host check "virsh pool-list"
> Step 3: Stop and start libvirtd service
> Step 4 : Check "virsh pool-list"
> Actual Result
> "virsh pool-list" is blank after restart libvird service
> [root@Rack2Host12 agent]# virsh pool-list
> Name State Autostart
> -----------------------------------------
> 41b632b5-40b3-3024-a38b-ea259c72579f active no
> 469da865-0712-4d4b-a4cf-a2d68f99f1b6 active no
> fff90cb5-06dd-33b3-8815-d78c08ca01d9 active no
> [root@Rack2Host12 agent]# service cloudstack-agent stop
> Stopping Cloud Agent:
> [root@Rack2Host12 agent]# virsh pool-list
> Name State Autostart
> -----------------------------------------
> 41b632b5-40b3-3024-a38b-ea259c72579f active no
> 469da865-0712-4d4b-a4cf-a2d68f99f1b6 active no
> fff90cb5-06dd-33b3-8815-d78c08ca01d9 active no
> [root@Rack2Host12 agent]# virsh list
> Id Name State
> ----------------------------------------------------
> [root@Rack2Host12 agent]# service libvirtd stop
> Stopping libvirtd daemon: [ OK ]
> [root@Rack2Host12 agent]# service libvirtd start
> Starting libvirtd daemon: [ OK ]
> [root@Rack2Host12 agent]# virsh pool-list
> Name State Autostart
> -----------------------------------------
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
