13.3. Adding Storage Devices to Guests

Procedure 13.1. Adding file-based storage

1. Create a storage file or use an existing file (such as an IMG file). Note that both of the following commands create a 4GB file which can be used as additional storage for a guest:
   • Pre-allocated files are recommended for file-based storage images. Create a pre-allocated file using the following dd command as shown:

     # dd if=/dev/zero of=/var/lib/libvirt/images/FileName.img bs=1M count=4096

     Copy to Clipboard
   • Alternatively, create a sparse file instead of a pre-allocated file. Sparse files are created much faster and can be used for testing, but are not recommended for production environments due to data integrity and performance issues.

     # dd if=/dev/zero of=/var/lib/libvirt/images/FileName.img bs=1M seek=4096 count=0

     Copy to Clipboard
2. Create the additional storage by writing a <disk> element in a new file. In this example, this file will be known as NewStorage.xml.
   A <disk> element describes the source of the disk, and a device name for the virtual block device. The device name should be unique across all devices in the guest, and identifies the bus on which the guest will find the virtual block device. The following example defines a virtio block device whose source is a file-based storage container named FileName.img:

   <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/var/lib/libvirt/images/FileName.img'/>
      <target dev='vdb'/>
   </disk>
   

   Copy to Clipboard
   Device names can also start with "hd" or "sd", identifying respectively an IDE and a SCSI disk. The configuration file can also contain an <address> sub-element that specifies the position on the bus for the new device. In the case of virtio block devices, this should be a PCI address. Omitting the <address> sub-element lets libvirt locate and assign the next available PCI slot.
3. Attach the CD-ROM as follows:

   <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/var/lib/libvirt/images/FileName.img'/>
      <readonly/>
      <target dev='hdc'/>
   </disk >
   

   Copy to Clipboard
4. Add the device defined in NewStorage.xml with your guest (Guest1):

   # virsh attach-device --config Guest1 ~/NewStorage.xml

   Copy to Clipboard

   Note

   This change will only apply after the guest has been destroyed and restarted. In addition, persistent devices can only be added to a persistent domain, that is a domain whose configuration has been saved with virsh define command.
   If the guest is running, and you want the new device to be added temporarily until the guest is destroyed, omit the --config option:

   # virsh attach-device Guest1 ~/NewStorage.xml

   Copy to Clipboard

   Note

   The virsh command allows for an attach-disk command that can set a limited number of parameters with a simpler syntax and without the need to create an XML file. The attach-disk command is used in a similar manner to the attach-device command mentioned previously, as shown:

   # virsh attach-disk Guest1 /var/lib/libvirt/images/FileName.img vdb --cache none --driver qemu --subdriver raw
   

   Copy to Clipboard

   Note that the virsh attach-disk command also accepts the --config option.
5. Start the guest machine (if it is currently not running):

   # virsh start Guest1

   Copy to Clipboard

   Note

   The following steps are Linux guest specific. Other operating systems handle new storage devices in different ways. For other systems, refer to that operating system's documentation.

6. Partitioning the disk drive

   The guest now has a hard disk device called /dev/vdb. If required, partition this disk drive and format the partitions. If you do not see the device that you added, then it indicates that there is an issue with the disk hotplug in your guest's operating system.
   1. Start fdisk for the new device:

      # fdisk /dev/vdb
      Command (m for help):
      

      Copy to Clipboard
   2. Type n for a new partition.
   3. The following appears:

      Command action
      e   extended
      p   primary partition (1-4)
      

      Copy to Clipboard
      Type p for a primary partition.
   4. Choose an available partition number. In this example, the first partition is chosen by entering 1.

      Partition number (1-4): 1

      Copy to Clipboard
   5. Enter the default first cylinder by pressing Enter.

      First cylinder (1-400, default 1):

      Copy to Clipboard
   6. Select the size of the partition. In this example the entire disk is allocated by pressing Enter.

      Last cylinder or +size or +sizeM or +sizeK (2-400, default 400):

      Copy to Clipboard
   7. Enter t to configure the partition type.

      Command (m for help): t

      Copy to Clipboard
   8. Select the partition you created in the previous steps. In this example, the partition number is 1 as there was only one partition created and fdisk automatically selected partition 1.

      Partition number (1-4): 1

      Copy to Clipboard
   9. Enter 83 for a Linux partition.

      Hex code (type L to list codes): 83

      Copy to Clipboard
   10. Enter w to write changes and quit.

       Command (m for help): w
       

       Copy to Clipboard
   11. Format the new partition with the ext3 file system.

       # mke2fs -j /dev/vdb1

       Copy to Clipboard
7. Create a mount directory, and mount the disk on the guest. In this example, the directory is located in myfiles.

   # mkdir /myfiles
   # mount /dev/vdb1 /myfiles
   

   Copy to Clipboard
   The guest now has an additional virtualized file-based storage device. Note however, that this storage will not mount persistently across reboot unless defined in the guest's /etc/fstab file:

   /dev/vdb1    /myfiles    ext3     defaults    0 0

   Copy to Clipboard