I edited vm from its advance properties and created this entry
guestinfo.hypervisor.hostname = esxi hostname i typed here
and then i executed this command
vmtoolsd.exe "info-get guestinfo.hypervisor.hostname
I edited vm from its advance properties and created this entry
guestinfo.hypervisor.hostname = esxi hostname i typed here
and then i executed this command
vmtoolsd.exe "info-get guestinfo.hypervisor.hostname
any vmware source where this info is available?
Hi Thomas,
I've did what suggested in the two sections, but still no luck...
What I have in the codes follow these steps,
Connect:
VixDiskLib_InitEx()
VixDiskLib_PrepareForAccess()
Take snapshot
VixDiskLib_ConnectEx()
Read:
VixDiskLib_Open()
VixDiskLib_GetInfo()
VixDiskLib_FreeInfo()
a lot of VixDiskLib_Read(), then
VixDiskLib_Close()
Disconnect:
Wait until the timeout set in configure is reached, then delete snapshot
VixDiskLib_Disconnect()
VixDiskLib_Cleanup()
VixDiskLib_EndAccess()
VixDiskLib_Exit()
Just wonder what could be wrong?
Hello all. First post. Been playing with ESXi for a few months and I'm having an unusual issue. Here's my hardware and VM setup:
Hardware: Supermicro x9scm-f-o with 32GB of ECC RAM and E3-1230v2 CPU
Also included is a M1015 reflashed to IT mode and used as passthrough with VT-d to the FreeNAS VM.
VMs:
FreeNAS 8.3.1 64-bit with 20GB of RAM assigned (3vCPU)
Linux Mint 13 LTS 4GB RAM (3vCPU)
Cyberpower UPS Appliance VM 2GB RAM (1vCPU)
After building the machine a week or two went by, then I lost network connectivity to the entire box(this was when I first realized something might be wrong). I couldn't use the vSphere client or access the guest machines. I attempted to "Restart Management Network" locally but that didn't solve anything. Still no connectivity. I then attempted to shutdown the box but it wouldn't shutdown. Ultimately I power cycled it.
So over the last 2 months at random times I've lost network connectivity. Thanks to reading various sources I've found an error in my syslog that ends up being logged 5-20+ times in a row, and happens randomly at intervals of 2-10 minutes. I get an error that says:
Unknown: out of memory [5880]
I thought it was due to my VMs using a lot of network connections, but never really could find someone else with the error. It's very non-specific and I'm running out of leads to check out the issue, hence I've turned to the community.
Well, today I have decided I want to figure this puzzle out, so I shutdown all of the VMs and that error still continues to show up in the syslog. So clearly I have a configuration problem somewhere. This is odd to me because I've tried to avoid changing settings that I wasn't 100% sure was appropriate for me because Im a newbie to ESXi and I'd rather not break my own installation. The only thing I've done that might be construed as an 'advanced' feature modification is I enabled the RDM function for the Linux Mint installation. It was already on a hard drive and I thought I'd just do RDM passthrough and use it that way if it worked. Well, it has so I left it like that.
I can't find much info on what 5880 might represent, so I assumed its a PID or something. It has changed from one bootup to the next. So here's the output from the CLI:
~ # ps -P | grep 5880
5880 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5881 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5882 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5883 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5884 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5885 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5887 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
5888 5880 sfcb-vmware_raw 5606 /sbin/sfcbd
~ #
Again, I tried searching for sfcbd and it really doesn't give me any clues.
I actually built 2 identical systems. One for me and one for a friend. He uses more RAM for his VMs(and different VMs) but he doesn't have this issue. I'm figuring I've done something to my installation to deserve this since his is flawless, but I am out of leads.
tl;dr: I get the "Unknown: out of memory" error along with a loss of all network connectivity randomly after 1 day to 2 weeks. Sometimes when the server would be idle(such as at night). I don't know if they are related, but I assume they are.
Anyone have ideas to try? This is baffling me and I'm really at a loss to explain the problem let alone how to fix it.
Thanks!
Barry, Thanks for the reply.
Could you give me a sample of client configuration on how to set up a region with CACHING_PROXY_HEAP_LRU with no data streamed to it from the server at startup. Once the client makes a request for a key, it will get it from the server and hold it in its local cache. BUt if that key changes on the server, update should be pushed to the client.
Documentation isn't clear here... this is my configuration now, does this look correct for my use case?
<gfe:client-region id="Price" shortcut="CACHING_PROXY_HEAP_LRU" pool-name="gemfire-pool" >
<gfe:key-interest durable="false" result-policy="NONE" receive-values="false">
<bean class="com.myCompany.RecordKey">
<constructor-arg value="ALL_KEYS" />
</bean>
</gfe:key-interest>
</gfe:client-region>
Unless it's a typo, the command is missing "--cmd" and should read
vmtoolsd.exe --cmd "info-get guestinfo.hypervisor.hostname"
André
Have you rear this article? Please hava a look..
http://technet.microsoft.com/en-us/library/cc958935.aspx
Oh ok, internal only just like you said in your first post. So you want the one pool to be only available to people on specific networks, your internal networks. Yes, i see your quandary now. So if you only want to use one fqdn, (view.domain.com) then you just tell those people that are only have internal access, to only use it when they're in those networks. Im guessing your stuck with the inside only requirement. Please post your solution if you figure out a way around these limitations. Sorry i couldn't help you though.
In the hardware section of the summary the network adapter as a Red Cross
In order to restore the network connection shut down the virtual machine, remove the network adapter
Add hardware
Choose network adapter, next and finish. Restart the virtual machine and the network adapter shows is connected again.
No, if nothing is different you would see all registry and file access in white. Sounds like you are getting it wrong somehow.
This not problem is in certification@vmware.com. I think problem in your side.
Have you check your internet connection is working properly?
If you are using third party tools like outlook then check the configuration.
We have a main network of 10.1.x.x for all the switches/routers (1.x), servers (10.x), desktops (30.x), and and a private network for the SANs to communication with the virtual environment (221.x and 222.x). The private network consists of 2 switches, with just the 2 SANs and 3 host VM servers plugged into them, and the switches are redundant, with redundant iSCSI paths set up in Vmware. The vMotion settings are set up on this private network, not on the main network. We have 3 host servers, each with dual 8-core procs and 128GB of ram, and all 3 run about 1% - 5% cpu utilization and 10%-15% memory utilization tops, so the environment is way overbuilt, but it's built for the future.
We put #1 into maintenance mode, which set up an automated process to migrate all VM's off of it, and after almost a day it finally succeeded in moving all VM's to the other 2 hosts. We rebooted the host, and now it's working fine, as it always has.
Ok, ti ringrazio ancora e lavoro sopra i tuoi suggerimenti.
Ciao
Hi
I apologize if this is the wrong sub-forum. We use VMware 5.1 , with vCenter to test our software application. We are in in the process of releasing a patch which is delivered via an MSP file.
Scenario 1:
All ok - Pass
Scenario 2 (designed to speed up testing)
Pre-setup (one time):
For each patch:
The actual error is
MSI (c) (14:44) [13:36:45:194]: APPCOMPAT: looking for appcompat database entry with ProductCode '{4EC8B526-FBAA-4085-9D34-1B6E7A664C1C}'.
MSI (c) (14:44) [13:36:45:194]: APPCOMPAT: no matching ProductCode found in database.
Our main product is installed. If you search the registry for the ProductCode GUID, It is there. If I remove the main application, reinstall and then try to run the patch again, it still won't work. If I jump back to the original snapshot, it works, but won't after the snapshot restore with the main app already installed.
Does this sound like some sort of disk corruption?
Hopefully I was clear about what I am seeing.
Cheers
Tom
1)
Great.
2)
In your VMMARK2.CONFIG file, you name "virtualclient0" as your client. 10.1.80.161. By Client0, I meant virtualclient0.
Please verify that:
1. You installed the correct version of STAF for your virtualclient0 operating system (Did you install 32 bit staf on a 64 bit operating system?)
and
2. That you installed the correct version of Java on virtualclient0 (correct bitness) and that you set the environment variable JAVA_HOME correctly. See instructions "Install a Java JRE" in the benchmarking guide. To double check Java installation, open a command prompt and run java -version.
At the time that you ran VMmark, the following VMs were present in the cluster that should not have been there:
DeployTemplate1 PoweredOff 1 0.500
deployvm1 PoweredOn 1 0.500
You can see this listed in VC-listVMs.txt.
3)
You are not supposed to copy the same hosts file to all the VMs. For an example of the correct hosts file, deploy a new OlioWeb or OlioDB VM from the template and look at its hosts file.
On your OlioWeb VM, add the line:
10.1.80.164 olio-db
OR you can add the line:
10.1.80.164 olio-db oliodb0
Both are correct.
On your DS2Web VMs, add the line:
10.1.80.166 DS2-DB
You can use VMware standalone converter. http://vmware.com/go/converter
http://vmware.com/go/converter. Y
ou can also have a look at
http://communities.vmware.com/docs/DOC-8760
Hi. We have an host that disconnected from vCenter. All the VMs are still running on it without problem, but we pray that they will stay online until our next maintenance period.
It's not the first time it happens in our cluster, and it's not always happening on the same host.
We can't connect to the host directly using vSphere client, but we can SSH to it. Unfortunately, in the ssh session, lot of the commands freeze forever. For example, I can't "cat" the log files and I can't do "ls /dev/volumes", etc.
In ps -s, the stuck processes are in the state WAIT OCOBJS. Unfortunately, even Google can't tell me what OCOBJS is.
The host is running ESXi 5.0.0 768111, but similar issue happened to us on ESXi 5.0.0 914586.
Does someone has an idea about what's happening?
Thanks
Have you read this kb. Have a look...
Here is a nice article. Have seen this..??
http://blog.solori.net/2011/03/21/short-take-vmware-view-whats-up-with-pcoip/