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

Archive for Mai, 2008



VMware ESX3.5 Update1 – Fehler in Pegasus install queue

ESX 3.5, VMware No Comments »

Nach einer Neuinstallation eines ESX 3.5 Update1 Hosts ist mir beim Booten ein Fehler beim starten der Pegasus queue aufgefallen. Dies hängt im Zusammenhang ein paar Fehler und fehlenden Files zusammen.

Diskussion im VMware Forum

Der Workaround funktionierte beim mir soweit gut. Anstelle von dem beschriebenen Ordnern 3_files war bei mir alles im Ordner 1_files. Der Rest war soweit korrekt.

Edit the roleauth-schema compiler directive to include the VMware_Identity class definition using

nano /var/pegasus/vmware/install_queue/3_files/mofs/root/PG_Interop/roleauth-schema.mof

Add the bolded line above the pre-existing member directive.

#pragma include (“VMware_Identity.mof”)
#pragma include (“VMware_IdentityMemberOfCollection.mof”)

It also needs to be added in the standard cimv2 path.

nano /var/pegasus/vmware/install_queue/3_files/mofs/root/cimv2/roleauth-schema.mof

#pragma include (“VMware_Identity.mof”)
#pragma include (“VMware_IdentityMemberOfCollection.mof”)

Copy the missing file from the stardard cimv2 path to the shared path.

cp /var/pegasus/vmware/install_queue/3_files/mofs/root/cimv2/VMware_Identity.mof /var/pegasus/vmware/install_queue/3_files/mofs/root/PG_Interop/

Stop and start the service with these commands.

/etc/init.d/pegasus stop
/etc/init.d/pegasus start

Once the scripts completes the install_queues will be empty and the service will start much more quickly.

Links:
http://communities.vmware.com/message/914939#914939

Share


VMware ESX – CPU steigt sprungartig nach VMotion an

ESX 3.5, VMware No Comments »

Aufgrund eines Fehler im VirtualCenter 2.5, in Zusammenhang mit Konfiguriertem HA und DRS, kann nach nach einem VMotion die CPU Performance stark ansteigen. Dies bis zu 100%. Egal ob VMotion manuell oder automatisch via DRS ausgeführt wird.
Aufgetreten ist dieser Effekt bei virtuellen Novellserver. Bei Windows oder anderen Systemen ist mir dies noch nicht bekannt.

Die Beschreibung des Fehlers/Workaround in ist der KB von VMware zu finden.

To work around this issue:

Log in to VirtualCenter with Virtual Infrastructure Client as an administrator.
Right-click your cluster from the inventory.
Click Edit Settings.
Ensure that VMware DRS is shown as enabled. If it is not enabled check the box to enable VMware DRS.
Click OK.
Click an ESX Server from the Inventory.
Click the Configuration tab.
Click Advanced Settings.
Click the Mem option.
Locate the Mem.VMOverheadGrowthLimit parameter.
Change the value of this parameter to 5 and click OK.

To fix multiple ESX Server hosts

If this parameter needs to be changed on several hosts (or if the workaround fails for the individual host) use the following procedure to implement the workaround instead of changing every server individually:
Log on to the VirtualCenter Server Console as an administrator.
Make a backup copy of the vpxd.cfg file (typically it is located in C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg).
In the vpxd.cfg file, add the following configuration between the vpxd and the /vpxd tags:

This configuration provides an initial growth margin in MB-to-virtual machine overhead memory. You can increase this amount to larger values if doing so further improves virtual machine performance.

Restart the VMware VirtualCenter Server Service.

Note: When you restart the VMware VirtualCenter Server Service, the new value for the overhead limit should be pushed down to all the clusters in VirtualCenter.

Links:

http://kb.vmware.com/selfservice/dynamickc.do?externalId=1003638&sliceId=1&command=show&forward=nonthreadedKC&kcId=1003638

http://communities.vmware.com/thread/122229

Share