LVM can't find devices after moving from VirtualBox to KVM
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
LVM can't find devices after moving from VirtualBox to KVM
This is probably much less a virtualization question that an LVM question. However, I'm not sure where to ask LVM questions, and it's hypervisors that are giving me problems.
I frequently have to move virtual appliances made in VirtualBox over to KVM or Xen. When I move the disk image over and boot the box, hard drive entries like /dev/sda or /dev/hda become /dev/vda or /dev/xda. Most often the system simply detects the changes and boots. Starting with the more recent Fedoras this has become a little painful, as I always end up neededing to regenerate an initramfs with dracut.
Yesterday I got a VM from one of the more junior sys admins. It was his first time using CentOS 7, and left LVM turned on. After fiddiling with migrating the VM for a while I can get it to book just fine in dracut resuce mode, but not in standard mode with a standard kernel.
It would certianly be more efficient to redo the VM without LVM, but I really want to know how to fix it. I assume I just need to update the mapping in LVM, but haven't found a reasonable tutorial just searching the net.
Here's my error message:
[ OK ] Reached target Paths.
[ OK ] Reached target Basic System.
Starting File System Check on /dev/mapper/centos-root...
systemd-fsck[288]: fsck: error 2 (No such file or directory) while executing fsck.ext2 for /dev/mapper/centos-root
[ OK ] Started File System Check on /dev/mapper/centos-root
dracut-initqueue[250]: Warning: Could not boot
dracut-initqueue[250]: Warning: /dev/centos/root does not exist
dracut-initqueue[250]: Warning: /dev/centos/swap does not exist
dracut-initqueue[250]: Warning: /dev/mapper/centos-root does not exist
Starting Dracut Emergency Shell...
Warning: /dev/centos/root does not exist
Warning: /dev/centos/swap does not exist
Warning: /dev/mapper/centos-root does not exist
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.