Fedora to access VMware server 2 web

Similar Questions

• publication order, config to access local server remote-web

  Al hilo mi otro post http://forums.ni.com/t5/LabVIEW/sin-acceso-a-control-remoto-web-publishing/m-p/1497856/highlight/tru... are solved, tengo otro problemilla:

  I have a server local integrated con varios hence donde to banish una scada application runs. Can not get access a control remote, any red ordenador desde (tras varios question fallidos, to consiguio asignandole has the IPv4 cada red useful, the fija del servidor DNS config).

  Well, then be brought desde una conexion externa, claro, pero no con fija the DNS no access or internet tengo acceso al servidor, por direccion http... remote web-publising created por the tool tool. Aunque seguimos investigando, local administrator el y yo creo as cerca, pero momento estamos no hemos dado con the respond.

  What creeis can faltar a mi config, tanto local como labview_v8.5 del servidor del?

  MUCHAS gracias Jorge, por information.

  Todo lo Québec is explica in el link are be habia probado una u otra forma.

  The main problem, I think that is what el servidor is una IP fija, puesto that companies should pay al proovedor telephone what wear ahora esta mas. Además, de dejar el servidor por temas seguridad tal y como esta.

  Logicamente no mi depende, pero to thanks the ayuda.

  No however, TR alguna alternativa en funcion of lo conoces what ha en el Haddad post, comentalo.

  Saludos.

• Access the interface user Web de VMware Server 2 will crash Firefox 3.5

  Hello

  Trying to access the web interface installation of VMware Server 2 running on Enterprise Linux 5 update 2 64-bit

  using Mozilla Firefox 3.5 on XP causes Firefox to crash.

  Previous Firefox 3.0.11 version was able to connect and log in successfully.

  Everything in FF 3.5 cach has been deleted before trying to access the user interface. In addition, the certificate has also been removed before.

  When you access the UI first with 3.5 ist ask to accept the certificate (identical to 3.0.11)

  This will result in a blank page is displayed.

  Closing FF 3.5 (clear cache included) and re-open it at the interface of the web UI that causes FF crash.

  I m the only one to see this problem with the new Firefox 3.5 access to VMware Server 2 Web UI?

  Kind regards

  Agent of

  Although VMware-server - 2.0.1 - 156745.x86_64 has been out for a while, so I just assumed it was your version.

  Silly me

  Hope that cure your problem.

• VMware server on fedora 11

  I'm a newbie to linux. I prepare vmware server on fedora 11. VMware server has been installed by using the default setup of the KDE environment. How to start the console vmware?

  From the prompt, as root, run:

  /usr/bin/vmware-config.pl

• Vmware server Web Access 2 does not work

  Dear vmware community:

  First of all thank you for taking the time to read this.

  I have a problem that looks like this isn't the first time that this happens, Yes, I was still unable to find an adequate solution.

  We have vmware server 2 is installed on a Debian 5 machine. Until yesterday, it was working fine.

  Today, when I tried to access to via web browser as usual, the page not load (the browser would say 'done, but the name of the page says "Loading").

  We have one of the virtual machines that are configured to start automatically, and it does not work as expected. The other I can't handle because I can't have the vmrun run perhaps (related?). So far, the only things that doesn't seem to work is web access only.

  There is one thing to note: after a restart of the computer, or restart the vmware mgmt, the service called "VMware Virtual Infrastructure Web Access" would show anything (while other services say "done" at the end of each line).

  I saw other people with similar problems here, and generally the solution was to reinstall the vmware server all on this machine. I would avoid this of course.

  Did someone already experienced this? Where I can look for more information on the VMware VI Web Access service won't start not (I do not know where are stored the logs of this service, maybe that can help).

  Please let me know if I should add any information, such as newspapers, etc.

  Thank you in advance!

  Hello

  I would recommend you check carefully this post and this post another may also help.

  Have you checked the vmrun documentation? Take a look at the file that I downloaded on this post.

  I would like to know if one of my tips work for you (or not)

  Best wishes / Saludos.

  Pablo

  Please consider providing any useful answer. Thank you!! - Por favor considered premiar las useful responses. ¡¡MUCHAS gracias!

  Virtually noob blog

• How not to VMware Server 2.0.1 Web GUI access from localhost

  It seems that the vmware - hostd.exe only accepts requests from localhost and not from any PC on the network.

  How can I remove this limitation so that I can manage my withou being physically vmware servers with the server (Yes, that includes... Remote Desktop)

  Host operating system: Win Srv 2003

  VMWare server: 2.0.1

  Google did not all solutions...

  Thanks in advance

  Bjoern Dirchsen

  What if you try https://: 8333 or https://vmserver1:8333 (without option)

  Try to use the FULL domain name to connect.

  J.

  If you have found this device or any other answer useful please consider the use of buttons useful or Correct to award points.

  Post edited by: janlib

• vSphere WEB client falha ao try access o Serviço SRM

  Estou logando no vSphere Web client e e quando tento access o SRM appears uma falha atenticacao mensagem e os sites are offline. Very ja alterei a senha da conta do Serviço SRM e mesmo assim nao works.

  A conta pra instalar o e a mesma as esta utilizando atualmente SRM used? Caso afirmativo, o fato ter alterado senha pode ter glass o funcionamento do SRM, uma vez that essa senha armazenado fica na base RS, e para atualiza - e rodar o instalador SRM e again Chipre selecionar o option change.

  O bind a seguir mostra em details o principle: VMware KB: change the account to access the server vCenter Site Recovery Manager

• VMware Virtual Infrastructure Web Access won't start not

  Hi all

  I'm a little puzzled. Yesterday my vmware server 2 was working fine, but today it does simply not at all. Or rather vmware server seems to work, but web access won't start so I can't access it.

  I created a log of errors of the problem by changing the start of web access line in vmware-mgmt to send the log to a file instead of dev/null and the result which is attached to the file. I can't make heads or tails of it, but I hope someone can help me. I have re-installedvmware Server 2 times, but it does not help.

  The host is under ubuntu 9.04 and the guest is windows xp. As I said, everything worked without problem yesterday, but today it won't work/start.

  Hoping that someone will know what to do!

  Hello

  Perhaps with the failure, vmware server became unstable. Then put back in place a clean vmware server is necessary.

  To do this, all you need is to run ' vmware - uninstall.pl ' and then do a clean install using the script that I told you.

  Remove it and install check is all vmware remains of zombie process in running and kill them.

  You will not lose the virtual machine, but are always a good idea to make a backup. During the installation of vmware server all you need is pointing to the directory containing the files of the virtual machine.

  If you have problems with vmware vmware hostd.log and/var/log/vmware proxy.log after install the own reach and we will check.

  Best wishes / Saludos.

  Pablo

  Please consider providing any useful answer. Thank you!! - Por favor considered premiar las useful responses. ¡¡MUCHAS gracias!

  Virtually noob blog

• Could not load the interface Web VMware Server 2

  Hello

  It seems that there have been a number of users has a problem similar to mine. Unfortunately so far it seems not be an easy fix. A few weeks ago, I downloaded VMware Server 2.0.2 and installed on my Ubuntu 8.04 Server. Surprisingly, it worked very well and I set up a virtual machine via the web interface. It took 3 weeks later I started having problems. Or, when I tried to access the web interface through the browser page just came not upward or it came I have connected, but then was then put on the door.

  Initially, I have done the following but doesn't seem to help.

  -Reboot the system

  -Restart all vmware services

  -Delete all cookies and cache.

  Then I thought that this question had to do with the process of webaccess. It seems that the process was not because for a very short period of time, the connection appeared and I was able to connect. But after a short period of time, it displays an error and then the connection was unreachable again.

  I checked the port 8308 below:

  netstat - LNP | grep: 8308

  TCP 0 0 0.0.0.0:8308 0.0.0.0: * LISTEN 5754/webAccess

  Here is the response from audit ipv6:

  netstat - LNP | grep tcp6

  ping6-c1 localhost

  Unknown host

  I disabled it by changing of ipv6 on off in the etc/modprobe.d/aliases.

  My hosts file resembles the following:

  127.0.0.1 localhost

  127.0.1.1 web web.cinci.rr.com

  The following lines are desirable for the hosts with IPv6 support

  : 1 localhost ip6 ip6-loopback

  FE00::0 ip6-localnet

  FF00::0 ip6-mcastprefix

  FF02::1 ip6-allnodes

  FF02::2 ip6-allrouters

  FF02::3 ip6-allhosts

  I have attached the file proxy.log. I saw a few exceptions so don't know if this has to do with the problem.

  Also, I've included the hostd.log (it's in a zip archive because there are a few files of newspapers spend). I have

  Finally, I checked all the active internet connections and sockets. The results are below:

  Connections Internet active (only servers)

  Name of Proto Recv-Q Send-Q address foreign address State PID/program Local

  TCP 0 0 127.0.0.1:8005 0.0.0.0: * LISTEN 6910/webAccess

  TCP 0 0 0.0.0.0:902 0.0.0.0: * LISTEN 6888/vmware-authdla

  TCP 0 0 0.0.0.0:8009 0.0.0.0: * LISTEN 6910/webAccess

  TCP 0 0 0.0.0.0:8333 0.0.0.0: * LISTEN 6994/vmware-pass

  TCP 0 0 0.0.0.0:80 0.0.0.0: * LISTEN 4917/apache2

  TCP 0 0 127.0.0.1:8307 0.0.0.0: * LISTEN 6994/vmware-pass

  TCP 0 0 0.0.0.0:8308 0.0.0.0: * LISTEN 6910/webAccess

  TCP 0 0 0.0.0.0:23 0.0.0.0: * LISTEN 4421/sshd

  TCP 0 0 0.0.0.0:443 0.0.0.0: * LISTEN 4917/apache2

  TCP 0 0 0.0.0.0:8222 0.0.0.0: * LISTEN 6994/vmware-pass

  UDP 0 0 0.0.0.0:68 0.0.0.0: * 4393/dhclient3

  brute 0 0 0.0.0.0:1 0.0.0.0: * 7 6634/vmnet-natd(8)

  UNIX domain sockets active (only servers)

  Proto RefCnt flags Type State I-node PID/name path of the program

  UNIX 2 BDRM STREAM LISTEN 16158 6994/vmware-pass/var/run/vmware/root_0/1267514173386057_6994/ha-nfc-fd

  UNIX 2 BDRM STREAM LISTEN 16165 6994/vmware-pass/var/run/vmware/root_0/1267514173386057_6994/ha-nfcssl-fd

  UNIX 2 BDRM STREAM LISTEN 16167 6994/vmware-pass/var/run/vmware/proxy-Web server

  UNIX 2 BDRM STREAM LISTEN 16189 6994/vmware-pass/var/run/vmware/root_0/1267514173386057_6994/hostd-vmdb-fd

  UNIX 2 BDRM STREAM LISTEN 16191 6994/vmware-pass/var/run/vmware/proxy-mob

  UNIX 2 BDRM STREAM LISTEN 15714 6634/vmnet-natd(8) /var/run/vmnat.6634

  UNIX 2 BDRM STREAM LISTEN 11895 4940/python /var/run/fail2ban/fail2ban.sock

  Finally, just to try to "start over". I removed VMware Server system and reinstalled. Since the virtual machine is in a separate Directory I thought I had nothing to lose. Removal and resettlement seem to succeed. After a reboot and an attempt to access the interface web it STILL didn't work. I'm really at a loss right now. Any help would be much appreciated.

  Thank you

  Aaron

  Hello

  Welcome to

  Don't forget to give my answer. It is the way to give users of vmware communities who helps others.

  Best wishes / Saludos.

  Pablo

  Please consider providing any useful answer. Thank you!! - Por favor considered premiar las useful responses. ¡¡MUCHAS gracias!

  Virtually noob blog

• need help to set the access rights of a vmware server 2.0.1 on vmware image

  Hello!

  I have a vmware (running ubuntu server 9.04) image that was created with a vmware server installation varsion 1.0.9. now I decided to upgrade to the host, which means that the host totally changed: new equipment, new OS, new vmware-server-version: 2.0.1

  My problem atm is, I may not know, what would be the appropriate access rights (chown/chmod) for this vmware image. during the installation of vmware server 2.0.1 I was asked to specify some 'administrative user' where I took the an im working with Linux itself (lets call it "user").

  so, when I copied the old vmware image in the data store (/ var/lib/vmware/VirtualMachines for me), chown-ed the folder including all files init by A, setting chmod to something like 600, the console vmware (web surface) told me that there were several problems with the image and couln can't be started etc. etc. etc...

  I played with several rights to the image and the only thing that seemed to help was setting the folder and all files included in 'root' with the command chmod chown '777'... not what I would call 'secured '.

  so: how to set the access rights for the virtual machines? I want that they have only minimal rights as possible and especially nothing like root: 777...

  My static VM files, as in those who are not dynamically created when the virtual machine starts, are the property of root, root of group with permissions of 711. Root is the user that I have chosen as the admin user when you run vmware - config.pl. My users do not have direct access to this server, so I'm not too worried about the permissions. You can give different rights for different users to different virtual machines, creating roles and their allocation to users/groups. On that, the details are in Chapter 10 of the user guide - http://www.vmware.com/pdf/vmserver2.pdf.

  Guy Leech

  VMware vExpert 2009

  ---

  If you have found this device or any other answer useful please consider the use of buttons useful or Correct to award points.

