chrwei's Posts

worked for me too, thanks for finding and posting the solution!
Just dropping a note that I uploaded script for cluster remediation that will automatically vmotion guests to hosts in a balanced way and remediate hosts.  More info on the document page http://c... See more...
Just dropping a note that I uploaded script for cluster remediation that will automatically vmotion guests to hosts in a balanced way and remediate hosts.  More info on the document page http://communities.vmware.com/docs/DOC-16824
best option is to use $host.ui.PromptForCredential() to get both the username and password, the result of which Connect-VIServer can take via its -Credential option
This script will automatically update all hosts in a cluster, even without DRS. It is based on the script in this blog post.  Please do read his post, he covers the necessary prerequisites an... See more...
This script will automatically update all hosts in a cluster, even without DRS. It is based on the script in this blog post.  Please do read his post, he covers the necessary prerequisites and talks about some assumptions.  The rest of this document will assume you've read this blog post. My changes involve around how the guests are moved off to other hosts.  The original script would move guests to a random host, I was not comfortable with that idea.  My changes will inspect all hosts and guests and record the RAM configured to each guests and try to keep memory configured on each host balanced.  It does not take CPU or actual ram usage into account, only guest configured ram in order to minimize the chances of over committing, though if your cluster is not sized to tolerate one host failure without  over committing, them there is a possibility that  over committing will happen.  The script also will put all guests back where they started at the end, just in case you've manually balanced your workloads based on hardware variances. The process is as follows: - record which host each guest is on and sum up all configured ram per host - starting with first host, iterate its guests starting with the one with the most configured ram -- find the host with the largest difference between host ram and its total guest configured ram -- recalculate the 2 hosts ram and start a background VMotion to move the guest to the new host -- repeat until all guests on the host are being moved -- show progress indicators for the vmotions and wait until all vmotions are complete -- remediate the host and wait for it to come back up - repeat the above for each host in the cluster - when al hosts have been remediated, start tasks to move the guests back to their original hosts. - show progress indicators for the vmotions and wait until all vmotions are complete Usage: The script takes no arguments and needs no configuration, other than the prerrquasited mentioned in the above blog post.  The script will prompt for your vcenter hostname and crdentials, and which clusters and baselines you want to apply.
seems installing update 1 on hosts doens't update the client, re-downloaded the client from the host's web interface and it's working again
last nights windows updates also broke it for XP
Can you post some details such as distro, kernel version, export options and storage layout? I'm unable to even get that good a speed on linux NFS. also, I'm not sure how well ESX 3.5 can use... See more...
Can you post some details such as distro, kernel version, export options and storage layout? I'm unable to even get that good a speed on linux NFS. also, I'm not sure how well ESX 3.5 can use bonded nics with nfs, at the very least you'd have to run benches in more than 1 guest at the same time. I know that it doens't with iscsi, and no jumbo frames in the vmkernel either.
where should I start... lets see, how about security... "Security advice: Keep your keys expecially the private one secure by placing it inside encrypted filesystems or limit the usage by chm... See more...
where should I start... lets see, how about security... "Security advice: Keep your keys expecially the private one secure by placing it inside encrypted filesystems or limit the usage by chmod 600 for user root." - and yet you COPY the root@ESXhost users key to a windows system? every user@host should generate their own key-pair and you ONLY copy the pub part to the ESX .ssh/authorized_keys file. The server shoud not ever have your client's private part of the key! Having multiple copies of the private part is just plain wrong and against your warning..."do as I say not as I do" or what? - Putty has its own keygen, use it. - RE: DSA vs RSA - it's less about speed since on any 1Ghz+ system either is done in a blink and more about security, but even that seems to be right along the lines vi vs emacs. steps 15 and 16 are good info though.
I know this is an old thread, but one thing here went without comment that I needs it. Windows does not support the paravirt that VMWare uses. Enabling it will cause Windows to find an unknow... See more...
I know this is an old thread, but one thing here went without comment that I needs it. Windows does not support the paravirt that VMWare uses. Enabling it will cause Windows to find an unknown memory controller, and I don't know what that does to performance, but it can't improve it. I have also had problems using paravirt with 64bit linux guests on Intel CPU's, but not on AMD's. not sure why.
I'm not looking for RR or any type of failover. I want to put 4 HBAs in my ESX server and stream 4x more data, over all 4 paths, from a single VM, to a single LUN, all at the same time. t... See more...
I'm not looking for RR or any type of failover. I want to put 4 HBAs in my ESX server and stream 4x more data, over all 4 paths, from a single VM, to a single LUN, all at the same time. the other thing you are missing is that you are talking about taking a stream, splitting it into 4 streams and sending them through 4 "tubes" and then stitching them back together. Your switches don't care, and your SAN may have a DSP or fast enough CPU to do this, but your HBA's probably don't and I'm not so sure I'd like the ESX console doing all that work. It's also likely to result in some delays while dropped packets get resent and could even perform slower than a single pipe on occasion. if you want a faster connection, get a faster connection.
you'd have to ask Thecus if there target software supports SCSI reserve/release commands, if it does, cluster should work, but in my tests with other targets that do support this but aren't on th... See more...
you'd have to ask Thecus if there target software supports SCSI reserve/release commands, if it does, cluster should work, but in my tests with other targets that do support this but aren't on the HCL, it either gets unstable or very slow with more than one initiator per lun
I have not had these kinds of issues with 3.5, but I do have other issues with it. guests that are not doing heavy IO even tend to survive a reboot of the target, which I was impressed by. what... See more...
I have not had these kinds of issues with 3.5, but I do have other issues with it. guests that are not doing heavy IO even tend to survive a reboot of the target, which I was impressed by. what I'm not impressed by is that certain usage of via vmware causes the target host to need to be rebooted, and similar uses with other initiators do not cause this.
thing is, I can't think of a good reason to not allow installation on 64bit systems. VI client is just a tcp client, it's not like it's interactive with core OS features, and VC is just apache... See more...
thing is, I can't think of a good reason to not allow installation on 64bit systems. VI client is just a tcp client, it's not like it's interactive with core OS features, and VC is just apache/tomcat/java server and SQL Express, which the 32-bit versions of can each be installed on 64bit Windows.
so i called support. turns out that if you have IIS installed and do a custom VC install to change the ports, it goes all to hell. I stopped IIS, installed VC with the defaults, then I can st... See more...
so i called support. turns out that if you have IIS installed and do a custom VC install to change the ports, it goes all to hell. I stopped IIS, installed VC with the defaults, then I can stop the vmware web service and start IIS again and everything works, but I've yet to get the vmware web service working even after changing its ports in the config.
had a generic database error and no combination of config or crdentials would do anything useful eben though that worked for you. so i installed it all and tried again, this time using the mssql... See more...
had a generic database error and no combination of config or crdentials would do anything useful eben though that worked for you. so i installed it all and tried again, this time using the mssql2k server I already have. 68 pages into the install pdf it finally tells me the user I made has to have db_owner on the msdb database as well as dbo on the database I created. what a pain! never had to do that before for any application. I still get "a connection failure occured", though not I don't have a database error in the logs. I do have a new error though I have no idea what it means: MOB started on pipe .\pipe\vmware-vpxd-mob-pipe -- BEGIN task-internal-3 -- -- vim.ServiceInstance.retrieveContent -- DB880B2B-6037-4455-A528-69B85E38C433 -- FINISH task-internal-3 -- -- vim.ServiceInstance.retrieveContent -- DB880B2B-6037-4455-A528-69B85E38C433 -- BEGIN task-internal-4 -- -- vim.SessionManager.GetCurrentSession -- DB880B2B-6037-4455-A528-69B85E38C433 -- FINISH task-internal-4 -- -- vim.SessionManager.GetCurrentSession -- DB880B2B-6037-4455-A528-69B85E38C433 -- BEGIN task-internal-5 -- -- vim.SessionManager.loginExtension -- DB880B2B-6037-4455-A528-69B85E38C433 -- FINISH task-internal-5 -- -- vim.SessionManager.loginExtension -- DB880B2B-6037-4455-A528-69B85E38C433 -- ERROR task-internal-5 -- -- vim.SessionManager.loginExtension: vim.fault.InvalidLogin: (vim.fault.InvalidLogin) { dynamicType = , msg = "" }
nope, still says "cannot establish initial connection" even though the service starts fine. the only thing in the logs is: The description for Event ID ( 1000 ) in Source ( VMware VirtualCent... See more...
nope, still says "cannot establish initial connection" even though the service starts fine. the only thing in the logs is: The description for Event ID ( 1000 ) in Source ( VMware VirtualCenter Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Starting VMware VirtualCenter 2.5.0 build-64192.
finally got it the finals all downloaded I've also just noticed that the build number on the add/remove for the VC components doesn't match the download, reinstalling again!
I'm not sure I understand. VC talks to the database via a TCP protocol and an MSSQL user account, service permissions should have nothing to do with it. However, I had already tried changing ... See more...
I'm not sure I understand. VC talks to the database via a TCP protocol and an MSSQL user account, service permissions should have nothing to do with it. However, I had already tried changing the user account that the service runs from "system account" as to one that I run other services as and it did not help.
so is there actually no change to VC? with last weeks downlad I am not able to connect to 2.5 after upgrading a 2.0 install, I even completely uninstalled, deleted database, rebooted, reinstalle... See more...
so is there actually no change to VC? with last weeks downlad I am not able to connect to 2.5 after upgrading a 2.0 install, I even completely uninstalled, deleted database, rebooted, reinstalled, even tried the bundled mssql instead of my existing one. VC will not start during the install so the install never fully completes, but it will start manually though i cannot connect to it. This is on a physical Win2k3 server 32-bit where VC 2.0 worked fine.
I'm hoping it's becaue this isn't the "final" version, but the Foundation license still doesn't support iSCSI or SAN even though the ESX 3.5 press release sounds like it should, or maybe I'd need... See more...
I'm hoping it's becaue this isn't the "final" version, but the Foundation license still doesn't support iSCSI or SAN even though the ESX 3.5 press release sounds like it should, or maybe I'd need an updated license file? It does see my starter license as Foundation. "Unlike the previous VMware Infrastructure 3 Starter, VMware Infrastructure 3 Foundation will have no restrictions on shared storage connectivity, memory utilization or number of CPUs of the physical server" installation and local vmfs storage on SATA does work on a 2801GR/HR controller though so that's a plus