Skip to main content

Adding HDD to KVM/Virtual Machine.

Adding HDD to Virtual Machine.

Steps to create virtio HDD.
  1. First Create a image using qemu-img command.
  2. Add image to VM as a virtio HDD.
  3. This will appear as /dev/vda in the VM, format it using the mke2fs command.
  4. Add to /etc/fstab, so that the device can be mounted on boot up.
Details below.

First Create a image using qemu-img command.

Below is the command to create image.
[ahmed@ahmed-server ~]# qemu-img create VM-1-NEW-HDD.img 100G
This will create a HDD with 100GB disk.

Add image to VM as a virtio HDD.

Method 1 - Adding image from virt-manager UI.

Steps to Adding from the UI.
  1. Select a VM, right-click -> open.
  2. Next on the screen select view -> details.
  3. In the new window select Add Hardware -> Storage -> select managed or other existing storage.
    • Select Device Type : virtio
    • Select Storage Format : raw
'Adding New HDD'
After Adding the HDD we can see it as below.
'After Adding HDD'

Method 2 - Adding image using virsh command.

To edit the VM configuration use below command.
[ahmed@ahmed-server ~]# virsh edit VM-1
Format
virsh edit 
To add the image to the server add the below xml tag.
<disk type='file' device='disk'>
  <driver name='qemu' type='raw' cache='none'/>
  <source file='/virtual_machines/images/VM-1-ADD.img'/>
  <target dev='vda' bus='virtio'/>
  <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</disk>
Now reboot the VM, after restart you will see the new device.
[ahmed@ahmed-server ~]# fdisk -l
'fdisk output'

Added image will appear as /dev/vda in the VM, format it using the mke2fs command.

Before we mount the device we need to format the device.
[ahmed@ahmed-server ~]# mke2fs -j /dev/vda
This will format the device.

Add to /etc/fstab, so that the device can be mounted on boot up.

# /etc/fstab 
# 
# Column Details here : http://man7.org/linux/man-pages/man5/fstab.5.html          
# ------------------------------------------------------------------
/dev/vda            /data            ext3        defaults    0 0
Now we can check by mounting.
[ahmed@ahmed-server ~]# mount -a 
Check by running below command.
[ahmed@ahmed-server ~]# df -h
'DF OUTPUT'

Useful Links.

http://xmodulo.com/install-configure-kvm-centos.html
http://www.cyberciti.biz/faq/kvm-virtualization-in-redhat-centos-scientific-linux-6/
https://www.howtoforge.com/vnc-server-installation-centos-6.5
http://wiki.centos.org/HowTos/KVM
https://www.howtoforge.com/virtualization-with-kvm-on-a-centos-6.4-server-p4
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization/sect-Virtualization-Virtualized_block_devices-Adding_storage_devices_to_guests.html
http://unix.stackexchange.com/questions/92967/how-to-add-extra-disks-on-kvm-based-vm
http://www.techotopia.com/index.php/Adding_a_New_Disk_Drive_to_a_CentOS_6_System
http://blog.zwiegnet.com/linux-server/add-new-hard-drive-to-centos-linux/
http://man7.org/linux/man-pages/man5/fstab.5.html

Comments

Post a Comment

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa