| vSphere Client Version | Lien de téléchargement |
| VMware vSphere Client v4.1 Update 1 | VMware-viclient-all-4.1.0-345043.exe |
| VMware vSphere Client v4.1 Update 2 | VMware-viclient-all-4.1.0-491557.exe |
| VMware vSphere Client v5.0 | VMware-viclient-all-5.0.0-455964.exe |
| VMware vSphere Client v5.0 Update 1 | VMware-viclient-all-5.0.0-623373.exe |
rpm -qa | grep hyperDans mon cas les paquets retournés sont :
microsoft-hyper-v-rhel6-43.1.x86_64Pour enlever les paquets on exécute "rpm -e"
kmod-microsoft-hyper-v-rhel6-43.1.x86_64
rpm -e `rpm -qa | grep hyper`On redémarre le serveur et on peut procéder à la migration.
VBoxManage.exe clonevdi "Windows XP.vdi" "Windows XP clone.vdi"Voici ce que vous obtiendrez
Oracle VM VirtualBox Command Line Management Interface Version 3.2.12
(C) 2005-2010 Oracle Corporation
All rights reserved.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
1. sudo -i
2. apt-get update
3. apt-get upgrade
4. apt-get install build-essential binutils linux-headers-$(uname -r)
5. mount /dev/scd0 /cdrom
6. cp -a /cdrom/VMwareTools* /tmp/
7. cd /tmp/
8. tar -vxzf VMwareTools*.gz
9. cd vmware-tools-distrib/
10. ./vmware-install.pl
As other users have pointed out, the VMDebug error is misleading. That driver is only useful for Replay Debugging in VMware Workstation. Fusion doesn't support Replay Debugging, so the driver doesn't start. However, this shouldn't cause any slowdowns. There seem to be other issues with Tools that some users are experiencing, resulting in either high CPU usage or slow Shared Folder performance, and may be the cause of the startup delay. We're trying to determine what causes them so they can be fixed.
If you would like to get rid of the error from the event log, you can turn off the VMDebug driver with regedit. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmdebug and change the Start key from 1 to 4 to disable it.
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 /i eventcls.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
Petite mise en garde, si vous prévoyez l'utiliser avec plus de 1200 utilisateurs, vous avez soit l'option d'installer Microsoft Windows 2003 en anglais ou désinstaller le mise à jour de sécurité MS09-012.To set the maximum size of the JVM heap for the Tomcat service and the Message Bus service:
- Start Registry Editor by running regedit at the command prompt.
- In the navigation area, locate the parameters subkey of the Tomcat service:
HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wsnm\tomcatService\Params- In the topic area, right-click the JvmOptions key entry, and select Modify. The Edit String dialog box appears with values similar to the following in the Value data field:
-Xmx parameter. Do not change the values of any other parameters in the Value data field.
-Xms128m -Xmx1024mModify the argument to the -Xmx parameter so that it reads -Xmx750m, for example:
-Xms128m -Xmx750mNote: The values of the arguments to the -Xms and -Xmx parameters represent the initial size and the maximum size of the JVM heap respectively. The value for the -Xms parameter must be less than or equal to the value for the- Repeat step 3 for the parameters subkey of the Message Bus service:
HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wsnm\messageBusService\Params- Click OK and exit Registry Editor.
- Restart the system.
