Quantcast
Channel: VMware Communities: Message List - ESXi
Viewing all 28826 articles
Browse latest View live

Ways to speed up the login page?

$
0
0

We support a few remote locations with very slow, high latency internet links. One issue has kept us with ESXi 5.5 and the fat C# client. The login page on ESXi 6.5 takes over 8 minutes to load, before you can type in your password. Even then, it doesn't actually login, just gives an error, which varies between timeout and lost connection, then it boots you back out again.

 

I can see a steady stream of data coming from the host via resource monitor, but it tops at 15Kb/sec. The link we're working with is a 600Kb/sec link and 300ms latency; this is under ideal conditions, which is rarely the case.

 

I can sort of replicate this with Workstation running a nested ESXi host. I've ruled out the site-to-site VPN being an issue, but going direct to the https port and nothing actually changes. I'm hoping someone will have had experience with this and would have any ideas on how to better cope with the low-speed & high latency combination.

 

Bill


VMs on NAS

$
0
0

Hi,

 

I am having issues with my VMs corrupting every couple of days on an ESXi bare metal setup.

 

I have about 7 or 8 VMs, one is a domain controller (windows server 2012), and the rest are dedicated workstations for groups of applications (windows 10), and one Linux Ubuntu VM.

 

I have had the most corruptions on the domain controller, but the others including the Linux machine have almost all corrupted at some point, which usually has resulted in me having to do a fresh install or full VM restore from a weekly backup.  By corruptions, I mean the OS tries to start goes into some sort of repair mode, or error mode, etc., and cannot load the OS, even in safe mode.

 

The VMs are stored on a NAS.  The NAS is split up into a iSCSI LUN with Thick Provisioning for my VM datastore, and the rest is just for simple network file storage on a separate volume.  The NAS is set up for RAID 5 and also has a scheduled backup every week onto a USB locally attached HDD.  The corruptions do not seem to coincide with the backing up of the LUN, they just seem random.  The NAS itself I would say is working fine, since there are no faults/errors, and all of my other file storage has had not issues.

 

Any ideas what could be causing this?

Re: Dell R740 With ESXi 6.5 Problems

$
0
0

try switching your memory modules and cpu between sockets.

Add snapshot option "workingDir" via the ESXi WebConfigurationInterface fails.

$
0
0

Hi,

 

due to our storage layout it is advantageous for us to have the snapshots created on HDDs and not SSDs. Mainly Snapshots are created during Backup Hours or Upgrades so the performance impact is acceptable. I also decided to move the swap file of some VMs to da dedicated location.

 

VMWare lists the following options for the vmx config file:

 

workingDir = "/vmfs/volumes/587939d7-a30f66a9-23a1-ecf4bbe1a868/snapshots/srv"

snapshot.redoNotWithParent = "true"

sched.swap.dir = "/vmfs/volumes/587939d7-a30f66a9-23a1-ecf4bbe1a868/swapdir/srv"

 

The host is running ESXi 6.5 with the latest 20180502001-standard bundle. When I clicked around the VM-Options on the ESXi Webinterface I found that neat and handy config file editor where you can edit and add vmx options.

 

I had no troubles adding those two lines:

snapshot.redoNotWithParent = "true"

sched.swap.dir = "/vmfs/volumes/587939d7-a30f66a9-23a1-ecf4bbe1a868/swapdir/srv"

 

however the

workingDir = "/vmfs/volumes/587939d7-a30f66a9-23a1-ecf4bbe1a868/snapshots/srv"

line won't get saved or persist after applying the change.

 

When I edit the vmx file via ssh and vi I can add the workingDir (reregister the vmx) but it still won't show in the ESXi Webinterface (however the option is persistent in the vmx file saved)

 

Is there a reason why this specific configuration option has to be done using a manual vmx edit? Editing and reregistering is not too complicated but opening ssh etc. are just a couple of more steps instead of just punching the parameters in the webui

 

regards,

 

Fabian

vim-cmd diskaddexisting scsi1 1 attempts to add existing vmdk into scsi0 and fails

$
0
0

For automation, I use vim-cmd  utility to add existing devices as hot add into VMs.

Before running below command there are disks attached to ScsiController 0 with unit id 1,2,3,4,5,6 and when i try to add a next device for Scsi controller 1 with unit id 1 it fails,

Cmd - vim-cmd vmsvc/device.diskaddexisting 3  /vmfs/volumes/esx_ld7/esx_ld7_1527840895.vmdk scsi1 1

Failed: Reconfigure failed

 

When I started looking for exact issue as per the hostd.log,

