LINUX AND VMWARE STUFF

This Blog is to share our knowledge and expertise on Linux System Administration and VMware Administration

Showing posts with label VMWare Best Practices. Show all posts
Showing posts with label VMWare Best Practices. Show all posts

Saturday, November 25, 2017

Virtual machines show warning messages when starting the udev daemon Linux

Saturday, November 25, 2017 0

Virtual machines show warning messages when starting the udev daemon.

After upgrading VMware Tools,  Linux virtual machines show warnings when starting the udev daemon.

dmesg shows the below messages.

Starting udev:
udevd[572]: add_to_rules: unknown key 'SUBSYSTEMS'
udevd[572]: add_to_rules: unknown key 'ATTRS{vendor}'
udevd[572]: add_to_rules: unknown key 'ATTRS{model}'
udevd[572]: add_to_rules: unknown key 'SUBSYSTEMS'
udevd[572]: add_to_rules: unknown key 'ATTRS{vendor}'
udevd[572]: add_to_rules: unknown key 'ATTRS{model}'

Ctrl+C will bypass udev daemon to finish the boot process.

To disable the warning message, comment out unused lines (ubuntu  & other type of unix entries) in the  /etc/udev/rules.d/99-vmware-scsi-udev.rule file

For linux we need to modify the below line from

ACTION=="add", BUS=="scsi", SYSFS{vendor}=="VMware, " , SYSFS{model}=="VMware Virtual S", RUN+="/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'"

To

ACTION=="add", BUS=="scsi", SYSFS{vendor}=="VMware " , SYSFS{model}=="Virtual disk ", RUN+="/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'"

Save the modifiation and reboot the virtual machine.
Tags # Linux Troubleshooting # VMWare Best Practices Continue Reading
By v�o l�c No comments:
Labels: ,

Wednesday, November 8, 2017

Enabling Intel VT-x and AMD-V Virtualization Hardware Extensions in BIOS of ESXI

Wednesday, November 08, 2017
This section describes how to identify hardware virtualization extensions and enable them in your BIOS if they are disabled. The Intel VT-x extensions can be disabled in the BIOS. The virtualization extensions cannot be disabled in the BIOS for AMD-V. 

Procedure for Enabling virtualization extensions in BIOS

1.    Reboot the computer and open the system's BIOS menu. This can usually be done by pressing the delete key, the F1 key or Alt and F4 keys or F10 key depending on the Harware.

2.    Enabling the virtualization extensions in BIOS

        a.    Open the Processor submenu The processor settings menu may be hidden in the Chipset, Advanced CPU Configuration or Northbridge.
         b.    Enable Intel Virtualization Technology (also known as Intel VT-x). AMD-V extensions cannot be disabled in the BIOS and should already be enabled. The virtualization extensions may be labeled Virtualization Extensions, Vanderpool or various other names depending on the OEM and system BIOS.
         c.    Enable Intel VT-d or AMD IOMMU, if the options are available. Intel VT-d and AMD IOMMU are used for PCI device assignment.
         d.    Select Save & Exit.

3.    Reboot the machine.

4.    When the machine has booted, run cat /proc/cpuinfo |grep -E "vmx|svm". Specifying --color is optional, but useful if you want the search term highlighted. If the command outputs, the virtualization extensions are now enabled. If there is no output your system may not have the virtualization extensions or the correct BIOS setting enabled.
Tags # VMWare Best Practices Continue Reading
By v�o l�c
Labels:

Tuesday, November 7, 2017

How to Determin if Intel Virtualization Technology or AMD Virtualization is enabled in the BIOS without reboot

Tuesday, November 07, 2017
When troubleshooting vMotion, Enhanced VMotion Capability (EVC), or 64bit virtual machine performance, you may need to determine if the Intel Virtualization Technology (VT) or AMD Virtualization (AMD-V) are enabled in the BIOS.

This section describes how to identify hardware virtualization extensions and enable them in your BIOS if they are disabled.

Log in to the ESX host as the root user.

    Run this command:

    esxcfg-info|grep "\----\HV Support"

    The output of the HV Support command indicates the type of Hyper-visor support available. These are the descriptions for the possible values:

    0 - VT/AMD-V indicates that support is not available for this hardware.
    1 - VT/AMD-V indicates that VT or AMD-V might be available but it is not supported for this hardware.2 - VT/AMD-V indicates that VT or AMD-V is available but is currently not enabled in the BIOS.3 - VT/AMD-V indicates that VT or AMD-V is enabled in the BIOS and can be used.
Tags # VMWare Best Practices Continue Reading
By v�o l�c
Labels:

Tuesday, October 17, 2017

How to Update the BIOS of the ESX/ESXi host?

Tuesday, October 17, 2017 0

Updating the BIOS of the ESX/ESXi host

The steps required to update firmware or a system BIOS varies depending on the hardware vendor and the component to be updated. Typically, the vendor will supply some type of utility that will update the component automatically.

For example, to update a motherboard's BIOS:

Notes:

    Before performing this procedure, ensure to migrate the virtual machines and appliances in the ESX/ESXi host.    

    This a only an example. The results may vary from each manufacturer.

 1. Download the update utility from the vendor.

 2. Create a bootable floppy disk or CD/DVD-ROM that contains the utility.

 3. Physically be in front of the server that hosts ESX/ESXi.

 4. Reboot the host.
   
 5. Access the BIOS of the server.
    Note: You may access the BIOS by pressing F2 or DEL. However, this varies depending on the vendor and is usually displayed on your screen.

 6. Find the System Information section of the BIOS. The location varies depending on vendor.

 7. Note the BIOS version and any other relevant information before upgrading.

 8. Ensure that your BIOS is capable of booting from a floppy or CD/DVD-ROM.

 9. Place the floppy or CD/DVD-ROM in the server and reboot the system. 

 10.Boot from the device and follow the on-screen instructions to update the hardware.

 11.Verify if the firmware/BIOS has been updated.

 12.Proceed with the ESX/ESXi installation or upgrade.
Tags # VMWare Best Practices Continue Reading
By v�o l�c No comments:
Labels:

Monday, December 28, 2015

Configuring Network Time Protocol (NTP) on ESX/ESXi hosts using the vSphere Client

Monday, December 28, 2015 0
This Blog  provides steps to enable Network Time Protocol  (NTP) on an ESX/ESXi host using the vSphere Client.

To configure NTP on ESX/ESXi 4.1 and ESXi 5.x hosts using the vSphere Client:
  • Connect to the ESX/ESXi host using the vSphere Client.
  • Select a host in the inventory.
  • Click the Configuration tab.

  • Click Time Configuration.
  • Click Properties.
  • Click Options.


  • Click NTP Settings.
  • Click Add.
  • Enter the NTP Server name. For example, pool.ntp.org.
    Note: When entering the multiple NTP Server names, use a comma (,) followed by a space ( ) between the entries.
  • Click OK.
  • Click the General tab.
  • Click Start automatically under Startup Policy.
    Note: It is recommended to set the time manually prior to starting the service.
  • Click Start and click OK.
  • Click OK to exit.
Tags # VMWare Best Practices Continue Reading
By v�o l�c No comments:
Labels: