Warning: mysql_real_escape_string(): Access denied for user ''@'localhost' (using password: NO) in /home/festplat/public_html/blog/wp-content/plugins/statpress/statpress.php on line 1191

Warning: mysql_real_escape_string(): A link to the server could not be established in /home/festplat/public_html/blog/wp-content/plugins/statpress/statpress.php on line 1191

Warning: mysql_real_escape_string(): Access denied for user ''@'localhost' (using password: NO) in /home/festplat/public_html/blog/wp-content/plugins/statpress/statpress.php on line 1194

Warning: mysql_real_escape_string(): A link to the server could not be established in /home/festplat/public_html/blog/wp-content/plugins/statpress/statpress.php on line 1194

Warning: mysql_real_escape_string(): Access denied for user ''@'localhost' (using password: NO) in /home/festplat/public_html/blog/wp-content/plugins/statpress/statpress.php on line 1197

Warning: mysql_real_escape_string(): A link to the server could not be established in /home/festplat/public_html/blog/wp-content/plugins/statpress/statpress.php on line 1197
Update 2 « Tag « festplatte.ch

VMware ESX 3.5 HA Agent Fehler mit Update 2

ESX 3.5, VMware No Comments »

Mit dem Update 2 für das Virtualcenter 2.5 und ESX Host 3.5 können Fehler mit dem HA Agent auftreten. Es folgen Fehlermeldungen wie

“insufficient resources to satisfy HA failover level on cluster” and “unable to contact a primary HA agent in cluster” and “HA Agent is disabled on…”

Das Problem kommt von den Hostnamen der Host Server. Diese müssen alle klein geschrieben sein…. Wenn nicht, entstehen Probleme mit dem HA Agent…

Via VirtualCenter -> Configuration -> DNS and Routing -> Host Identification. Der Name und Domain klein schreiben. Danach Host rebooten.

Weiter zu überprüfen auf Kleinschreibung sind folgende Einstellungen via SSH Konsole der jeweiligen Hosts:

Wenn alles angepasst ist mit folgenden Befehlen überprüfen:
uname -n
hostname -a
hostname -s
hostname -d
hostname -f

Weiter sicherstellen dass in /etc/vmware/esx.conf die Zeile
/adv/Misc/HostName = (alles klein Geschrieben)

Danach HA wieder aktivieren.


ESX VMware 3.5 Update 2 download wieder möglich

ESX 3.5, VMware No Comments »

Das ISO File (ESX Install) für eine Neuinstallation von ESX 3.5 direkt mit Update 2 steht nun gepached wieder zur Verfügung. Die Buildnummer lautet 110268


Der Expresspatch für bereits upgedatete Hosts auf Update 2 steht nach wie vor auch im Downloadbereich zur Verfügung.


Verzögerung bei neuem VMware ESX 3.5 Update 2

ESX 3.5, VMware No Comments »

Das neue Update 2 für Neuinstallationen (ohne time-bomb-error) verzögert sich weiter. Laut VMware dauert die Testphase länger als erwartet… :)
Ist natürlich auch gut so, dass exakt getestet wird. Nicht dass wir im Septemer oder Oktober wieder wie am 12. August mit grossen Augen im Büro stehen wenn es heisst, Licence expired…

Dear VMware Customers,

We are experiencing a delay in releasing the new version of ESX/ESXi 3.5 Update 2. Our testing of this release is taking longer than anticipated. We are now targeting to release the update between 2 AM PDT (0700 UTC) August 14 and 8 AM (1500 UTC) August 14 PDT.

We apologize for the delay. VMware engineering teams are working around the clock to deliver this new version. We will continue to keep you informed of developments until this issue is fully resolved.

Please note this update is only relevant to customers who did not install the impacted release of ESX 3.5Update 2 (build number 103908) and ESXi 3.5 Update 2 (build number 103909). If you have installed either of these please visit http://www.vmware.com/landing_pages/esxexpresspatches.html and install the express patch.

Thank you,

The VMware ESX Product Team



VMware ESX 3.5 Update2 Patch

ESX 3.5, VMware No Comments »

Der Patch steht nun zur Verfügung


Statement von CEO Paul Maritz

Letter from VMware CEO Paul Maritz

