CentOS7 failed from Esxi 6.5 to Windows Server 2019 HELP!

[yaroslav (staff)]

Yes on the original VM please.

[root@]

[root@freepbx ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/SangomaVG-root 59G 26G 33G 45% /
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 1.9G 224K 1.9G 1% /dev/shm
tmpfs 1.9G 186M 1.7G 10% /run
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
/dev/sda1 1.9G 152M 1.7G 9% /boot
tmpfs 380M 0 380M 0% /run/user/0
tmpfs 380M 0 380M 0% /run/user/995

[yaroslav (staff)]

Can you run sudo fdisk -l inside the VM?
Also, could you tell us where the swaps are located in the original VM? Just make a screenshot of virtual disk paths (acquire that in VM settings).

[root@]

I posted content of VM in esxi few posts ago, here is command output:

Disk /dev/sda: 68.7 GB, 68719476736 bytes, 134217728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000d3757

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 4098047 2048000 83 Linux
/dev/sda2 4098048 134217727 65059840 8e Linux LVM

Disk /dev/mapper/SangomaVG-root: 62.5 GB, 62453186560 bytes, 121978880 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/SangomaVG-swaplv1: 4160 MB, 4160749568 bytes, 8126464 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

[yaroslav (staff)]

Did you use LVM in the original VM?
If so (or if you are not sure), please run lsblk, pvdisplay, vgdisplay and lvdisplay both in the original VM and in the converted one.

[yaroslav (staff)]

Hey,

We've found a solution:
Before VM conversion, please make sure to change boot order.
1. Log in and edit grub
$ vi /etc/default/grub
2. Change GRUB_DEFAULT value to GRUB_DEFAULT=1
3. Apply the changes.
$ grub2-mkconfig -o /boot/grub2/grub.cfg
4. Turn of the VM.
5. Run conversion

You do not need to change the boot order back.

[root@]

Thank you I'll try and update.

[root@]

Hey,

We've found a solution:
Before VM conversion, please make sure to change boot order.
1. Log in and edit grub
$ vi /etc/default/grub
2. Change GRUB_DEFAULT value to GRUB_DEFAULT=1
3. Apply the changes.
$ grub2-mkconfig -o /boot/grub2/grub.cfg
4. Turn of the VM.
5. Run conversion

You do not need to change the boot order back.

SO, after modifying grub config and applying grub2-mkconfig -o /boot/grub2/grub.cfg command the OS refuses to boot properly.
After addling grub2-mkconfig -o /boot/grub2/grub.cfg the GUI of OS trew errors.
Does it mean I should only modify grub only?
Please advice.
I recovered from snapshot so I'm back to original issue.

[yaroslav (staff)]

Yes, please modify grub only.
Change GRUB_DEFAULT value to GRUB_DEFAULT=1
Could you share with us the screenshots of the errors you have?

[root@]

I only modified grub to =1 but it still wouldn't boot after conversion.

[yaroslav (staff)]

Greetings,

Could you share the logs again, the screenshot of the issue you have? Provide me with the following outputs.
check BIOS-UEFI, command:

Code: Select all

dmesg | grep "EFI v"

ver pbx for newer version, command:

Code: Select all

cat /etc/schmooze/pbx-version

ver pbx for old version, command:

Code: Select all

cat /etc/asterisk/freepbxdistro-version

ver ceontOS, command:

Code: Select all

rpm -q centos-release

[danswartz]

A bit of a necro here, but whatever. Anyway, the vswp files are only used by vmware while the guest is running. AFAIK, they have nothing to do with the configuration internally of the vmware guest. I wouldn't think v2v would know or care about this, but I could be wrong (just ask my ex-wife!)

Anyway, I'm having the same problem. In one of my guests, boot on hyper-v looks like a bunch of dracut-initqueue timeout messages, then:

/dev/centos/swap does not exist
/dev/mapper/centos-root does not exist

Any news on this? This happens consistently on all of the 4 centos7 guests I have tried, and is a show-stopper for vmware => hyper-v for me.

[yaroslav (staff)]

Did you already try modifying grub as described here?

[danswartz]

Yes, no difference.

[danswartz]

Solved! Had to rebuild the initramfs for the production release!

For this VM it was:

dracut -f /boot/initramfs-3.10.0-1160.6.1.el7.x86_64.img 3.10.0-1160.6.1.el7.x86_64