• ERROR with 2.6.29.4 - 167.fc11.i686.PAE kernel FEDORA 11 & VMware-server - 2.0.1 - 156745.i386.rpm

  I was unable to boot VMware-server - 2.0.1 - 156745.i386.rpm with my new fedora 11 due to the following error... any idea?

  -error-

  /usr/bin/vmware-config.pl

  Ensuring services for VMware Server are stopped.

  Stopping VMware services:

  VMware authentication daemon

  Virtual machine monitor

  None of the vmmon modules pre-built for VMware Server is suitable for your

  kernel running.  Do you want this program to try to build the vmmon module for

  your system (you must have a C compiler installed on your system)?

  Using compiler "/ usr/bin/gcc". Environment variable CC to override.

  What is the location of the directory of C header files that match your running

  kernel?

  /lib/modules/2.6.29.4-167.FC11.i686.PAE/build/include

  Extract the sources of the vmmon module.

  The construction of the vmmon module.

  Using 2.6.x kernel build system.

  do: enter the directory ' / tmp/vmware-config3/vmmon-only '.

  do /lib/modules/2.6.29.4-167.fc11.i686.PAE/build/include/ - C... SUBDIRS = $PWD SRCROOT = $PWD. modules of

  make [1]: Entering directory ' / usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

  CC /tmp/vmware-config3/vmmon-only/linux/driver.o

  In file included from /tmp/vmware-config3/vmmon-only/linux/driver.c:31:

  /tmp/vmware-config3/vmmon-only/./include/compat_wait.h:78: error: conflicting types for 'poll_initwait '.

  include/Linux/poll.h:67: Note: previous declaration of 'poll_initwait' is here

  In file included from tmp/vmware-config3/vmmon-only/./include/vmware.h:38,

  from /tmp/vmware-config3/vmmon-only/linux/driver.c:99:

  /tmp/vmware-config3/vmmon-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined

  In file included from tmp/vmware-config3/vmmon-only/./include/vcpuset.h:103,

  of tmp/vmware-config3/vmmon-only/./include/modulecall.h:37.

  of tmp/vmware-config3/vmmon-only/./common/vmx86.h:33.

  of tmp/vmware-config3/vmmon-only/linux/driver.h:29.

  from /tmp/vmware-config3/vmmon-only/linux/driver.c:101:

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined

  In file included from tmp/vmware-config3/vmmon-only/./include/vm_basic_asm.h:46,

  of tmp/vmware-config3/vmmon-only/./include/rateconv.h:45.

  of tmp/vmware-config3/vmmon-only/./include/modulecall.h:40.

  of tmp/vmware-config3/vmmon-only/./common/vmx86.h:33.

  of tmp/vmware-config3/vmmon-only/linux/driver.h:29.

  from /tmp/vmware-config3/vmmon-only/linux/driver.c:101:

  /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:62:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:177:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:346:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_basic_asm_x86.h:453:7: warning: "_MSC_VER" is not defined

  In file included from tmp/vmware-config3/vmmon-only/./include/vm_asm.h:43,

  from /tmp/vmware-config3/vmmon-only/linux/driver.c:103:

  /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:486:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:779:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:820:7: warning: "_MSC_VER" is not defined

  /tmp/vmware-config3/vmmon-only/./include/vm_asm_x86.h:922:7: warning: "_MSC_VER" is not defined

  In file included from /tmp/vmware-config3/vmmon-only/linux/driver.c:119:

  /tmp/vmware-config3/vmmon-only/./common/hostif.h:53:7: warning: 'WINNT_DDK' is undefined

  /tmp/vmware-config3/vmmon-only/Linux/driver.c: in function 'LinuxDriverSyncCallOnEachCPU ':

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1423: error: too many arguments to function 'smp_call_function '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c: in function 'LinuxDriver_Ioctl ':

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'euid.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1987: error: 'struct task_struct' has no member named 'uid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'fsuid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1988: error: 'struct task_struct' has no member named 'uid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'egid.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1989: error: 'struct task_struct' has no member named 'gid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'fsgid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:1990: error: 'struct task_struct' has no member named 'gid '.

  /tmp/vmware-config3/vmmon-only/Linux/driver.c:2007: error: too many arguments to function 'smp_call_function '.

  make [2]: * /tmp/vmware-config3/vmmon-only/linux/driver.o error 1

  make [1]: * error 2

  make [1]: leaving directory ' / usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

  make: * http://vmmon.ko error 2

  make: leaving directory ' / tmp/vmware-config3/vmmon-only '.

  Unable to build the vmmon module.

  For more information about how to troubleshoot module, please

  visit our Web site at " " http://www.VMware.com/go/UNSUP-Linux-products "and "

  " http://www.VMware.com/go/UNSUP-Linux-tools ". "

  The execution is canceled.

  Look here for the patch to module 2629 vmware servers: http://communities.vmware.com/message/1261181

  It worked for me with F11, although I'm not 64-bit.

  Jeff

