Open a virtual machine in a san on 2 different esx hosts

Hi, I have a Vsphere essentials, 2 Esx hosts and an Iscsi san, I need to connect the virtual machine in the two esx hosts (I know I don't have FT and HA), in order to launch the virtual machine never the first Esx and if first host, does not have the virtual machine on the second esx.

I tryied to connect the virtual machine to the second host, but the Vsphere client tell me that's not possible, because the virtual machine is already present at the first ESX.

There is a way to establish this setting?

For some it may depend on your application, if you can run multiple instances of the same application? If it is a web application? It stores its data in files on the server, or it stores it in a database locally? or remote database?

-VM on a local storage of the army, would not really recommended if you need so that it starts the VMS on host b quickly.

-If the two hosts have access to permits it storage even say and what the application can really be run only once.  He could only save it to HostA and if it fails at some point that it will be released the lock, have it on the virtual machine and you will be able to manually register the virtual machine to host b and start the virtual machine.  However, you will not be able to really get ahead.

-HA out of here, as if a host or power failure shuts on HostA, HostB will feed into the virtual machine down automatically

-FT - here in the spectrum creates a VM ghost on the secondary host in levels (what happends on HostA happens on host b)

-Another option to the other end of things has implemented Microsoft MSCS Clustering with iSCSI support I think.  You can run VMS with iSCSI to your San and clustered like this application.  Just note that with iscsi client it uses some CPU to create iscsi packets.

-Web Cluster, Cluster database.    It doesn't matter if one of the nodes of web servers or the database nodes go down really that the user will be redirected to another node in the cluster so really no need for HA/FT.

Of course, with some of the here above are expenses and pro / con of and there's a few ways to increase availability.

Tags: VMware

Similar Questions

  • Open a virtual machine to different hardware

    Hello

    I read in the documentation center, it's good, as long as all the files are copied correctly, to open a virtual machine on a different host computer with different hardware.

    My question is this, will be the new host with a different material, the original host, recognize the virtual machine snapshots, I had? I could not find that answer, and despite in collaboration with VMware for a year I never found in this situation.

    This virtual machines are very important, they have my TI final degree of engineering project, but my phone no longer works.

    Everything will work as before right?

    Thank you all!

    Hi, Carlos

    and welcome to the forums!

    You are right: If you copy the whole directory to the VM to another machine and open the vmx file in VMware Workstation it then you will have the virtual machine available in exactly the same State as on the old machine (incl. images.).

    If you want to have a backup of the virtual machine, then you can just copy the whole directory of the virtual machine to another location. It is perhaps a good idea in your situation.

    Andreas

  • What is the open file Virtual Machine vCenter web console?

    What is the open file Virtual Machine vCenter web console?

    I have about 20 MV listed here and the rest under VMS.

    Thank you

    Dan

    Records are a method of setting permissions in VMware vCenter. They form a triage unit and behave as a logical separation. When you first add the hosts to vCenter and you have all the files, there will be a default folder created for you as Richardsonporto mentioned.

    Later, you can create new folders and separate the virtual machine by drag-and - drop of their.

  • In opening the virtual machine: "could not find a peer valid to connect to" or "error of Transport (VMDB) - 32" / "-14" ""»

    Hello

    Since yesterday after a reboot of my host (DELL E6410, W7 SP1 64-bit, 8 GB RAM, 2x750GB SATA3 running WorkStation 9.0.2 Update Windows Update), I can't open my existing VM.

    I often get "can not find a valid peer to connect to" and sometime before: "Transport (VMDB) - 32 error: Pipe: reading is not'or'error of Transport (VMDB)"-14: fitting broke

    I worked for 2 years on this machine without a hitch, WS7 reclassification in WS9 without any problem.

    FYI: we have changed the domain 3 months ago, but it has never be a problem.

    I have google and search several Forum. So far, I tried to:

    -restart the service vmware-auth as an administrator

    -launch vmware.exe administrator

    stop/start the vmx86 service

    -uninstall / reboot / install Workstation.  3 times. First using uninstall from the Control Panel, then doing a / clean before installation and finally track down any file/reg entry.

    -HE asked if any group policy changes were made recently (like not allowing to run vmware.exe?)

    -Rename vmware.exe (logs I look similar to what is in this post: http://communities.vmware.com/thread/331099?start=0 & tstart = 0 ... but no luck)

    -excluded vmware.exe in my AV (Microsoft ForeFront). Unfortunately, in that I'm not allowed disabled...

    -Open the virtual machine using the drive == > does not work either.

    This isn't a file corrupted in a virtual machine (even backup - 7zipped - don't work on my laptop... but the launch on the other).

    Even a newly created WM (boneless), unbootable! :-(

    *, BUT to BE NOTE *: if a virtual machine is created as a shared virtual machine, I can start the application locally remotely! And this same VM, if started (via the.vmx) does not work using Workstation GUI!

    I have attached 2 newspapers. Work a (vmware.log remotely) and the inactive (vmware-vmx - 4072.log thru WS GUI).

    Of after what I saw (and what little I understand), it's as if the CPU is not detected?

    The two newspapers have this line:

    FeatureCompat: EVC masks:

    but the non-working goes - we with

    Module CPUID initialization failed.

    While working it display information on CPU (hostCPUID name / family / type... etc...)

    Any idea is welcome.

    I'll answer me to my problem!

    A lot of research to this knowledge.

    In summary: don't mess with the processor affinity... or keep it in mind!

    Response to distinguish:

    I installed 6 months ago a small utility named prio (search for "PRI prnwatch"), because it can save the priority of a given process. What I did notice, is that it also save the processor affinity ! What happened: I probably changed the affinity once for a VM running to give greater priority to a 7zip archive process to complete more quickly (setting HT no core to 7zip and one - or 2? - HT core to VM). Everything works until the next reboot, where the CPU detection during * start EVERY * VM has been somewhat "damaged" leading to the wrong log message: failed initialization Module CPUID.

    This is the reason of *my* question. Perhaps it might help someone else?

    TIPS:

    For advanced people who do not want to check the processor affinity of each process in the Task Manager, you can try this Windows Powershell command (remember to launch PowerShell as an administrator):

    Get-Process | Format-Table-PriorityClass name, ProcessorAffinity property

    ProcessorAffinity column gives the number of representation of the authorized core, 1-bit by heart.

    15 = 1111 is all possible core (for a logical processor 4). Mine is 1 CPU with 2 core HT <=>4.

    LSB is the core lowest. So if you allow only core0 and core3 (1001) on a process, the number of ProcessorAffinity will be 9...

    Post edited by: cbiero (LSB and MSB...)

  • Could not open the virtual machine

    I used the customer convertor to create this virtual machine from one which works well on ESxi.  When I try to open on Win7-64 machines running vmplayer 3.1.4 I get the following error:

    Could not open the virtual machine: file "D:\Data\VM Machines\WW S2008_32\WW S2008_32.vmx 10_1 10_1" line 1: syntax error.

    Any ideas?

    "" "WW 10_1 S2008_32.vmx.zip" attached file contains the "WW 10_1 S2008_32.vmx" file created under VMware Player 3.1.4 and was then modified to reflect the values of parameter that you might want to stay the same as uuid etc.  Start VMware Player and then check the settings before running the virtual machine.

  • Getting error: could not open the Virtual Machine: failed to query the Source for more information

    When I have a virtual machine to export to the FVO on an ESXi 4.0 and then try again to import the FVO on VMware Player or Workstation 7.1, I get the following message:

    «Could not open the Virtual Machine: failed to query the Source for more information.» I can successfully re-import this file OVF in an ESXi server without any problems. Anyone know why this is happening and what can be done to remedy this?

    Thank you

    Christopher

    Hello.

    Try to use ovftool to convert a VMX of the FVO.

    Good luck!

  • What should I do to use Workstation to open a virtual machine created by the merger?

    Because my MBP is in the shop for repair, I need to use on a PC Workstation to open my VM created by Fusion on a Mac. I copied the VM to a NTFS drive and thought, I'd go, but when I try to open the virtual machine in the Workstation 6.0.5 build 109488, I get a message saying that the configuration of the virtual machine file contains features not supported by this version of Workstation. What should I do to access this virtual machine? I have more access to the merger, because it is on the machine in for repair.

    Update your workstation 6.5.x (current latest version is 6.5.1) in support of hardware virtual version 7.

  • NLB - two virtual machines can't ping eachother when on separate hosts

    Greetings,

    I've been running some tests with NLB on the different desks as recommended here:

    http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & externalId = 1006558 & sliceId = 1 & docTypeID = DT_KB_1_1 & dialogID = 42912404 & StateID = 0% 200% 2041454115

    http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & externalId = 1006778 & sliceId = 1 & docTypeID = DT_KB_1_1 & dialogID = 42912404 & StateID = 0% 200% 2041454115

    I found that Unicast works better in our network environment, but it is still a problem:

    In http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & externalId = 1006580 & sliceId = 1 & docTypeID = DT_KB_1_1 & dialogID = 42912690 & StateID = 0% 200% 2041454807

    He says: "since all hosts in the cluster have the same IP Address and the same MAC address, there is no communication possible inter-hote between the hosts configured in unicast mode.» A second NETWORK adapter is required for any other host communication. »

    However, even with a second NETWORK adapter the virtual machines cannot ping eachother when they are on a different esx host. When they are on the same host esx virtual machines can ping each other. Also, when they are on different hosts, so that a virtual machine cannot reach each other on their dedicated IP address, virtual machines can reach other when ping the second card NETWORK (the one without an informed gateway).

    For example, the next 2 guests are connected unicast:

    VM1 has 2 network cards, NIC1 = 172.18.18.41 with gateway (dedicated IP) and NIC2 = 172.18.18.43 without gateway / WLBS enabled.

    VM2 has 2 network cards, NIC1 = 172.18.18.42 with gateway (dedicated IP) and NIC2 = 172.18.18.44 without gateway / WLBS enabled.

    When on the same ESX host VM1 can reach VM2 on 172.18.18.42 and 172.18.18.44, and vice versa.

    When on ESX different hosts VM1 cannot reach VM2 on 172.18.18.42 but it can reach VM2 thanks 172.18.18.44. In this case VM2 cannot reach VM1 on 172.18.18.41 but can reach VM1 on 172.18.18.43.

    I followed and applied the settings recommended in this article: http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & externalId = 1556 & sliceId = 1 & docTypeID = DT_KB_1_1 & dialogID = 42912404 & StateID = 0% 200% 2041454115

    I even tried the kb from microsoft as shown here: http://support.Microsoft.com/kb/898867 even if the virtual machines have 2 network cards, but of course that did not help either.

    Does anyone have an idea what is happening here?

    The fact that it works on the same host, but not on different hosts type advanced to a network within VMware issue.

    Thanks in advance,

    Bram

    It seems that ir can be a problem of IP routing, even with the hosts on the same subnet.  Make sure that your routing table that traffic on each that is to/from your mgmt that ips turns off your local management interface.  If it isn't, then update your routing table in order to.

    Or, you could try setting up your mgmt network cards on a different subnet from your IP NLB.  I suspect that this will solve the problem.

    JP

  • Move a virtual machine from one SAN to another

    Top o ' the morning, tech heads,

    I have a VM, I need to move from one san to another. I think I'll need to shut down the guest operating system, download all the files (see image), create a lun on the san of destination, then download the files to that lun. Lack of vmware 5.5. Is that what that sounds right?

    Your ESXi host vSphere is a stand-alone type or is managed by vCenter? If managed by vCenter, just make a Storage vMotion... If not, take a look at this article: VMware KB: move or copy of a virtual machine in a VMware environment

  • Could not open the virtual machine after Windows blue screen

    I updated my machine Windows 8, he projected blue, now I can't open my VM that I had open at the time of the blue screen.

    This is the message that I received from VMware Workstation 10 attached.

    Search for files of *.lck in virtual machine directory - delete them all.
    Also delete the directories named *.lck

    Then try again - if it still does not need more details

  • File not found error when opening a virtual machine (from No-Time Machine backup)

    Hello world

    I have a problem with my installation of Fusion 2.0.6 on my iMac to Snow Leopard related to a "file not found".  I did my best to analyze the positions of the community to see if anyone has experienced this before.  I found several posts and tried the suggestions in these posts, but I have not been able to solve.

    I'm trying to restore from a full backup of my XP VM. It's not a backup Time Machine; just a straight backup of VM together using SuperDuper (part of my nightly backup routine).  To restore, I copied:

    -> BACKUP/users/John/Documents/Virtual Machines/Windows XP Home Edition.vmwarevm

    for -> MacHD/users/John/Documents/Virtual Machines/Windows XP Home Edition.vmwarevm

    Merge, I opened the Windows XP Home Edition VM, only to get the error:

    «File not found: Windows XP Home Edition-000005 - s001.vmdk.» This file is required to power on this virtual machine.  If this file has been moved, please provide its new location. »

    I find the file hard (what is there) and get the same error message several times.

    Interestingly, when I try to open the same VM from the backup location, I also get the same error.

    Really stuck now and don't know what to do.  Any help that can be provided would be greatly appreciated.

    Thank you

    John

    It seems that the latest files are missing. The virtual disk which I guess has a size 5-6 GB provisioned consists of 3 files, of which 2 are missing for snapshot 000005 (Windows XP Home Edition-000005 - s002.vmdk and Windows XP Home Edition-000005 - s003.vmdk). Unless you have some backup, your options are limited and you will need to go back to the last instant whis is dated March 2012.

    Windows XP Home Edition - 000005.vmdk descriptor file (text file) will show the files that make up the virtual disk (the Flash disk in this case).

    André

  • black screen, when you open the virtual machine console

    Hi guys need help in answering the following questions:
    When you open the console of the virtual machine, the connection process is fine, but it stops at a black screen

    Screen.jpg

    That's what I use:
    (1) Windows 7 x 32
    VMRC 2) 5.1.0.20447
    (3) Mozilla Firefox 18.0.1
    (4) VMware vSphere Client 5.1
    (5) Vcloud 5.1.0.810718

    Here is my log:

    13/01/29 10:15:42.100 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
    29-01-2013 10:15:42.101 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
    {{2013-01-29 10:15:42.101 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}, VMRC_EVENT_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance"vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C}"ID - 2 modes - message mode has 2-3
    29-01-2013 10:15:42.101 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
    29-01-2013 10:15:42.103 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
    29-01-2013 10:15:42.821 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
    29-01-2013 10:15:42.821 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
    {2013-01-29 10:15:42.832 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{135627FE-3BDE-45F6-8234-053307C0876C]}
    29-01-2013 10:15:42.833 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
    29-01-2013 10:15:42.845 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
    29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:379] 10:15:43.901: control of the VM has not been created
    29-01-2013 10:15:43.902 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
    29-01-2013 10:15:43.909 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
    29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.909: control of the VM has not been created
    29-01-2013 10:15:43.923 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
    29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.923: control of the VM has not been created
    29-01-2013 10:15:43.925 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
    29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:15:43.925: control of the VM has not been created
    29-01-2013 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
    29-01-2013 10:15:44.275 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
    {{2013-01-29 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}, VMRC_EVENT_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance"vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD}"ID - 2 modes - message mode has 2-3
    29-01-2013 10:15:44.275 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
    29-01-2013 10:15:44.276 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
    29-01-2013 10:15:44.957 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
    29-01-2013 10:15:44.957 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
    {2013-01-29 10:15:44.958 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{9340F800-963A-46AF-9EBB-CCCFF83FC2CD]}
    29-01-2013 10:15:44.959 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
    29-01-2013 10:15:44.970 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
    29-01-2013 10:15:46.770 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
    29-01-2013 10:15:46.770 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3
    {{2013-01-29 10:15:46.771 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:191]: start: VMRC_MONIKER_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}, VMRC_EVENT_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}, 5.1\Firefox\vmware-vmrc.exe C:\Program Files VMware Remote Console Plug-ins, "C:\Program Files\Common VMware Remote Console Plug-in 5.1\Firefox\vmware-vmrc.exe - parent-PID 6316 - instance ID 'vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996}' - mode 4 - message mode has 2-3
    29-01-2013 10:15:46.771 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:205]: process of creating VMRC
    29-01-2013 10:15:46.772 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:220]: loop from MsgWait
    29-01-2013 10:15:47.339 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/common/ScriptableObject.cc:321]: ID of property not found: onMessage
    29-01-2013 10:15:47.339 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/common/VmrcPlugin.cc:2548]: onMessage Manager call failed
    29-01-2013 10:15:47.379 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:229]: A WAIT_OBJECT_0
    29-01-2013 10:15:47.379 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:256]: expect successful moniker
    {2013-01-29 10:15:47.380 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:149]: link to [VMRC_MONIKER_vmrc-np-t-{381FF1D3-DBD1-4B19-A516-5CA7DEE58996]}
    29-01-2013 10:15:47.381 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:154]: BindToObject managed
    29-01-2013 10:15:47.388 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:217]: successful startup
    29-01-2013 10:17:20.197 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
    29-01-2013 10:59:13.788 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
    29-01-2013 10:59:13.792 [d:/build/ob/bora-781747/bora/apps/vmplayer/win32/plugin/procControl.cpp:633]: no associated window with control of the virtual machine
    29-01-2013 10:59:15.303 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
    29-01-2013 10:59:15.308 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
    29-01-2013 10:59:15.324 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
    29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:15.324: control of the VM has not been created
    29-01-2013 10:59:15.326 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
    29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:15.326: control of the VM has not been created
    29-01-2013 10:59:33.283 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:246]: called stop
    29-01-2013 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:251] 10:59:33.284: control of the VM has not been created
    29-01-2013 10:59:33.540 [d:/build/ob/bora-781747/bora/apps/vmplayer/npplugin/win32/VmrcDelegateImpl.cc:174]: startup called
    29-01-2013 10:59:33.540 [d:\build\ob\bora-781747\bora\apps\vmplayer\npplugin\win32\.. /.. /plugin-common/utils.h:145]: advanced configuration analyzed characteristics: 3

    Windows 7 x 32

    That's kinda our old friend is back.

    Two checklists

    1. check the version of the VM VGA driver, if that's the case, you must update the WDDM driver display driver.

    2. make sure that you use HW 7 and more.

    More info here

  • HELP: VMware Fusion does not open a virtual machine

    Hi *.

    suddenly, I had a big problem with merging om Mac OS X 10.6. If I try to boot my virtual machine by opening the .vmx file, merger tells me that is is not possible to open, because it's a file "Steinberg VST mixer Stettings. Steinberg is installed and MAC OS brand all the file .vmx as 'Steinbergfiles '. But in fact the content of the .vmx file is my virtual machine configuration.

    Advice how to convince to use my config file and start my VM fusion are welcome. I already tried to change the type of file in this folder to a text file, but it did not help.

    Thank you

    RobiTobi

    the file extension has been hijacked by another application.  Right-click and choose open with, and then VMWare Fusion.    You can work around this problem by changing the name of the virtual machine at the end of .vmwarevm folder, and then double-click that instead of the vmx file (OSX only lets you have several apps to easily open the files automatically with the same extension)

  • Could not open the Virtual Machine: get Windows XP line 1: syntax error

    The VMware Fusion team:

    I impatiently force them to leave my MacBook Pro as my virtual machine was frozen... as a result, whenever I try and open my VM, I get this error: http://img.Skitch.com/20100316-bdpjryuqdskw8831i8j56iyqs1.jpg .

    I restart and no improvement.

    Tips, thoughts, suggestions? Thanks a lot for your help.

    I do not have the fainest idea why you're engaging again the truncated .vmx file of origin that you posted first however back a review what I said.  The line at the bottom is the .vmx file that I have attached to my last answer should be used to replace your computer in the Virtual Machine "s as package but the Virtual Machine must be stopped, not suspended and merger closed when you replace the truncated by a good I have attached.»  I can't do it, is more obvious or simple then I already have!

  • How to present a drive on a Virtual Machine of the SAN storage?

    Hi all

    My Question is that suppose we have three Machines virtual VM1 and VM2 VM3 respectively running on an ESX host. Now, we would like to introduce a SAN storage disk that is HP EVA VM02.

    How we would present disk for this particular virtual machine.

    Kind regards

    Khurram Shahzad

    A VM disk can be a vmdk file or disc RDM.

    With vmdk, you take the space of a VMFS data store, which is a logical unit number which could be simple presented to the ESX (and can be shared across ESX) and is formatted by ESX.

    With RDM you take a raw SAN disk, you must always present at ESX (as a VMFS data store), but you must add it to your VM without ESX format.

    André

Maybe you are looking for