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

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one.  If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin

Install RHEL 7 on old HP DL380 g5

Someone at work had been running RHEL on an HP DL380 G5 and blew it up.  After several attempts at doing an installation that made me conclude the hardware was actually bad... I kept digging for the answer. Attempt install and Anaconda could not find any disks - try a Drivers Disk (dd.img) both cciss and hpsa.   -- once we did that, when the system would reboot it would say it could not find a disk. hmmm. Boot from your installation media and interrupt the startup at grub. Add hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 to the line starting with linuxefi press CTRL-X to boot. Once the system restarts after the install, you need to once again interrupt the startup and add the line from above. After the system starts, edit /etc/default/grub and add those 2 parameters to the end of the line starting with GRUB_CMDLINE_LINUX (which likely has quiet at the end of the line currently). then run # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.orig # grub2-mkconfig -o /boot/grub2

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un