2018-06-01T13:22:12.563Z warning hostd[2099399] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5b10f081-1bc2e1d0-c444-98f2b3f236a6/Deploy_VMWin/Deploy_VMWin.vmx opID=vim-cmd-5e-3819 user=root] The specified controller slot is already occupied by Hard Disk 2: (vim.vm.device.VirtualDisk) {

-->    key = -1,

-->    deviceInfo = (vim.Description) null,

-->    backing = (vim.vm.device.VirtualDisk.FlatVer2BackingInfo) {

-->       fileName = "[] /vmfs/volumes/esx_ld7/esx_ld7_1527840895.vmdk",

-->       datastore = <unset>,

-->       backingObjectId = <unset>,

-->       diskMode = "persistent",

-->       split = <unset>,

-->       writeThrough = <unset>,

-->       thinProvisioned = <unset>,

-->       eagerlyScrub = <unset>,

-->       uuid = <unset>,

-->       contentId = <unset>,

-->       changeId = <unset>,

-->       parent = (vim.vm.device.VirtualDisk.FlatVer2BackingInfo) null,

-->       deltaDiskFormat = <unset>,

-->       digestEnabled = <unset>,

-->       deltaGrainSize = <unset>,

-->       deltaDiskFormatVariant = <unset>,

-->       sharing = <unset>,

-->       keyId = (vim.encryption.CryptoKeyId) null

-->    },

-->    connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,

-->    slotInfo = (vim.vm.device.VirtualDevice.BusSlotInfo) null,

-->    controllerKey = 1000,

-->    unitNumber = 1,

-->    vDiskId = (vim.vslm.ID) null,

-->    virtualDiskFormat = <unset>,

-->    nativeUnmanagedLinkedClone = <unset>

--> }

2018-06-01T13:22:12.564Z warning hostd[2099399] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5b10f081-1bc2e1d0-c444-98f2b3f236a6/Deploy_VMWin/Deploy_VMWin.vmx opID=vim-cmd-5e-3819 user=root] Method fault exception during reconfigure: N3Vim5Fault17InvalidDeviceSpec9ExceptionE(Fault cause: vim.fault.InvalidDeviceSpec

--> )

--> [context]zKq7AVICAgAAAJz7cgAVaG9zdGQAAEyZNWxpYnZtYWNvcmUuc28AAADAGwBgsBcB/1r9bGlidmltLXR5cGVzLnNvAIGiMRYBgc6GFgGBoLIWAYEutBYBgX6fEgECYotlaG9zdGQAAsoZuwJe6a4Cw+2ugTVDAQECkcLBAonLwQD1LygA0zMoAAsPNgNrgABsaWJwdGhyZWFkLnNvLjAABJ2ZDmxpYmMuc28uNgA=[/context]

2018-06-01T13:22:12.579Z info hostd[2099399] [Originator@6876 sub=Vimsvc.TaskManager opID=vim-cmd-5e-3819 user=root] Task Completed : haTask-3-vim.VirtualMachine.reconfigure-2656923718 Status error

 

Surprisingly,

When I ran below command it passed and added the disk against SCSI controller 0, not 1

vim-cmd vmsvc/device.diskaddexisting 3  /vmfs/volumes/esx_ld7/esx_ld7_1527840895.vmdk scsi1 8

 

As per .vmx file entries are,

scsi0:8.deviceType = "scsi-hardDisk"

scsi0:8.fileName = "/vmfs/volumes/5b10f551-104555a6-b83b-98f2b3f236a6/esx_ld7_1527840895.vmdk"

scsi0:8.present = "TRUE" 

scsi0:8.redo = ""      

 

Can anyone please guide me here, there seems to be some issue.

Re: vim-cmd diskaddexisting scsi1 1 attempts to add existing vmdk into scsi0 and fails

$
0
0

Does the second scsi-controller already exists before you run the command ?
Make sure you already have
scsi1.present = "TRUE"
I also think your syntax is incorrect - try
vim-cmd vmsvc/device.diskaddexisting 3  /vmfs/volumes/esx_ld7/esx_ld7_1527840895.vmdk   1   1

Re: Guest OS to vCenter Performance Monitor - Memory Reporting Mismatch

$
0
0

Hi, I came across this thread again from a while back. Did you ever get to the bottom of it?

Re: ESXi 6.5.0 - Datastore lost

$
0
0

I ran a series of tests to hard drive and it turns out that some blocks are defective. He does not pass the tests.
I opened an RMA with Western Digital.


Add USB Device grayed out in ESXi 6.7

$
0
0

Team,

 

Any idea why "Add USB Device" would be grayed out in the VM's configuration within the ESXi Embedded Host Client?  I've tried multiple operating systems, USB 3.0 and USB 2.0 controllers, etc. but for some reason my WD Pa$$port USB HD device never shows up in the client.  I've also tried other basic USB devices.  Are there any troubleshooting steps I can take to see where the issue is?

 

Thanks,

Brad

Re: ESXi 6.5 -> ESXi 6.7 Upgrade fails to boot with Trusted Execution enabled in BIOS