• No web console with the version of VMware Server is a core 2.0.1 and 2.6.31 - 10-generic in Karmic AMD64

  Hello

  I've successfully used vmware - server.2.0.1_x64 - modules - 2.6.30.4 - fix.patch to build modules on my laptop running Ubuntu Karmic Koala. VMware Server version is VMware server 2.0.1 - 2.0.1 - 156745.x86_64.tar.gz, and I'm running it with kernel 2.6.31 - 10-generic. The question I have is that while the web console seems to be running on port 8333, I can't get an answer from him. Has anyone else encountered this problem? See you soon.

  OK, I got it to work. Try this in a terminal and let me know if it works for you too:

  VMWARE_USE_SHIPPED_GTK = force. Mozilla/Firefox/*.default/extensions/[email protected]/plugins/vmware-vmrc

  See you soon,.

  Peter

• VMWARE Server 2 and Red Hat 5.4 Interface Web ES crashes

  I have been using VMWare Server 2.0.1 fine several months until I've restarted my server in a new kernel.

  Although all modules start OK in the window of the terminal web interface seems to hang after have been up for a few seconds only - sometimes barely enough to open a session.

  Any ideas?

  My hardware is Dell R900 - 4 image intel CPU with 128 GB of ram

  My OS is Red Hat Linux ES version 2.6.18 kernel - 128.2.1.el5

  Thank you

  I came across the same issue last week. This is the background I and fix that made me backup for now.

  It seems that vmware provides their own libraries for some of what they need and that there may be a bad interaction between that and RHEL 5.4 libraries updated.

  The FIX:

  yum downgrade glibc glibc-common

  Delete it / come back about 22 packages/dependencies. Then I restarted and re - represented vmware-config and functions of each thing. Note You must change your configuration of yum update so that it is not pushing the new glibc glibc-common until this problem gets solved official.

• Access to the customer via VNC in VMWare Server 2 (has that changed?)

  In earlier versions of VMWare server, it was possible to connect to a virtual computer remotely via a VNC client (or customer using this Protocol). Test with VMWare Server 2 that doesn't seem to work. I know that via the Web Interface, they start their own remote console player. Does anyone know if it uses another protocol of VNC (RFB) such as used previously? Actually now is no longer an open soluton?

  I think you should also add the RemoteDisplay.port = "5900" (or whatever port you want) as well.

• Move a VM from VMWare Workstation 7 to VMWare Server 2

  Hi all:

  I had to create a virtual machine in VMware Workstation 7 manually prepare and now I need to move it to VMWare Server 2, which is used to run automated tests. It is our usual working process.

  I would like to know if there is a problem with it, because the process of setting up the machine took several hours, install programs, and to configure, you know.

  Should I edit the .vmx file? I copied the machine using scp, since the destination that VMware Server is installed on a remote computer; I can access which the machine in ssh and web.

  Thanks in advance for your attention and your time and best regards,

  Luis

  If the virtual machine was powered (non-suspended) offshore before moving them to the destination, you should be able to turn on without problems. Both VMware Workstation 7.x and VMware Server 2.x can use hardware virtual version 7 (http://kb.vmware.com/kb/1003746), which is probably the most important thing.

  If you don't know, create a snapshot before you turn on the virtual machine to the remote site, in this way that the virtual disks have changed.

  If the copied virtual machine snapshots, you will not be able to come back to them on the new hardware if they were taken while the virtual machine is running.

  André