Moving a storage pool in Virt Manager/Qemu

Today, I had to move my storage pool in Qemu to some other partition due to low disk space on my root partition. I decided to move it to a directory in my /home partition (I'm used to allocating most of my disk space to the /home partition).

First of all, we need to stop libvirtd.

/sbin/service libvirtd stop

Next, we should move the storage pool to the new location. By default the storage pool is located at /var/lib/libvirt/images. I choose to move it to the directory /home/ausmarton/vm.

mv /var/lib/libvirt/images /home/ausmarton/vm

Any storage pool that is configured, has an xml file created for itself in /etc/libvirt/storage. So, in our case, we just need to edit the file /etc/libvirt/storage/default.xml. Here, we need to edit the path element which comes under the target element.

<path>/var/lib/libvirt/images</path>

Now that line should look something like this:

<path>/home/ausmarton/vm</path>

I would like to point out that /etc/libvirt/storage/ also contains a directory called autostart which again contains symlinks to each of the xml files inside /etc/libvirt/storage/. In case if you don't find any files in /etc/libvirt/storage/ try having a look at /etc/libvirt/storage/autostart/.

After this, we also need to make appropriate changes to each of the VM configurations. For this, we need to edit files located in /etc/libvirt/qemu. Each VM would have an xml file with the name that you have configured for the VM. I have a VM named Fedora, and so there's a config file with the name Fedora.xml. In this, we need to change the source element under the disk element which comes under the devices element. Currently in Fedora.xml, the <source> element is:

<source file='/var/lib/libvirt/images/Server.img'/>

We need to change it to:

<source file='/home/ausmarton/vm/Server.img'/>

Finally, we need to start libvirtd,

/sbin/service libvirtd start

and that's that!
Location: 4, Karunanidhi Beach Rd, Bharathi Nagar, Palavakkam, Chennai, Tamil Nadu, India

Comments

  1. Tim Grissom11 January 2017 at 15:14

    When I attempt to start the moved VM I now get a permission error
    "Error starting domain: Cannot access storage file /home/foo/VMs/myvm.qcow2 (as uid:107 gid:107 permission denied.

    ReplyDelete
    Replies
    1. Tim Grissom11 January 2017 at 16:24

      I got around this but editing /etc/libvirt/qemu.conf - options "user" and "group"

      Delete

Post a Comment

Popular posts from this blog

Errors while trying to monitor Asterisk through Nagios

Today, I was trying to configure nagios to monitor an asterisk setup. I installed the nagios-plugins-check_sip plugin available for CentOS. I also had check_asterisk downloaded from here just to try out both. Now, check_asterisk and check_sip are perl scipts which can be used to monitor an asterisk setup. When run through the command line, they seem to work fine, i.e: given that asterisk or any other sip server is listening and your command is correct, you should get output similar to this: ;SIP/2.0 200 OK, 0.000585 seconds response time, cnt=1 Although, that's exactly what I got, it didn't work the same way through nagios, I was getting the following as the output from the plugin. (Service check did not exit properly) After enabling debug info for nagios, I found this in the logs, HOST: remotehost, SERVICE: Asterisk, CHECK TYPE: Active, OPTIONS: 1, SCHEDULED: Yes, RESCHEDULE: Yes, EXITED OK: No, RETURN CODE: 3, OUTPUT: **ePN failed to compile /usr/lib64/nagios/plugins/chec...
Read more

Configuring remote access for couchdb

By default, CouchDb is configured to be access only from a local port, i.e: you can connect to a couchdb instance as long as it is on the same host. Also, it is necessary that the HTTP request be made using the loopback IP address (127.0.0.1). In case you want to be able to access a couchdb instance from an external machine, you need to make some changes to the couchdb configuration. Note that you would need to have superuser access in order to make changes to these files. Usually couchdb will have two configuration (ini) files in /etc/couchdb depending on your installation. Both these files (default.ini and local.ini) can be used to enable remote hosts to access couchdb. The configuration required for this is: [httpd] port = 5984 bind_address = 0.0.0.0 By default the configuration would be: [httpd] port = 5984 bind_address = 127.0.0.1 This means that the Http server is bound only to the loopback IP address, which is why we change it to 0.0.0.0 to make it bind to any IP address. If...
Read more

Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3

I had a setup of tomcat running on port 8080 and Apache proxying for tomcat on port 80. If I tried to access webapps directly from tomcat on port 8080,. they were accessible, while on port 80, I would get the followig error: Proxy Error 502 “Reason: Error reading from remote server” with Apache 2.2.3 following fix worked: adding retry=1 acquire=3000 timeout=600 Keepalive=On after the Proxy directive in the http configuration.
Read more