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
2008 August « Archiv « festplatte.ch

Archive for August, 2008



VMware ESX 3.5 Maintenance Mode timeout

ESX 3.5, VMware No Comments »

Seit ESX 3.5 U2 / VC 2.5 U2 werden VMs nicht mehr migriert, wenn in den Maintenance Mode gewechselt wird, “… if the VMware HA failover level would be violated after the host enters the requested mode. This restriction applies whether strict HA admission control is enabled or not.”

Der Timeout wird durch HA verursacht, indem das Evakuieren des Hosts unterbunden wird. Workaround für diesen Fall ist das manuelle migrieren der VMs oder alternativ das Deaktivieren der HA Option im Cluster…

Obwohl dieses Verhalten die Verfügbarkeit von VMs erhöht, schränkt es auch wieder ein.
Das Engineering diskutiert mögliche Änderungen bzw. Optionen für zukünftige Versionen sowie die Dokumentation des neuen Verhaltens.

Share


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:
/etc/hosts
/etc/sysconfig/network
/proc/sys/kernel/hostname
hostname

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

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

Danach HA wieder aktivieren.

Share


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

http://www.vmware.com/download/vi/

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

Share

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

http://communities.vmware.com/thread/162377?tstart=0&start=660

Share

VMware ESX 3.5 Update2 Patch

ESX 3.5, VMware No Comments »

Der Patch steht nun zur Verfügung

http://www.vmware.com/landing_pages/esxexpresspatches.html?start=585
http://www.vmware.com/download/

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
VMware

Weitere Links zum Thema:
http://communities.vmware.com/thread/162377?tstart=0&start=600
http://communities.vmware.com/thread/162714?tstart=0&start=15
http://communities.vmware.com/thread/162713

Share