non-compliant host - can't upgrade or install patches

$
0
0

I think i may have at some point manually installed some VIB on this host (but can't remember) and now I can't upgrade it from 6.0 to 6.5 .. i'm seeing errors in the logs such as:

 

2018-06-02T06:41:24Z esxupdate: 71318: esxupdate: ERROR: An esxupdate error exception was caught:

2018-06-02T06:41:24Z esxupdate: 71318: esxupdate: ERROR: Traceback (most recent call last):

2018-06-02T06:41:24Z esxupdate: 71318: esxupdate: ERROR:   File "/usr/sbin/esxupdate", line 239, in main

2018-06-02T06:41:24Z esxupdate: 71318: esxupdate: ERROR:     cmd.Run()

2018-06-02T06:41:24Z esxupdate: 71318: esxupdate: ERROR:   File "/build/mts/release/bora-4887370/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esx5update/Cmdline.py", line 148, in Run

2018-06-02T06:41:24Z esxupdate: 71318: esxupdate: ERROR:   File "/build/mts/release/bora-4887370/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximage/Transaction.py", line 262, in InstallVibsFromSources

2018-06-02T06:41:24Z esxupdate: 71318: esxupdate: ERROR:   File "/build/mts/release/bora-4887370/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximage/Transaction.py", line 382, in _installVibs

2018-06-02T06:41:24Z esxupdate: 71318: esxupdate: ERROR:   File "/build/mts/release/bora-4887370/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmware/esximage/Transaction.py", line 436, in _validateAndInstallProfile

2018-06-02T06:41:24Z esxupdate: 71318: esxupdate: ERROR: vmware.esximage.Errors.DependencyError: VIB Extrasphere_bootbank_extrasphere_3.2.2142_1.3.284 violates extensibility rule checks: ['(line 25: col 0) Element vib failed to validate content']

 

any idea how I can fix this or just force it to upgrade?

Re: Add USB Device grayed out in ESXi 6.7

$
0
0

I SSH'd to the ESXi server and ran the following command which showed that the USB device is connected but also showed that the usbarbitrator service wasn't running.

 

esxcli hardware usb passthrough device list

 

I would have expected this service to be running by default as part of the ESXi install, but in any case I enabled it by running the addition command below which resolved the issue.

 

/etc/init.d/usbarbitrator start

VM power on error

$
0
0

when i power on vm i get the mention error The redo log of 'XXXX.vmdk' is corrupted. If the problem persists, discard the redo log

Re: VM power on error

$
0
0

Welcome to the Community,

 

please provide more details.

  • How much free disk space do you have on the datastore?
  • Run ls -lisa from the command line in the VM's folder, and post the output in your next reply.
  • Compress/zip the VM's configuration (.vmx) file, the .vmsd file as well as the vmware*.log files, and attach the resulting .zip archive to your reply post.

 

André

Re: VMs on NAS

$
0
0


Re: Another "unable to create datastore" issue...

$
0
0

Problem solved.  I've installed an H220 HBA and moved all the SATA disk over to it.  Immediately I could create datastores on all of these drives.

 

Based on this experience along with what I've read elsewhere, a P420 + HBA mode = a bag of hurt.

Re: vCenter 6.7, ESXi 6.7, and Horizon 7.4 compatibility

$
0
0

I also tried Horizon 7.5 with VCSA 6.7 and didnt work for Instant Clones. Not sure what the cure will be at the moment.

How to shutdown VMs during host poweroff, without using autostart

$
0
0

I have a scenario whereby I have a single ESXi host, and would like VMs to gracefully shutdown when a shutdown command is issued to the host.

 

For reasons I won't go into, I do not wish for VMs to autostart when the host is powered on.

 

Is it possible to configure autostart to stop VMs during a host shutdown, but not have them startup during host power on?

 

Cheers

Eds

Ubuntu (16.04/18.04) guest customization fails with open-vm-tools > 10.0 vSphere 6.5/6.7

$
0
0

Hey all - trying to get to the root of this issue. I am running vSphere 6.7 and a 16.04 LTS template (and testing with 18.04 as well). Even when running vSphere 6.5, if I did an apt-get upgrade and let the system bring all packages to the latest version in my template, customization fails. Right now, with open-vm-tools version 10.0.7 guest -customization works. If I upgrade open-vm-tools (or install 18.04 LTS) to version 10.2.0.1608 (build-7253323) guest-customization fails. The /var/log/vmware-imc/.. guest log files indicate a bunch of generic "can't lock file does not exist" but nothing descript.

 

Anyone else experiencing this issue?

 

Re: ESXI 6.5 Free License ?

$
0
0

Dear Brothe

I had some problem with WMware Exsi 6.5

When I had to deployed APp is finished

Storage have some status like picture bellow

Viewing all 28826 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>