Hi a.p.
I have the host connected to a cisco 3560cx running dchp pools for the vlans and no port security. i have other physical L2 switches branged off of this switch with no problems. the management IP for the host is connecting fine but when i build a new VM, like my WIN7 box, i do not get a network address.
here is what i have in the vSwitch. am i missing something?
i should also note that setting static IP address information does not work as well leading me to believe there is something wrong with the way i have the vsphere networking set up.
SOLUTION:
I look you search more complicated solutions, the life is more simple
Yes is possible and very easy to do. Without any vmware tool. Only looking the not virtual life. I named it THE REAL MODE.
If you have a disk of 150 Gb, but only have 50 Gb of information.
Steps:
1) Create a disk in vmware of 50 Gb and attach to the windows 2008 machine
2) Defrag in windows the 150 Gb machine
3) Boot from cd with a live cd iso like system GParted -- Live CD/USB/PXE/HD
4) Use Gparted to shrink the partition to 50 Gb from the 150 Gb disk you want shrink --> Now you have a 50 Gb partiton
5) Use Gparted to create partition msdos table to the new 50 Gb disk
6) Use Gparted to copy from 150 Gb the new 50 Gb partition to the 50 Gb disk
Now you have a 50 Gb with the original partition copied from the 150 Gb disk
7) remove the 150 Gb disk and configure the 50 Gb disk to set for example SCASI 0:0 or the primary sata or ide
Now you have your machine in a 50 Gb virtual disk
THE PROBLEM 8) And it's problem from windows 2008, now from this 50Gb the windows 2008 not boot, i don't have time to investigate, secure by boot config, but with a Windows 2008 Installation DVD ISO I start from it, and I made repair windows startup. With this solutioon windows 2008 boots correctly:
Boot from Windows 2008 ISO:
a) No install, select --> Repair Windows
b) Advanced Options
c) Startup Repair
8) After it Boot correctly, only automatic disk check for possible problems, but boot correctly.
I do this solution 2 times with the same good result.
Good luck!
Jorge Duran
Sorry for my English!
The same with Linux!
Ok, so i think i fixed it. the VLAN ID for the VM network was set to 20 (the vlan that it is connected to on the switch). i did that because i thought i read somewhere that it would tag the traffic for you in the case of trunking.
i changed it to 0 (to remove the ID) and then created a second vmkernal NIC to append the VM Network port group to. now the VM guests are online.
Great.
My next clarification would be, do i have to have a separate network for the guests (and a separate NIC), rather than just jumping on the management network?
Have you tried disabling the Syslog Collector Service? I had the same issue updating vCenter Server 6.0 to U2 and this worked out for me.
Not even a static IP configuration works?
You mentioned VLANs. Is the ESXi host connected to "Access", or "Trunk" ports on the Cisco switch? In case of "Tunk" ports, how did you configure the VM Port group? In case you set a VLAN-ID for the port group, make sure that it's not the ID of the Cisco ports default/native VLAN. Port groups with access to the physical default/native VLAN must not be tagged.
André
PS: Just read your latest reply after I posted my response. It seems I'm typing too slow. ;-)
VMkernel port groups are only required for host traffic. You can always add additional VM port groups to a vSwitch if you want.
André
how to disable this service?
Attached the logs
Seems like downloading update from online depot fills up your tmp storage resulting in above error. Just needed to enable the use of datastore for SWAP. Another workaround is to download the zip package to a datastore and install.
Running esxi 6.5 u1 on a 1 GB sdcard not a problem.
Hi Andre,
Thanks for you replies and the assistance! I will keep this in mind.
jason.
We fixed this for our R620 servers with Broadcom 5719/5720 NICs by disabling the ntg3 driver and enabling the tg3 driver. We also updated tg3 to the latest version. VMware support was well aware of this issue and stated they are seeing lots of problem with the ntg3 driver. All problems immediately ceased after changing the drivers.
Option #1 for me, not only is memory cheap it's the path forward to doing it properly. You can be a yes man for the boss, for these 'plugins' I'm often tempted to nod and carry out orders for amusement, unfortunately they're gone a year later and you end up cleaning up the mess anyway... so yea, stick to your guns with #1
6.5 Update 1.
I've just created VM from a Template, which I've done many times before. This time, I'm unable to launch the VM using "Launch Web Console". I am, on the other hand, able to launch the VM using "Launch Remote Console" The error that I'm receiving is detailed below.
I have other VMs in my environment that are launching fine with the web console. I've even deleted the VM and recreated a new one using the template without success. Any ideas as to what might be causing this. I've restarted the VM. I've deleted a VM and recreated it.
What is necessary to tell ESXi to use a gatewayless /32 address for the web configurator?
I help run a small gaming community on a datacenter server. I have no access to the server's keyboard console. We are trying to switch to ESXi with the free license, but I am having huge problems trying to get this to work.
We have a single "normal" /30 IPv4 address plus an additional "gatewayless" /32 IPv4 address. In order to use the /32 address it needs to be routed through the /30's gateway.
IP: 72.20.9.126
NM: 255.255.255.252 (/30)
GW: 72.20.9.125
IP: 72.20.54.117
NM: 255.255.255.255 (/32)
GW: 72.20.9.125
Currently VMWare is configured to use the 72.20.9.126 (/30) address for its web console. But this presents a problem for my VM's because you can't use the /32 without creating a separate WAN interface for the /30 address in order to route through its gateway.
And the instant I create a WAN interface for the /30 on my VM, I lose all communication because you can't share the /30 address with the VMWare web console and your own VM at the same time.
I am totally stumped as to how to proceed. As far as I can tell the only way forward is to twiddle around in the SSH console and create a static route for the /32, as described in this document:
Configuring static routes for vmkernel ports on an ESXi host (2001426) | VMware KB
,
But a second problem is how to move the web console over to the /32 address when I only have remote access, I don't have console access, and the datacenter host for the machine has no idea how to help with this.
If I can't switch the ESXi web console over from the /30 to the /32 in one single clean step, then I will be cut off from the remote access and fully locked out and unable to proceed, without having the datacenter host just "reset the configuration" and then we are stuck with using the /30 again.
Hi,
I have created a new cluster with 3 hosts (A,B,C) and enable HA/DRS on that cluster. I managed to build the autolab with 3 ESXi hosts part of Vsphere 5.5.
Now I am facing issue i.e. out of 3 hosts... 2 hosts are showing that "The Vsphere HA agent on this host cannot reach some of the management network addresses." whereas the 3rd ESXi host is fine.
I tried to reconfigure the HA but still it's getting the same issue and when I set 1 ESXi host to maintenance mode then the HA works fine with 2 hosts but not with all 3 hosts in the cluster.
Below are some more details:
The vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network. Check the vMotion network settings and physical network configuration. vMotion migration [-1408186613:1502279704441717] failed to create a connection with remote host <172.16.199.12>: The ESX hosts failed to connect over the VMotion network Migration [-1408186613:1502279704441717] failed to connect to remote host <172.16.199.12> from host <172.16.199.11>: Host is down The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct.
Anybody seen this issue before and knows how to resolve it?
Any help will be appriceated.
I am running Juniper's vMX 17.2R1.13 on ESXi 6.0 currently and have been experiencing significant lag on the console window connecting to the Control Plane VM (vCP). I am currently running ESXi 6.0.0 build 3620759 and client 1.21.0 on a Laptop with an i7 7700HQ processor and 32gb of memory. It is running on Windows 10 Home, and the ESXi VM itself has been allocated 24gb in VMWare Workstation 12. Workstation was given 2 processors/4 cores for 8 total logical cores and I have assigned 2 CPU and 2gb of memory currently to the Juniper vCP VM.
I noticed that during boot the VM itself is using close to 100% of its CPU. It will fluctuate down a little bit once it is fully booted but I am not sure if this is the issue. Is the console connection tied directly to CPU usage or is this possibly a limitation with the console being opened in the browser (chrome)? It seems to scroll text, almost like loading an image on a dial up connection. I am not sure if increasing the CPU count for this VM will help it significantly enough, or if it would just take more resources and it's something I either have to tweak elsewhere or perhaps even just learn to live with.
Is there a better program that can be tied into ESXi for use in console connections? Can you tie it to something like SecureCRT or another terminal program in any way since it's a nested VM? Sorry I am new to much of ESXi and still playing around with it. I am a networking guy systems stuff is new to my world. Thanks!
the problem is VMwareSTS service is not starting during the update.
Can you please attach the VMwareSTS logs at the time 2017-08-09T18:15:13 from the SSO folder at C:\ProgramData\VMware\vCenterServer\runtime\VMwareSTSservice\logs\
from vminst-con.log
===
2017-08-09T18:15:13.346Z ERROR Starting service: VMwareSTS, Exception: (2, 'StartService', 'The system cannot find the file specified.')
Error executing start on service VMwareSTS. Details {
"resolution": null,
"detail": [
{
"args": [
"VMwareSTS"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'VMwareSTS'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Service-control failed. Error {
"resolution": null,
"detail": [
{
"args": [
"VMwareSTS"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'VMwareSTS'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
===