Hello Carl,
Have you tried running Wireshark on the Server 2016 VM? It would narrow down if the issue is at the VM.
To troubleshoot at an ESXi level, look at Monitoring network traffic from within a virtual machine on a VMware vSphere ESX/ESXi server (1038847) | VMware KB
The ESXi versions are dated in the KB though I cannot think of any that do not apply still (May need the Web Client to complete some steps).
Hello,
Refer more on Understanding IP Multicast in ESXi,
Understanding IP Multicast in ESXi/ESX (2044735) | VMware KB
I have ESXi 6.5 (5969303), and I am using VMware Remote Console 10.0.1 build-5898794
I have built a Server 2012 R2 VM and the pre-VMware Tools Mouse performance is SO BAD as to render this console unusable! In reality, I was able to install the tools by tabbing through all the screens (time-consuming, frustrating and nearly impossible as W2K12 is not really deigned around pre-mouse KVM systems).
The basic issue is latency and speed. The smallest possible amount I can move my actual (physical) mouse causes the pointer to fly all the way across the screen. Highlighting a single icon or button is not almost, but fully impossible!
Is there a way to slow down the mouse using a Virtual Machine option in the *.vmx of the VM?
THX
I'm currently not aware of a limit regarding the number of local users. Why don't you simply go ahead and create the users you need, to find out whether it works.
André
In this case.
solutions1:-
delete the VM from host and re-register to host again. if it is successful, check for the snapshots and delete it.
Solution 2:-
. if the above case not resolving the problem, please follow below steps
- Checked for locks using vmkfstools –D on the parent vmdk and showed the mac address of the local host.
- Ran lsof command to see if we could kill the process with the current file lock
- Kill -9 of the process could not be ended as there was a lock that couldn’t be removed.
- Rebooted the host that contained the VM.
- Once the host was rebooted, the VM was still not starting stating it couldn’t open the parent disk vmdk.
- Reviewed the descriptor file for the snapshot disk and parent disk vmdk file and found that the CID in the parent vmdk was not matching what the snapshot vmdk was calling.
- Changed the CID on the parent vmdk to match what was in the snapshot descriptor file and VM powered on.
- VM would not connect to the network as the IP information of the nic were gone.
- Once we were able to login directly to the VM, we were able to set the IP address
- Rebooted the VM and validated all services were started and user could log in with domain credentials
Unfortunately my problem doesn't appear to be with the client. I've installed multiple versions of MSM with no luck. I can also see that my hosts don't show the "Storage" disk health under their health status section either. Oddly, they are discoverable by any MSM version, I just can't login.
When I attempt to login, I see SYN packets going to the hosts on 3071. The process lasts for 12 hours with no change
You want to create a normal virtual disk backed up by a VMDK on a standard datastore and configure it in such a way that the guestOS perceives it as a USB-device ?
Yes.
The way to do it would be to add a USB controller, and under that, "add device" which is a virtual HDD (VMDK). Only that it seems there's no option to add such under those controllers, which might mean either of (a) you're right or (b) there's a CLI "advanced" way to do it still.
Or are you saying authoritatively that this is not supported in ESXi? (there's support for it in other virtualization products).
Thanks!
That procedure doesn't work as described. I copy the vmdk from the kvm host and run "vmkfstools -i `pwd`/myvm-temp.vmdk -d thin myvm.vmdk" and I do not end up with a large flat file and a small vmdk config file. I end up with a small vmdk config file that contains a reference to a VMFS file:
# Extent description
RW 41943040 VMFS "vsan://e911b759-a4fe-21cd-6d0a-0cc47ad3960a"
As far as I can tell that object does not exist; importing the small vmdk config file results in a bad VM.
This procedure does not work either:
- Use the vmdk file brought over from qemu-img convert.
- Create a VM, delete the SCSI disk and SCSI controller, you are stuck using the vmware IDE driver.
- Use the vmdk file brought over from qemu-img convert as your disk.
- Bad VM is result.
By "Bad VM" I mean a VM that won't even boot into BIOS, it just displays a message "Press any key to continue".
Hi Team,
need technical and expertice advice here.
I saw there is new security feature recommended since Vmware vpshere 5.5 which is the
possiblity to "create Timeout for Idle ESXi Shell Sessions "
by go to UserVars.ESXiShellInteractiveTimeOut field, enter the availability timeout setting.
this helps increase the security where if user login the ESXi Shell on a host via putty, but forgets to log out of the session,
the idle session remains connected continuously.
The open connection can increase the potential for unauthorized access.
but my engineering team has rejected my idea on this . reason they given is that
sometimes admnistrator use SSH (using putty)sessions to copy data (VMs, memory dumps) and etc.
it said during this activity there is no key-strokes are being sent to session
andd therefore the session will be terminated. it caused the process running behind got interrupted and stopped
Is that true that background process running behind such as copy data will be terminated
due to the exit of the putty/esxi shell session after the timed out session ? I thought it is indepedent?
hope to get expertise explaination and confirmation on this area.
your help is much appreciated.
The blog and KB might give you a fair understanding of vmfs mechanism Linux based file systems become read-only (51306) | VMware KB and VMFS Locking Uncovered - VMware vSphere Blog
To Preface - I've been working with VMWare since around the 3.5 days. I'm very much a 'fan' of the C# client, and really hate the 'new' Flash based Web client. Well, here's my first real major issue with the web client (other than it's slow, clunky, and has various crashes/faults that require a reload orders of magnitude more often than the C# client's NEVER... Other than cases where a host that the client was directly connected to rebooted, I can't recall ANY time it had ANY issue).. Anyway, back on track - I want to remove a VMFS5 datastore and then re-create it as a VMFS6 datastore, since VMFS5 can't be migrated to VMFS6 like previous VMFS versions. I've removed and deleted datastores many times in the past. Put the datastore offline, and if for some reason something was missed that would prevent that, it'll tell you before you can ever put it offline. Otherwise, the store goes offline, and from there, delete it and have a nice day.
With the web client, however, I have absolutely no idea what it's complaining about. There is literally NOTHING on the datastore. I can put it offline, for both my hosts that access it, and it goes offline/inactive with no warnings or issues - I went so far as to look at all the machines that were originally on the datastore (prior to moving them off it) for machines with snapshots and removed them all - still no bueno.
So I'm at a point where there is NOTHING on the datastore and there are NO snapshots of any kind even remotely associated with the datastore (even though 'in theory', a storage vMotioned machines snapshots shouldn't care about the previous datastore), but yet the junky web client is not letting me delete the store, and not giving me the slightest clue what it's complaining about.
So anyone have any ideas how I can delete this datastore, since it sees to think it's in use, despite the fact that I manually deleted everything that was remaining on the DS, and after which there's NOHTING on it, and ALL snapshots that MIGHT be able to cause issues are consolidated into the VMs?
Side 'plea' : Bring back the C# client!!! The web client just plain sucks. Bad. Beyond bad. The C# client was flat out reliable. The Web Client is hit or miss. At best. And dismally slow in comparison, coming from someone that has been working with VMWare since the 3.5 days. I simply can't stress how much better, faster and more RELIABLE the C# client was than the web client. And I personally know of others that WILL NOT 'upgrade' to 6.5 due to the termination of the C# client. The Web client is an OK option for day to day simple stuff, but at the and of the day, the C# client is beyond orders of magnitude better than the web client for anything other than the simplest console (and console is debatable with how it interacts with firefox), shutdown or reboot of VMs. At this point, I have zero intention of 'upgrading' my production, customer facing environment from 6.0 to 6.5 (at this point, I'd need some insanely ridiculous enhancements in 7.0, INCLUDING the return of the C# client, to go beyond 6.0) - and the performance and reliability of the web client vs the C# client is just... NO. The performance ''suggestions' of VMFS 6 over VMS5 are 'enticing', but considering the drawbacks... Nope. So bring back the C# client. As it was. Forever (and as far as I'm concerned, leave the web client as an option). But let the vastly superior management option continue.
Hi André,
thanks for your response.
I tried to create users and it works, so at least it's not limited by software. But I was not sure if there is any license limitation, so I asked here. We will see if somebody will have more information regarding this.
Jan
Hi
Check if SIOC is disabled on that datastore.
BTW: to find more details first you should check vpxd.log.
Thanks for share.
Virsh is my favorite cmdline for KVM management. You may wonder if there is sth similar for VMware or want to run VMware without GUI. Here is goes – vmrun.
0. VIX API
VIX API allows users to automate the management of VMs, such as APIs used to start/stop VMs. It supports most products from VMware, including Player, Sever, Workstation, Fusion and vSphere (though VIX API is deprecated as there is a vSphere API).
1. vmrun
After VIX API is installed, you will have a powerful command – vmrun, which leverages the powerful VIX API to provide a similar command line interface for VMware-based VMs, like virsh for KVM.
Take VMware Player and its VMs for example:
# Start the VM without GUI
vmrun -T player start “path/to/yourVM.vmx” nogui
# Stop the VM
vmrun -T player stop “path/to/yourVM.vmx” hard
# List all possible commands supported by vmrun
vmrun -h
2. Issues
There is a command in vmrun – getGuestIPAddress, which is used to get the IP address of the guest VM. First, the VM needs to be started. Second, VMware tools are needed to make the functionality work.
Once you login the VM, you may find top does not work. The same case happens if you try to compile the kernel (make menuconfig). Adding the fix into .profile helps.
root@dave-desktop:~/lsms# top
‘xterm-256color’: unknown terminal type.
Fix: export TERM=xterm
We run an ESX environment and we face answering the question of taking snapshots prior to patching our Linux VMs. We don't experience the need to revert to a snapshot often but we have faced instances where a machine won't boot after patching or the developers' code won't behave well after upgrading a particular package in the box. Due to this fact, as a safeguard, my team is in the habit of taking snapshots prior to patching. I know, time consuming. Our reasoning is that reverting to a snapshot is quicker than any other available options: spending extra time in troubleshooting, yum rollback, or an unlikely restore from backup.
We have a staff member who tells us that he heard a VMWare expert say that snapshots should never be used, never ever should you take a snapshot prior to patching our Linux systems. I have not been able to find best practices where this use of snapshots is discouraged. Looking for answers...
Thanks in advance,
RV
Hello,
first of all i'm very beginner in vmware, i may ask dumb questions don't blame me please
I've tried ESXi hypervisor 6.5 (no vcenter) on a workstation, it's working well, i can update to 6.5 U1 by following this tuto
It's ok but it's just a lab, i want to install ESXi on a HPE server with the custom iso and i want to know how i can update ESXi for future update? can i use the previous tuto ? can i do "online" update ?
thanks
The issue ended up taking over 6 months to resolve.
I don't know if this was the official fix, but the last of my notes show that we completely removed and recreated ARRAY's and the LUN's on the SAN and used 256k for the Segment size when creating the Arrays.
This was a destructive event, but we had enough capacity to move all VM's to one array, destroy/recreate the other array, then move everything to the new array and destroy/recreate the second array.
The SAN ran stable for another 2 years and was replaced with a V3700 with SAS disks. The DS3200 is still in service at the DR site.
Hopefully this helps - I had hundreds of hours spent on this issue.
I am thinking to dont touch the current ESXI installation on server so i will buy new USB and try to install esxi and boot from new USB. so with this way - i think i will have an option of fast rollback.
anyone see any problem with it?
Yes you can use the same tuto, but I would recommend you to follow official VMware docs. Ok, the point here is the upgrade process is same for Custom image and Vmware GA image.
You should make sure that if your current ESXi is custom build then you should upgrade with custom build image from same vendor.