Server Fault Asked by ivanleoncz on December 30, 2021
I’m trying to use a different Storage Pool on KVM in order to store the virtual disks of my VMs and also the ISOs from the operating systems which I’m using.
For example: I want to use the directory /media/work/kvm
which is mounted over /dev/sda5
, as the default Storage Pool for all future situations
To configure, create and start a new storage pool, it is pretty easy, but a least in Ubuntu, it doesn’t matter if I’m selecting and ISO from a different storage pool, Virtual Machine Manager always points me to the default Storage Pool (/var/cache/libvirt
) as the storage where the virtual disks from my VMs will be created.
How can I avoid this?
From the GUI, there doesn't seem to be a way to do it without an existing VM.
From the command line, the procedure described by ivanleoncz should work, but you'll need to run the commands with sudo
in order for virsh
to show any pools.
Update: It's apparently by design that you can't get the list of pools without sudo
. According to the virsh man page:
Most virsh commands require root privileges to run due to the communications channels used to talk to the hypervisor.
Answered by Vince on December 30, 2021
If you just want to change the image path, you can also edit the storage path in the default
pool by running:
$ virsh pool-edit default
The above command will open the default
pool xml in an editor (vim/nano), now:
libvirt
serviceAnswered by Junaid on December 30, 2021
Aside from the reply above showing how todo it from the command line, you can also change this from virt-manager directly. In the main virt-manager window, go to the menu 'Edit -> Host Details'. In the dialog box that appears, switch to the 'Storage' tab. You can now delete the 'default' storage pool and create a new storage pool to replace it.
Answered by DanielB on December 30, 2021
Before following the steps, be sure that you are running these commands as normal user and that your user belongs to the group libvirtd
(on some systems libvirt
).
Here are the following commands which I used:
Listing current pools:
$ virsh pool-list
Name State Autostart
-------------------------------------------
default active yes
Destroying pool:
$ virsh pool-destroy default
Pool default destroyed
Undefine pool:
$ virsh pool-undefine default
Pool default has been undefined
Creating a directory to host the new pool (if it does not exist):
$ sudo mkdir /media/work/kvm
Defining a new pool with name "default":
$ virsh pool-define-as --name default --type dir --target /media/work/kvm
Pool default defined
Set pool to be started when libvirt daemons starts:
$ virsh pool-autostart default
Pool default marked as autostarted
Start pool:
$ virsh pool-start default
Pool default started
Checking pool state:
$ virsh pool-list
Name State Autostart
-------------------------------------------
default active yes
From now, when creating virtual machines, Virtual Machine Manager will inform you that the *.img file (virtual disk of your VM), will be saved at /media/work/kvm.
Answered by ivanleoncz on December 30, 2021
Get help from others!
Recent Answers
Recent Questions
© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP