Skip to main content

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 delete a file, it may, or may not change the blocks back to zero)
dd if=/dev/sdb of=/mnt/RHEL7-CSB.raw
qemu-img convert -f raw -O qcow2 /mnt/RHEL7-CSB.raw /var/lib/libvirt/images/RHEL7-CSB.qcow2
chown qemu:qemu /var/lib/libvirt/images/RHEL7-CSB.qcow2 && chmod 0664 /var/lib/libvirt/images/RHEL7-CSB.qcow2    
restorecon -RFvv /var/lib/libvirt/images/RHEL7-CSB.qcow2
Create a new VM using virt-manager and point it at your new qcow2 file. (It will fail to boot at this point). Click the light-bulb and change the Disk from Virtio to IDE. (try booting at this point). If it still does not boot... edit the boot string and remove the hint for UEFI or the hint for baremetal (I don't actually know which one fixed the issue) "--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2"
qemu-img convert -f raw -O qcow2 centos7.img centos7.qcow2  
If not obvious, my original image was RHEL7 and the Hypervisor was also RHEL 7 using KVM. From my experience, other hypervisors seem more accepting of different disk image types, etc...

Comments

  1. P2V Using Dd For Kvm-Qemu Guest >>>>> Download Now

    >>>>> Download Full

    P2V Using Dd For Kvm-Qemu Guest >>>>> Download LINK

    >>>>> Download Now

    P2V Using Dd For Kvm-Qemu Guest >>>>> Download Full

    >>>>> Download LINK wl

    ReplyDelete

Post a Comment

Popular posts from this blog

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 ...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.