@cabli01
how big is your pool?
We have 800 VMs spread across 16 UCS blades. Our average failure rate was around 15%.
↧
Re: VDPCONNECT_NETWORK_FAILURE Agent Unreachable
↧
Re: VDPCONNECT_NETWORK_FAILURE Agent Unreachable
in our case the lock up was caused by a poorly coded driver which was creating a dead lock.
↧
↧
Re: Workstation 15.5.5 performance hit
@bkraul78 Unfortunately we couldn't reproduce this issue in-house. if possible, could u help collect some logs for us ? And we'll send it to developer to have a look.
Please noted to enable the debugging logging, you can change the log level by VM setting -> Options -> Advanced -> Gather debugging information -> Set the value to Full.
And upload the vmware.log and statistic folder to us. Many thanks for your help
↧
Re: Audio problems with RTAV in video conferences
It's hard to tell w/o further debug or looking into logs.
↧
Re: After Fusion 11.5.0 upgrade, no usb devices recognized
Honestly this is becoming a joke. Everything working, then update and BOOM USB functionality dead and requires a hack ( that has not worked for me ).
With many people complaining of the same/similar issue, how could this not be something found in QA process before a release of a sub-version.
I've spent hours trying to get this working again and then gave up and mounted the drive I needed through "file share" and then subst in windows to get a drive letter so I could continue to work.
I've been using Fusion for YEARS and of late this has been a disaster.
Same issue caused me to update OSX version months ago to see if that was the issue which it wasn't. I want to be able to mount my USB devices like I should be able to and is supposed to be supported.
Who's issue is this ? VMwares, OSX or running win10 as a guest ?
↧
↧
Re: Workstation 15.5.5 performance hit
Thanks for your effort on the investigation. I have couple of questions about your test environment.
- HOST information, like CPU type/Memory/Host OS version/Hyper-V status/new installation or upgrade/UEFI or BIOS/WSL status
- Guest information(OS type/OS version/new installation or upgrade/UEFI or BIOS/Disk type)
- VMware.log and vm-supported data
- Describe what you did when the issue happened
↧
Re: DRS Does Not Work with Specific ESXi Host...
Actually, I did't test vmking to vMotion kernel, but vMotion Host 4 to Host 5 is successful..!
They are in Shared storage
↧
Re: After Fusion 11.5.0 upgrade, no usb devices recognized
Same problem again after this update 11.5.5. Fusion is calling me in a day to fix. In the meantime, I downgraded back to 11.5.3 and it works
Frustrating !!!
↧
Virtual machine fine for months. Added a 2nd VM (as a test), ever since first VM "no network access" (Windows Server 2016)
I searched VMWare troubleshooting docs and tried ALL of the steps, and searched here. Surprised I didn't find a solution so here goes:
VMWare Workstation Pro v15.5. Running a single VM just fine (Windows Server 2016 Standard).
I recently added a second VM, a Windows Server 2003 Standard as a proof of concept only, it will never (hopefully) need to run on this host. This new VM was running on VMWare Player v6.x, I used the latest (v6.2.0) VMware vCenter Converter Standalone to "upgrade" it to the latest VMware it would convert to (hardware version 11 I recall). The new VM started up and a cursory check was fine. Since it was a test of a old but still running VM on another host, I changed networking to "Host only". I've since "removed" the new VM from VMware Workstation.
Now the original VM that was running flawlessly shows "no network access". I've tried everything I can think of! All appears fine with networking - the adapter is enabled and shows "connected", it has it's static ip address and all other pertinent network settings. The host's networking is fine, fully in production. The symptoms are simply "no network access", the tray icon has a yellow "!", the "network" is shown as an "Unidentified Network", "Public", Access Type: no network access" on "Ethernet0" adapter. Looking at the properties, everything appears correct. There is activity shown there, network traffic being sent a bit, and received a lot less but at least some. I can ping the loopback address but nothing else.
The network setting for the VM is Bridged (not checked "Replicate physical network state") as it always has been. "Connected" and "Connect at power on" are checked.
I've reverted the VM back to quite a few known good previous snapshots, including all the way back to near the beginning of the build - no luck. Uninstalled, reinstalled VMware Workstation. Allowed the upgrade from v15.5 to v15.5.5. Performed every trick in the book I know of resetting networking with netsh and even the "reset network" in the O/S GUI. No glaring items of interest are in the System or Application logs of either the host or the VM having the problem.
I've seen so tried "adding" a network adapter "Intel Pro 1000/MT" nic (replacing the original "Intel 82574L Gigabit network connection), that flunked with the new adapter reporting the hardware cannot start. Update driver for the original nic yields no available newer drivers. I've tried disabling the Windows firewall, uninstalling the Avast anti-malware software (ONLY the remote control module was installed anyway), and that's been solid since the beginning and on many other systems under my care. I've tried regenerating the MAC address for the VM. I'm still stuck!
↧
↧
vROPS 8.1
Hello Folks,
We have vROPS 8.1.0 ( 15972145 ) version. When I try to open VAMI with port 5480 I'm unable to browse to it. I need to patch this appliance. Any idea please? Or is there any other procedure to patch this?
TIA,
↧
VMs Under Vcenter 5.5 and With ESXi Vcloud License using Distributed Switch for VMwork load would like to Migrate to Vcenter 6.7 Standard License using Standard Switch
Best recommended Procedure with impact to VMs
Source:
Vcenter Server:5.5
ESXi Host:5.5
Distributed switch used for VMs with (Licensing Model: VCLOUD License)
Destination:
Vcenter Server:6.7
ESXi Host:6.7
Configuration is standard Switch (Licensing Model:Standard License)
↧
Re: Invoke-VMScript : Invoke-VMScript A general system error occurred: vix error codes = (1, 0).
LucD,
How can I get the report1 output in the same import file (adding new columns for RDP Status and Count) rather than creating a new file ?
↧
Re: No 3D support available from host
Your comments were very helpful, I updated the X11 configuration and started the X server on display 0 with Nvidia GPU.
Currently I don't get the message of no 3d support when opening the VM , but only when I invoke Vmware as root , when I open Vmware with other user permissions .. I still get the message.
Do you have an idea about this ?
↧
↧
Re: No 3D support available from host
I compared the vmware.log in both cases , it seems that as root , vmware keep searching for displays till it find (unix:0.0) display with Nvidia GPU and so it supports 3d.
For the other user , it just check the display I run on (VNC session) which is in my case :1
↧
I have used the raw device mapping (RDM) apporach to put a Self Encrypting Drive SSD in passthrough to my Centos 7.2 guest VM, but it fails to accept the hdparm security-unlock command: "bad/missing sense data". Has anyone encountered this, found resolu
I've a 480G Self Encrypting Solid State Drive that I want to make exclusive passthrough to a centos 7.2 guest VM. This OS is meant to be the unlocking gate-keeper for data on this SSD which gets NFS and samba made available to other network connected VMs and physical machines.
Following the approach noted in https://www.vm-help.com/esx40i/esx41/creating-rdms-on-sata-drives , I was able to successfully "see" the drive in the booted VM guest:
[root@GPP0 ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 6G 0 disk
├─sda1 8:1 0 200M 0 part /boot/efi
├─sda2 8:2 0 250M 0 part /boot
└─sda3 8:3 0 5.6G 0 part
├─centos_gpp0-root 253:0 0 5G 0 lvm /
└─centos_gpp0-swap 253:1 0 616M 0 lvm [SWAP]
sdb 8:16 0 447.1G 0 disk ß my test drive is a 480G
smartctl works to reveal details of drive:
Model Family: SandForce Driven SSDs
Device Model: HR3A2X0480AICC1
User Capacity: 480,103,981,056 bytes [480 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS, ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
within the ESXi host its listed this way:
[root@localhost:~] esxcli storage nmp device list
t10.ATA_____HR3A2X0480AICC1_____________________________________6G0005PR
Device Display Name: Local ATA Disk (t10.ATA_____HR3A2X0480AICC1_____________________________________6G0005PR)
Storage Array Type: VMW_SATP_LOCAL
Storage Array Type Device Config: SATP VMW_SATP_LOCAL does not support device configuration.
Path Selection Policy: VMW_PSP_FIXED
Path Selection Policy Device Config: {preferred=vmhba0:C0:T0:L0;current=vmhba0:C0:T0:L0}
Path Selection Policy Device Custom Config:
Working Paths: vmhba0:C0:T0:L0
Is USB: false
I can use the Hdparm –I /dev/sdb and it returns information. Including ATA security info:
. . .
Security:
Master password revision code = 3
supported
enabled
locked
not frozen
not expired: security count
supported: enhanced erase
Security level high
2min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 538c9a9000001bf4
NAA : 5
IEEE OUI : 38c9a9
Unique ID : 000001bf4
Checksum: correct
BUT issuing the hdparm security unlock command returns:
[root@GPP0 ~]# /usr/sbin/hdparm --user-master u --security-unlock localpassword /dev/sdb
security_password="localpassword"
/dev/sdb:
Issuing SECURITY_UNLOCK command, password="localpassword", user=user
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0b 00 00 00 00 24 00 00 c0 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
so no further operations to fdisk, or file, etc. will work and the drive cannot be mounted for use.
fdisk: cannot open /dev/sdb: Input/output error
I've also attempted steps from
https://kb.vmware.com/s/article/2013188 to ensure the LUN appears as a SSD, with same results.
One last capture from the ESXi host, maybe someone can point out if there are other adjustments that this might reveal that should/could be made to allow the unlock command to work.
[root@localhost:~] esxcli storage core device list -d t10.ATA_____HR3A2X0480AICC1_____________________________________6G0005PR
t10.ATA_____HR3A2X0480AICC1_____________________________________6G0005PR
Display Name: Local ATA Disk (t10.ATA_____HR3A2X0480AICC1_____________________________________6G0005PR)
Has Settable Display Name: true
Size: 457862
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/t10.ATA_____HR3A2X0480AICC1_____________________________________6G0005PR
Vendor: ATA
Model: HR3A2X0480AICC1
Revision: 2518
SCSI Level: 5
Is Pseudo: false
Status: on
Is RDM Capable: false
Is Local: true
Is Removable: false
Is SSD: true
Is VVOL PE: false
Is Offline: false
Is Perennially Reserved: false
Queue Full Sample Size: 0
Queue Full Threshold: 0
Thin Provisioning Status: yes
Attached Filters:
VAAI Status: unknown
Other UIDs: vml.01000000002020202020202020202020203647303030355052485233413258
Is Shared Clusterwide: false
Is SAS: false
Is USB: false
Is Boot Device: false
Device Max Queue Depth: 31
No of outstanding IOs with competing worlds: 31
Drive Type: unknown
RAID Level: unknown
Number of Physical Drives: unknown
Protection Enabled: false
PI Activated: false
PI Type: 0
PI Protection Mask: NO PROTECTION
Supported Guard Types: NO GUARD SUPPORT
DIX Enabled: false
DIX Guard Type: NO GUARD SUPPORT
Emulated DIX/DIF Enabled: false
Suggestions or insights?
fdisk: cannot open /dev/sdb: Input/output error
↧
Re: vSAN online health alarm 'Thick-provisioned VMs on vSAN'
Hi Lucasberndsky,
I'am understanding what you are saying. But these disks where thick-provisioned due a failure in vRA blueprint So we do have thick-provisiod disks on vSAN as the vCenter alarm displayed. If a thick provisioned disk is needed we do have a storage police with the Object Space reservation is 100. And yes it's a challange to make the disk thin provisioned if a cluster have only one vSAN datastore and planning downtime for a vm to clone is difficult.
So we're thinking the create a small temporary cluster in the same vCenter with the same vMotion network. Then it's possible to do a vMotion/storage vMotion to this cluster and back to the vSAN cluster with the correct storage policy.
With the following Powershell one-liner I created an overview of disks that are thick-provioned.
$thick_provisioned_servers = Get-Datastore | Get-VM | Get-HardDisk | Where {$_.storageformat -eq "Thick" } | Select Parent, Name, CapacityGB, storageformat, ConnectionState | Export-Csv "d:\temp\\thick_provision_vmdk.csv" -NoTypeInformation
Thank you for reply!
Vincent
↧
Re: Virtual machine fine for months. Added a 2nd VM (as a test), ever since first VM "no network access" (Windows Server 2016)
Please read the 2nd Known Issue in VMware Workstation 15.5.5 Pro Release Notes
Your Virtual Network Editor should look like the attached image, listing 3 virtual networks.
↧
↧
Set Management Interface Through CLI
Author : Chris Bedford
Topic Name : Choose Network Adapters for the Management Network
Publication Name : vSphere Installation and Setup
Product/Version : VMware vSphere/6.0
Question :
How can I configure the management interfaces through the console? I am trying to automate building esxi hosts that use vmnic5 as the management interface and all other interfaces should not be used for management.
↧
Re: Host CPU Power Usage and Power Usage Trend is Very High when Running VMware workstation V15.5.5 (windows 10- 64Bit)
Your host CPU usage is not "very high".12% or higher is quite normal if the guest is busy, for example installing OS updates. Try running the task manager in the guest and see what keeps it busy. When the guest CPU usage drops at ~0%, the VMX process in the host will also drop to ~0%.
If the problem persists, as a precaution make sure don't overprovision your VM - try reducing the number of CPU cores and limit RAM to 4GB.
↧
Re: VMWare 15 Pro -- The operation was cancelled by the user
From your snapshot I see you have provisioned 15.6 GB or RAM to the guest - how much RAM do you have in your host?
Also, try reducing the RAM allocated to the VM, it may help troubleshoot the problem.
↧