Skip to main content

Issue: Operating System not found


                   

Yesterday, I was working into my vsphere Lab where I have deployed one virtual machine into the environment. After deployment virtual machine was working perfectly fine. After some time, I have added 2 huge hdd of size 800 GB using PVSCSI. Once I added the hdd into the VM, and after accepting the change, I tried to open the console and found vm has rebooted and stuck at "Operating System not found"





That’s look wired, as I have just added the hdd online and suddenly it rebooted and stuck at this stage.
To troubleshoot this issue I tried to gracefully shutdown the VM and tried to bring online in hope, it will detect the changes, but again it stuck at same level "Operating System not found"

I checked my OS drive which is created with the LSI SCSI controller, and the 2 new hdd I created with PVSCSI controller. Here is what the problem exists!!!!!
Basically, When the virtual machine is created with the LSI SCSI controller, the operating system controller is selected as the first boot controller. Now when the controller type is changed to PVSCSI, it is detected as a new device and the controller with the data drive may be moved to the first boot controller. When it fails to find the operating system during bootup, this issue occurs.
Now the issue has been isolated as why the virtual machine is not booting with OS.
I planned to set the "scsi0;0" with the first boot controller.
To do so I perform below steps,

This is applicable from Esxi5.0 or later.

  1. Power off the virtual machine.
  2. Login to the Esxi using Putty or using Tech Support Mode
  3. Access the VMFS volume where the virtual machine is located using below command

    cd /vmfs/volumes/datastore_name/vm_name  
  4. Once VM folder is identified, open the its vmx file in vi (text editor)
  5. Make sure the VM is in powered of state
  6. Add this line to the .vmx file:

    bios.hddOrder = "scsi0:0"
  7. Save the changes into .vmx file.

  8. Now we need to reload the  .vmx file. to recognize the changes.
 To reload the .vmx file please use below steps:
    1. Fist we have to obtain the Vmid of the virtual machine using below command:
    2. #vim-cmd vmsvc/getallvms
    3. You see output similar to: 
      Vmid Name File Guest OS Version Annotation 2848 Win2003_storage_performance [local] Win .vmx winNetEnterpriseGuest vmx-07 To be used as a template
    4. In this example, the Vmid is 2848.
    5. Reload the .vmx file using this command:

      # vim-cmd vmsvc/reload Vmid
  1. Now Poweron the VM, Your VM wil boot now with OS  :)

Happy Sharing.

Comments

Popular posts from this blog

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment.
Somewhere during security auditing we require to provide several information to security team to get successful audit.
One of them is the compliance of Virtual machine auditing of creation date and time.
Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi.
To get the details we will use VMware Powercli to extract the details.
By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date.
Below is the function which needed to be copy and paste into the Powercli.
=======================================================================
function Get-VMCreationTime { $vms = get-vm $vmevts = @() $vmevt = new-object PSObject foreach ($vm in $vms) { #Progress bar: $foundString = "       Found: "+$v…

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 permissionUse above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_netOpt for option 3 (Hostname)Change the hostname to new nameReboot 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 the help of below KB 2112283 article.



Happy Sharin…

Could not connect to one or more vCenter Server systems: https://FQDN:443/sdk

Recently I got a case where vCenter 6.0 where the webclient was not showing inventory while loading. Issue occur when the customer was performing migration activity of virtual machine.
We verified that the vpxd services of vCenter, which is VCSA (Appliance), went into stopped stated just after starting means its crashing.
On VCSA Shell: service-control --status vmware-vpxd shows "stopped" service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again
VCSA 6.0 is linked with extrnal PSC 6.0. Verified the services of PSC and found all looks into good state.
Tried to power off both the VCSA and PSC and Power on in sequence where we started first PSC and later VCSA. After restarting the VCSA, status of the VPXD services was same as it was getting stopped after couple of seconds.
Checked the VPXD logs and found that the heartbeat between ESXi and VCSA was getting timed out for more than 1032 ms or more.
VCSA has generated the core dump at /var/core. …