Last night, we became aware of a code issue with the recently released update to ESX 3.5 and ESXi 3.5 (Update 2).
When the time clock in a server running ESX 3.5 or ESXi 3.5 Update 2 hits 12:00AM on August 12th, 2008, the released code causes the product license to expire. The problem has also occurred with a recent patch to ESX 3.5 or ESXi 3.5 Update 2. When an ESX or ESXi 3.5 server thinks its license has expired, the following can happen:
Virtual machines that are powered off cannot be turned on;
Virtual machines that have been suspended fail to leave suspend mode; and,
Virtual machines cannot be migrated using VMotion.
The issue was caused by a piece of code that was mistakenly left enabled for the final release of Update 2. This piece of code was left over from the pre-release versions of Update 2 and was designed to ensure that customers are running on the supported generally available version of Update 2.
In remedying the situation, we’ve already released an express patch for those customers that have installed/upgraded to ESX or ESXi 3.5 Update 2. Within the next 24 hours, we also expect to issue a full replacement for Update 2, which should be used by customers who want to perform fresh installs of ESX or ESXi.
I am sure you’re wondering how this could happen. We failed in two areas:
Not disabling the code in the final release of Update 2; and
Not catching it in our quality assurance process.
We are doing everything in our power to make sure this doesn’t happen again. VMware prides itself on the quality and reliability of our products, and this incident has prompted a thorough self-examination of how we create and deliver products to our customers. We have kicked off a comprehensive, in-depth review of our QA and release processes, and will quickly make the needed changes.
I want to apologize for the disruption and difficulty this issue may have caused to our customers and our partners. Your confidence in VMware is extremely important to us, and we are committed to restoring that confidence fully and quickly.
Thank You,
Paul Maritz
President and CEO

Weitere Links zum Thema:


recent news – VMware ESX 3.5 Update 2 error

ESX 3.5, VMware No Comments »

Post from offical VMware Community:


Dear VMware Customers,
Please find the latest update about the product expiration issue. From this point on, we’ll provide an update every two hours.
An issue has been discovered by many VMware customers and partners with ESX/ESXi 3.5 Update 2 where Virtual Machines fail to power on or VMotion successfully. This problem began to occur on August 12, 2008 for customers that had upgraded to ESX 3.5 Update 2. The problem is caused by a build timeout that was mistakenly left enabled for the release build.
Affected Products:
VMware ESX 3.5 Update 2 & ESXi 3.5 Update 2.
Reports of problems with ESX 3.5 U1 with the following 3.5 Update 2 patches applied: ESX350-200806201-UG
No other VMware products are affected.
What has been done?:
Product and Web teams pulled the ESX 3.5 Update 2 bits from the download pages last night so no more customers will be able to download the broken build.
VMware Engineering teams have isolated the cause of the problem and are working around the clock to deliver updated builds and patches for impacted customers.
A Knowledgebase article has been published (http://kb.vmware.com/kb/1006716), but traffic to the knowledgebase is causing time outs. A new static page has been published at http://www.vmware.com/support/esx35u2_supportalert.html that customers and partners will be able to view.
The phone system has been updated to advise customers of the problem
Vmware partners have been notified of the issue.
1) Do not install ESX 3.5 U2 if it has been downloaded from VMware’s website or elsewhere prior to August 12, 2008.
2) Set the host time to a date prior to August 12, 2008. This workaround has a number of very serious side affects that could impact product environments. Any Virtual Machines that sync time with the ESX host and serve time sensitive applications would be broken. These include, but are not limited to database servers, mail servers, & domain administration systems.
Next Steps:
VMware to notify customers who have downloaded this version and provide an update every two hours.
VMware Engineering has isolated the root cause and is working to produce an express patch for impacted customers today. The target timeframe is 6pm, August 12, 2008 PST.

* What would this express patch do?
More information will be provided in subsequent communication updates.

Will VMware still reissue the upgrade media and patch bundles in the timeframe that has been communicated?

Yes. We still plan to reissue upgrade media by 6pm, August 13 PST (instead of noon, August 13 PST) and all update patch bundles later in the week. We will provide an ETA for the update patch bundles subsequently. NOTE: the “patch bundles” referred to here are for the patches listed above under “Affected Products” and the other bundles released at GA. They are not the same as the express patch which is targeted for 6pm, August 12, 2008 PST as stated above.
Why does VMware plan to reissue the upgrade media before the patch bundles? That is a wrong priority call!

This is not a matter of priority. Since we can get done building and testing the upgrade media before the patch bundles, we want to make that available to customers first instead of reissuing all the binaries later in the week.
Can VMware issue a patch that opens the licensing backdoor in the next hour as a critical measure?

There is no licensing backdoor in our code.

Does this issue affect VC 2.5 Update 2?


What is VMware doing to make sure that the problem won’t happen again?

We are making improvements on all fronts. The product team had endeavored to deliver a release with support customers deem important. But we fell short and we are deeply sorry about all the disruption and inconveniences we have caused. We have identified where the holes are and they will be addressed to restore customers’ confidence.

The VMware ESX Product Team