Skip to main content

Clone an LVM based KVM based Virtual Machine ;-)

I recently opted to use a volume for my VM (instead of creating a file).

RHEVM01 is the "source" and RHUTIL01 is the destination.  I am also cloning from my vg_blackmesa to vg_apps.  One thing I would like to figure out is how to monitor the progress.


root@blackmesa ~]# lvdisplay /dev/mapper/vg_blackmesa-VM_RHEVM01
  --- Logical volume ---
  LV Path                /dev/vg_blackmesa/VM_RHEVM01
  LV Name                VM_RHEVM01
  VG Name                vg_blackmesa
  LV UUID                zx4BLV-Athf-Ymcd-ox4h-965J-uo30-Aey9dJ
  LV Write Access        read/write
  LV Creation host, time blackmesa.area51.private, 2012-06-22 00:12:02 -0500
  LV Status              available
  # open                 1
  LV Size                20.00 GiB
  Current LE             5120
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:6


[root@blackmesa ~]# vgs
  VG           #PV #LV #SN Attr   VSize   VFree  
  vg_apps        1   1   0 wz--n- 278.46g 153.46g
  vg_blackmesa   1   6   0 wz--n- 135.29g  43.29g


[root@blackmesa ~]# lvcreate -nVM_RHUTIL01 -L20g vg_apps
  Logical volume "VM_RHUTIL01" created


[root@blackmesa ~]# lvdisplay /dev/mapper/vg_apps-VM_RHUTIL01 
  --- Logical volume ---
  LV Path                /dev/vg_apps/VM_RHUTIL01
  LV Name                VM_RHUTIL01
  VG Name                vg_apps
  LV UUID                EM6eA5-Jcww-iugy-UfRn-GgJE-cvaC-P5i1Wd
  LV Write Access        read/write
  LV Creation host, time blackmesa.area51.private, 2012-06-22 19:14:04 -0500
  LV Status              available
  # open                 0
  LV Size                20.00 GiB
  Current LE             5120
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:7


-- During the copy, you can watch via iostat

[root@blackmesa ~]# ls -l /dev/mapper/vg_blackmesa-VM_RHEVM01 
lrwxrwxrwx. 1 root root 7 Jun 22 00:12 /dev/mapper/vg_blackmesa-VM_RHEVM01 -> ../dm-6
[root@blackmesa ~]# dd if=/dev/dm-6 of=^C
[root@blackmesa ~]# ls -l /dev/mapper/vg_apps-VM_RHUTIL01 
lrwxrwxrwx. 1 root root 7 Jun 22 19:14 /dev/mapper/vg_apps-VM_RHUTIL01 -> ../dm-7


[root@blackmesa ~]# dd if=/dev/dm-6 of=/dev/dm-7 bs=512K 
40960+0 records in
40960+0 records out
21474836480 bytes (21 GB) copied, 273.34 s, 78.6 MB/s
[root@blackmesa qemu]# cat RHEVM01.xml | sed 's/RHEVM01/RHUTIL01/g' > RHUTIL01.xml
[root@blackmesa qemu]# uuidgen 
bffa485a-70d3-4d58-80b2-bf1a56a81928
OR... use

[root@blackmesa ~]# dd if=/dev/vg_blackmesa/VM_RHEVM01 of=/dev/mapper/vg_apps-VM_RHUTIL01 bs=512K


[root@blackmesa qemu]#  vi RHUTIL01.xml
-- update 
    uuid
    Description (if present)
    name
    macaddress
[root@blackmesa qemu]# service libvirtd restart 
[root@blackmesa qemu]# virsh start RHUTIL01 && virsh start RHEVM01; 
[root@blackmesa qemu]# sudo virsh list --all
 Id    Name                           State
----------------------------------------------------
 1     CRWX01                         running
 2     RHNSAT01                       running
 3     WINPDC01                       running
 4     RHEVM01                        running
 5     RHUTIL01                       running


-- You will, of course, need to update your network configuration inside
   the cloned VM because of the new mac address.

Labels:

Comments

Post a Comment

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances.  I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals.  In this case, the rigor is justified.  They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system.  They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE:  This is NOT a good implementation strategy in the "real world"  it will simply allow you to test the functionality.  There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils ...
Post a Comment
Read more