Skip to main content

Oracle Linux VM unable to boot after P2V conversion.




Recently, I was having issue where I had decided to migrate one of my Oracle Linux machine which was running in HP Blade server to visualize and migrated through VMware converter.

Migration went successful and VM migrated successfully without any error but while powering on the Oracle Linux VM its failed with below error.



To resolve this issue I tried to boot the VM with Linix iso and run into rescue mode.

Please find below steps which I followed to boot the VM successfully.

1)     Mount the linux iso to the VM and boot it from CD
2)     At the first prompt, type linux rescue and press Enter.
3)     Change root to the mounted installation. Type chroot /mnt/sysimage and press Enter
4)     Type  ls /boot
5)     There you will see lots of initrd-xxxxx.EL.img files with different name.
6)     To verify the correct initrd-file used to /boot. Type cat /etc/grub.conf, and press Enter.
7)     From the location /etc/grub.conf I found there are two initrd files was there with the same name. From the initial error before traceback its shows the same fille where the boot stuck.
boot operation stuck with 2 same files and failed with "Pid:1, comm: switch_root Not tainted 2.6.39.-400.297.3.el5uek #1

  i.e
initrd-2.6.39-400.297.3.e15uek.img
initrd-2.6.39-400.297.3.e15uek.img 

8)     Rename one of the file with initrd-2.6.39-400.297.3.e15uek.img.old
9)     Rebuild the ramdisk. run the mkinitrd -v -f /boot/initrd-2.6.39-400.297.3.e15uek.img  2.6.39-400.297.3.e15

10)  Rebooted the VM and after that all the boot loader files successfully loaded and able to bring the Oracle Linux VM back.

This article is associated with VMware KB.


Comments

  1. Brandon William24 July 2019 at 16:50

    Nice tip. Keep sharing such ideas! Make sure to check this awesome online audio converter https://onlineconvertfree.com

    ReplyDelete

Post a Comment

Popular posts from this blog

VCF 9 Networking : Centralized vs Distributed Connectivity

  VCF 9 Networking : Centralized vs Distributed Connectivity With the release of VMware Cloud Foundation 9 (VCF 9.0) , VMware has redefined the private cloud networking model by introducing both centralized and distributed connectivity. This dual approach provides flexibility for organizations to choose between traditional edge-based routing and modern, host-level distributed networking. Why New Networking in VCF 9? Prior to VCF 9, NSX networking was largely edge-centric—requiring dedicated Edge clusters to handle north-south traffic. This created scaling and operational overheads. VCF 9 introduces a cloud-like networking abstraction with: Native VPCs (Virtual Private Clouds) for tenant isolation. Transit Gateways (TGW) to interconnect VPCs and external networks. Simplified bootstrapping – NSX VIBs are embedded in ESXi for easier enablement. Improved lifecycle and visibility via integrated VCF Operations. These enhancements align with VMware’s goal of offer...
Post a Comment
Read more

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with...
2 comments
Read more

High-Speed Networking for VMs: VMXNET3 Now Supports Up to 65 Gbps

The VMXNET3 adapter is VMware's high-performance virtual network adapter, designed for optimized performance in vSphere environments. It is the default and recommended adapter for most modern workloads on ESXi , delivering high throughput, low latency, and support for advanced networking features. With the release of vSphere ESXi 8.0 Update 2 , VMXNET3 introduces new capabilities that significantly enhance virtual network performance. What’s New in ESXi 8.0 Update 2 for VMXNET3? Traditionally, VMXNET3 reports a default link speed of 10 Gbps to the guest operating system. However, the actual achievable throughput often exceeds this value—thanks to technologies such as multi-queue support , Receive Side Scaling (RSS) , and Large Packet Offload . Starting with ESXi 8.0 Update 2 , this limitation can now be overridden , and VMXNET3 can be configured to support custom link speeds of up to 65 Gbps . This enhancement enables improved flexibility and throughput for high-performance w...
Post a Comment
Read more