Same problem here. The garphs are only visable in a few minute periode!
6.7.0 Update 2 (Build 13006603)
Vmware please help us!
↧
Re: ESXi 6.7 Performance graphs only show the last few minutes
↧
VM in ESXI can not access internet
Hello,
I am trying to learn ESXI so I set up an ESXI inside a VMware Workstation Player, the network is `NAT`
So far I set up a static IP v4 address for ESXI in VmWare Workstation Player, I set it like this
IPV4 Address 192.168.201.3 Subnet mask 255.255.255.0 Default gateway 192.168.201.2
With this for the DNS
Primary 8.8.8.8 Alternate 4.4.4.4 Hostame localhost
When I do a `ip a` on the host machine, I have this
4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff inet 172.16.1.1/24 brd 172.16.1.255 scope global vmnet1 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fec0:1/64 scope link valid_lft forever preferred_lft forever 5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff inet 192.168.201.1/24 brd 192.168.201.255 scope global vmnet8 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fec0:8/64 scope link valid_lft forever preferred_lft forever
So far so good, I can access esxi.
Now when I create a vm on ESXI (a debian), they are connected to the `VM Network`, I don't have `DHCP` during the installation of Debian but I guess it's normal.
Later after the installation of Debian, I tried to set up a static ip address in the same range of `192.168.201.0/24`, I can ping the vm from the esxi vm installed in VMware Player. But I can not ping the debian vm installed in esxi from my host and I can not access internet in the debian vm. Also when I set the gateway on the debian vm, I cannot access it so I suppose something is really wrong in the way I configure the static ip address on the debian vm.
Here is my config for the debian vm
cat /etc/network/interfaces allow-hotplug ens192 iface ens192 inet static address 192.168.201.11/24 gateway 192.168.201.2 ip r default via 192.168.201.2 dev ens192 onlink 192.168.201.0/24 dev ens192 proto kernel scope link src 192.168.201.11
I don't understand, I guess I probably miss configured something maybe.
Thank you in advance for your help
PS1: The `VM Network` is set with VLAN ID: 0`
PS2: I am running this on Arch Linux and I have this version of the kernel `5.1.5-arch1-2-ARCH`
↧
↧
Re: Cannot reach ESXi through LAN, but it's up and running just fine
I suppose so, as I could RDP to each VM just fine. And all network services on each VM were accessible. The only issue was connecting to esxi itself.
I rolled back now and it's fixed.
↧
LSI_SAS driver
I have to update the LSI_SAS driver because of a problem in the virtual machine. ı cant driver for windows 2012. how do I find the latest driver? ESXi 6.5 u1 and os is windows 2012 .
this device driver comes in windows or if vmware tools is installed ?
↧
Re: Cannot reach ESXi through LAN, but it's up and running just fine
I scrolled all the logs from the esxi UI/schell but nothing popped up to me. Of course I didn't know what to look for so I was just hoping to see some errors or rejected connections or something.
Eventually I used the rollback as you suggested and that cured it. Trouble next was that 1 of the storages got missing. So the VMs on it were no longer accessible. I manually added that back but for some reason there are still 2 VMs grayed out and in unknown status, saying vmx inaccessible. I am looking at the files on the volume though and they seem fine. Access rights and everything look good.
Not sure on policies on this forum: should I create a new question for this issue?
Thanks
LE: I see some of the VMs from the previously existing datastore were no longer in the inventory either. They may have been added after the restore point was created? Just guessing.
↧
↧
Re: Cannot reach ESXi through LAN, but it's up and running just fine
Not sure on policies on this forum: should I create a new question for this issue?
There are no strict polices which require a new discussion. However, creating dedicated discussions for different issues may help other users with similar issues.
Trouble next was that 1 of the storages got missing. So the VMs on it were no longer accessible. I manually added that back but for some reason there are still 2 VMs grayed out and in unknown status, saying vmx inaccessible.
What type of storage is it (Local, NAS, SAN)? And how did you add it back (mount, resignature)?
Are other VMs - located on the same datastore - accessible?
Internally, ESXi uses a VMFS datastore's UUID, rather than its friendly name. Resinaturing a datastore will assign a new UUID, which makes it necessary, to remove the unknown VMs from the inventory, and add them again by e.g. right clicking their configuration (.vmx) file in the datastore browser.
André
↧
Re: VM in ESXI can not access internet
Welcome to the Community,
for nested VMs, you may need to allow promiscuous mode for the virtual adapter (NAT = vmnet8)
see example at Using Virtual Network Adapters in Promiscuous Mode on Linux Hosts
André
↧
Re: VM in ESXI can not access internet
Thanks for your reply, I already did this, I even tried to set promiscuous mode inside the esxi on the vSwitch0 but without success
↧
Re: VM in ESXI can not access internet
... I even tried to set promiscuous mode inside the esxi on the vSwitch0 but without success
Just to confirm. Did you do this on vmnet8 too? The example shows vmnet0 (Bridged), but said that you are using NAT.
The point is that the virtual network adapters don't learn MAC addresses, i.e. only know the ones directly logged in, and not the nested ones.
The only virtual adapter that needs to be put in promiscuous mode in this case is host's vmnet8.
I'm not using a Linux host myself, so I'm not sure whether some vmware services need to be restarted after the permission has been modified.
André
↧
↧
Re: VM in ESXI can not access internet
Yes I did on the interface vmnet8. It was a bit obvious to do it here since that's the interface with this ip 192.168.201.1/24
ls -al /dev/vmnet8 crw-rw-rw- 1 root root 119, 8 May 31 09:50 /dev/vmnet8
I used
chmod a+rw /dev/vmnet8
Edit: I also rebooted several times already so the services restarted
I am wondering if I should not try to use chgrp instead or maybe reinstall Vmware Player
↧
Re: LSI_SAS driver
The device driver comes with VMware tools. Do not attempt to upgrade any driver that comes package with Tools outside of a Tools update.
↧
Re: VM in ESXI can not access internet
Yeah I solved it thanks to you, I did something pretty disgusting, I change the owner of the interface, did a down on the interface and restart vmware-networks.service
It works now thank you so much, awesome
↧
Re: VMFS Datastore won't mount
Your usage of the word successfully is a bit strange.
Stop what you are doing now.
Buy UFSexplorer Proffessional 7 - that eventually can help or call me next week.
I already told you that I need to see the complete volume.
Ulli
↧
↧
VM crashes if LPe11000 is used with PCI Passtrough (but not with other cards)
Hi! I have a single ESXi host that rruns various VMs.
I found out that if I pass through an Emulex LPe11000 card, the guest crashes. Let me resume some facts:
- I have a linux VM with a PCIe ASMedia eSATA controller passed-through card that has been working for years
- I have a Windows 8.1 VM that I used for long time with an LSI SCSI controller in passtrough without problem
- I have replaced the LSI SCSI with the Emulex FC4. The VM boots normally. If I try to install the driver it powers off
- I have created a new VM; if the Emulex card is passed through, even the Windows boot disk (tried W7 and W10) makes the machine power off. Same problem if I try to boot with a live ISO of Ubuntu 18.04
If I boot with windows 8 on the physical hardware, the system goes up and I'm able to install the Emulex driver normally.
ESXi continues running flawlessly when the VM guest powers off.
So I'm wondering: why that issue only with that specific card? How to fix it? Any suggestion?
and sorry, I'm running 6.7.0 Update 2 (Build 13006603) on a Lenovo M93P.
Thanks!
↧
Re: Best way to update/patch ESXi in huge infra
you can use auto deploy to build your hosts and then when you want to patch you put out a new software depot with a new version, update the deploy rule and reboot the hosts.
↧
Re: Cannot reach ESXi through LAN, but it's up and running just fine
>>What type of storage is it (Local, NAS, SAN)?
Local
>> And how did you add it back (mount, resignature)?
Just the "Add Storage..." link/button from the configuration\Storage (I also did a resscan but that didn't help any)
>> Are other VMs - located on the same datastore - accessible?
Well, as soon as I added the storage, the VMs on it were seen and recognized.
I see now the 2 grayed out VMs are from the first storage that was loaded up "fine" including the other VMs on it. I will do a reboot in the evening and see what happens.
Thanks
↧
Migration to new datastore (rebuilding the old one)
Hi All,
I have one RAID-0 array in my server. I'd need to break it (decrease it by one disk) but do not want to lose any vms on this machine.
To be able to keep all existing machines I want to perform the following activities. Kindly ask to verify if it makes sense and does not break my ESXi setup.
1. I'll add new temporary disk which will be out of the RAID - new datastore
2. I'll migrate all virtual machines from existing datastore (RAID0) to new, temporary datastore
3. I'll rebuild old datastore (based on RAID0)
4. When already restored, I'll migrate all vms back
5. Will decommission temporary datastore
Is this list complete? Do virtual machines are the only entities that need to be migrated? Doesn't ESXi require any disk to be able to boot?
Will appreciate your help
↧
↧
Re: Cannot reach ESXi through LAN, but it's up and running just fine
The reboot didn't help. I double checked and both VMs are from 2 other storages that were up just fine after the recovery/restore with other VMs on them showing up just fine.
So the VM shows up in the vsphere client like
/vmfs/volumes/<GUID>/folder/file.vmx (inaccessible)
the exact path (checked letter by letter) is accessible via the esxi ssh shell. Access on the vmx file is -rwxr-xr-x, and matches other visible/accessible VMs on the same storage.
I can do "less filename" on the vmx and see it ok. Doesn't look to be damaged/corrupted (compared the format/output with other (running) vmx file)
Without removing the inaccessible VM, I have added it to the inventory again. It added just fine. Powered up fine as well. So I went ahead and removed the inaccessible "link".
Gremlins, I tell you.
↧
ESXI install error 6.7u1
Hi,
When I try to install ESXI 6.7u1 on a HPE BL360c gen8 blade it shows this error its the first time i've had an error on these machines i've installed this same version on 28 other blades exactly the same but this one doesn't want to work I have attached an image of the error. i'm assuming its something to do with the micro SD card in the system for install by the error?
↧
Re: ESXI install error 6.7u1
I assume that you know that your hardware is not supported with this version? However, if it's a test system, and you can make it work that's fine.
The error message indeed looks like the SD card issue with either a bad SD card, or a previously existing partition table that should be deleted/cleared.
André
↧