Cannot start the virtual machine in a HA cluster

Similar Questions

• Cannot start the virtual machine after you create snapshop

  I found a strange behaviour. I have a Windows 2008 guest that I just copied in my new box ESXi. I am trying to create a snapshot before upgrading the guest to 2012 Windows operating system. The virtual machine has currently no snapshots. Whenever I have create a snapshot, he succeeds, but then I can't start the virtual machine saying that it does not find the vmdk file delta even though I see there in the data store. In order to start the virtual machine, I have to delete the inventory and it readd, but then I lose the snapshot. I also have another computer virtual running Windows 8.1 that does exactly the same thing. How can I create snapshots safely without damaging the virtual machine? I also tried to create the snapshot while the virtual machine has been activated but that makes crashing and then it does not start again, so I have to repeat the process to remove the inventory and it time. Frustrating. See the screenshots, I have attached.

  Once these virtual machines have been in Hyper-V in the past and I just convert to VMware format using the StarWind V2V converter.

  Yes, for an ESXi host and target you must either select the ESX f.vmdk as format target (growable option is for VMware Workstation), or you must convert the virtual machine once more instead of simply upload the files to an ESXi host.

  André

• Cannot start the virtual machine guest after receiving "License expired message" host ESXi 5.5

  I can't start computer virtual invited after receiving "License expired message" 5.5 ESXi host. I am able to copy the vm folder prompted with all its files using WinSCP I had already installed on a desktop computer in the network.

  However, it takes an extremely long time to download the VM [2.5 mb/s], which is of course a different question.

  It seems that I was still on the trial with my vsphere client license, until it expired. I am able to view the virtual machine within the workstation 10, but I can't turn it on. It says "Please install a license to power on this computer" there is no way to install a license anywhere.

  My question is... .will I be able to access this virtual machine if I download on an external hard drive, then add it to 10 VMWorkstation that I possess a current valid license?

  Even if the evaluation license has expired, you should be able to connect to the ESXi host using the vSphere Client and follow the steps mentioned in the article that I posted before you enter the free license key.

  André

• Cannot start the virtual machine on VMware Workstation 12.1.0

  The host machine is W2008R2, VM is the same. When im trying to start the current VM I see VMware screen, then "download files" screen loading, then VMware loading new screen and etc.

  Log file is attached below.

  An update of the firmware could certainly help.  After you install the update of the firmware, it can be useful following the instructions from the motherboard to reset the firmware configuration by default (if its configuration is not too heavily customized) and then reconfigure with custom settings, you might need.  Check that you have disabled in your TXT firmware settings too... who's going to stop us from using the capabilities of VT - x from the host.  And, where there is doubt, the error message is not really pleasant on cyclical food... Some systems cannot put a change of configuration of VT - x into force without being truly disconnected from power for a while, so if in case of doubt, he put it off and remove the power outlet for a few seconds.

  Your CPU is certainly capable of VT - x and support all the VT - x features required by VMware Workstation... Simply to force the system to allowing the use of VT - x and then it should start to work well.

  See you soon,.

  --

  Darius

• VMWarer Image cannot start the Virtual Machine in Windows 7

  Hello

  Receive a machine with disc encryption HARD full of checkpoint on it. I had successfully converted to a virtual machine Image, unfortunately every time tried to start gives me BSOD.

  Tried to fix it, tried to return to the image, but the same results.

  There were no errors during the conversion. complete cleaning.

  Someone at - it suggestions?

  How did you convert the image in a virtual machine?
  have you changed the type of Adapter LSI - SAS during conversion?

• ZPrint accident of process before starting the virtual machine

  I see the following messages in system.log everytime my Windows VM starts. These accidents zprint apparently never happened before today. There is no previous accident for zprint report. The messages below always repeat 3 times before other messages on VM, commissioning.

  09/02/15 21:20:33... Report of incidents ReportCrash [7538] advice for zprint processes [7537]

  09/02/15 21:20:33... ReportCrash [7538] error saved crashreport to /Library/Logs/CrashReporter/zprint_2015-02-09-212033_...crash using uid: gid 0: 0, euid: egid 0: 0

  Extract from the report of crash:

  Exception type: EXC_ARITHMETIC (SIGFPE)

  Exception codes: EXC_I386_DIV (division by zero)

  Why the merger issues the command zprint? If she has always done so before, why is zprint now blocking?

  (If I run the terminal zprint command without specifying the name of the area it blocks the same way.)

  Anyone have any ideas?

  Some things that I did today that might be important:

  My Mac Pro locked up while I was running Firefox (open Youtube and Yahoo pages).  I pushed the power button / stop. The virtual Windows machine was running at the time.

  After restarting the Mac Pro, when I tried to start the virtual machine, I got the message: "... vmdk has one or more internal errors that cannot be repaired. The only option is to restore from a backup copy of this disk... »

  So I renamed the corrupt VM bundle, then drag-and - drop copied all of the virtual machine to a backup volume.

  When I started the virtual machine restored, I noticed the crash zprint above messages.

  Thank you!

  OS X 10.5.8, Fusion 3.1.4

  Fusion uses zprint to internal information of the kernel which are very difficult to obtain by other means.

  Given how long it has been since OS X 10.5.8 or Fusion 3.1.4 were changed, either something has been corrupted or something has changed in the system environment for that to happen early.  I can't find any other references to zprint triggering a SIGFPE anywhere else on the Internet...

  If you do not already done, I highly recommend running disk utility and check (and possibly repair) the disks of your host before doing anything else.

  See you soon,.

  --

  Darius

• [Q] cannot start a virtual machine - internal error [SOLVED]

  Hallo,

  I installed Workstation 8 and cannot start a virtual machine - or those created those previous or new. Turn the machine gives me an "internal error."

  My characteristics: Win 7 64-bit (SP1), Core i7 2600 K with 8 GB of Ram

  The newspaper of vmware:

  011 10 - 03 T 19: 22:38.013 + 02:00 | VMX | I120: Log for VMware Workstation pid = 3424 version 8.0.0 = Build = build-471780 option = output
  2011-10 - 03T 19: 22:38.013 + 02:00 | VMX | I120: The process is 64-bit.
  2011-10 - 03T 19: 22:38.013 + 02:00 | VMX | I120: Host = encoding windows-1252 = windows-1252 codepage
  2011-10 - 03T 19: 22:38.013 + 02:00 | VMX | I120: Host is Windows 7 Home Premium, 64-bit Service Pack 1 (Build 7601)
  2011-10 - 03T 19: 22:37.713 + 02:00 | VMX | I120: VTHREAD initialize main thread id 0 "vmx" host 6336
  2011-10 - 03T 19: 22:37.738 + 02:00 | VMX | I120: Settings REGIONAL windows-1252-> user NULL = System = c07 c07
  2011-10 - 03T 19: 22:37.738 + 02:00 | VMX | I120: Msg_SetLocaleEx: HostLocale = windows-1252 UserLocale = NULL
  2011-10 - 03T 19: 22:37.743 + 02:00 | VMX | I120: FILE: FileLockDynaLink: other process validation tools are: available
  2011-10 - 03T 19: 22:38.014 + 02:00 | VMX | I120: Hostname = KOENIG
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = d fe80::41: e6a3:5dd2:fa9f % 11
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = fe80::1cf:3682:36e8:4ccb % 17
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = fe80::1 d 80: 2f6e:979 c: b57d 18%
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP 192.168.1.4 =
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = 192.168.30.1
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = 192.168.158.1
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: HOSTINFO 1074415970 @ 3331240Hz-> 0 Hz 1000000000
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: HOSTINFO ((x * 2518163806) > > 23) + 322527338056
  2011-10 - 03T 19: 22:38.037 + 02:00 | VMX | I120: System uptime 321912074 us
  2011-10 - 03T 19: 22:38.037 + 02:00 | VMX | I120: command line: "C:\Program Files (x 86) \VMware\VMware" "-s" 'vmx.stdio.keep = TRUE' "-#" "product = 1; name = VMware Workstation; version 8.0.0 =; BuildNumber = 471780; licensename = VMware Workstation; licenseversion = + 8.0; ""-@ ""pipe=\\.\pipe\vmxf3ce37cf9b6f9c3e;" "D:\VM\Windows 7 x64\Windows 7 x64.vmx".
  2011-10 - 03T 19: 22:38.037 + 02:00 | VMX | I120: Msg_SetLocaleEx: HostLocale = windows-1252 UserLocale = NULL
  2011-10 - 03T 19: 22:38.056 + 02:00 | VMX | "I120: UI connection on pipes '\\.\pipe\vmxf3ce37cf9b6f9c3e' user (null)".
  2011-10 - 03T 19: 22:38.057 + 02:00 | VMX | I120: VMXVmdb: local connection timeout: 60000 ms.
  2011-10 - 03T 19: 22:38.104 + 02:00 | VMX | I120: VmdbAddConnection: cnxPath = / db/connection / #1 /, cnxIx = 1
  2011-10 - 03T 19: 22:38.105 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:483]: VMAutomation: initialize VMAutomation.
  2011-10 - 03T 19: 22:38.105 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:780]: VMAutomationOpenListenerSocket() to listen
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Past vmx/execState/val of poweredOff
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 2, newAppState = 1877, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 3, newAppState = 1881, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: VMMon_GetkHzEstimate: calculated 3411189 kHz
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: VMMon_RememberkHzEstimate: calculated 3411189 kHz
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: TSC kHz estimates: Memoirs of vmmon 3411189, 3411189, osReported 3401000. With the help of 3411189 kHz.
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU 0 # TSC = 1100186590922
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 1 TSC = 1100186590888
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: # 2 CPU TSC = 1100186590603
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 3 TSC = 1100186590637
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 4 TSC = 1100186590948
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # TSC 5 = 1100186590906
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 6 TSC = 1100186590898
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 7 TSC = 1100186590836
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: TSC of measured first delta 345
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: TSC 387 min Delta
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: PTSC: RefClockToPTSC 0 3331240 Hz-> 0 to 3411189000 Hz
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: PTSC: RefClockToPTSC ((x * 4294966339) > > 22) +-1100565306901
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: tscOffset-1100187618517
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: using TSC
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: material TSCs are synchronized.
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: PTSC current = 289960
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: Module CPUID initialization failed.
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:869]: VMAutomation_LateShutdown()
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:819]: VMAutomationCloseListenerSocket. Close the socket of the receiver.
  2011-10 - 03T 19: 22:38.125 + 02:00 | VMX | I120: VMX VMDB Flushing connections
  2011-10 - 03T 19: 22:38.125 + 02:00 | VMX | "I120: VmdbDbRemoveCnx: remove Cnx Db for ' / db/connection / #1 /"
  2011-10 - 03T 19: 22:38.125 + 02:00 | VMX | I120: VmdbCnxDisconnect: Disconnect: pipe closed for pub cnx ' / db/connection / #1 /' (0)
  2011-10 - 03T 19: 22:38.129 + 02:00 | VMX | W110: Failed to initialize the virtual machine.

  I scored an error... I tried to reinstall, clean... nothing helps.

  Curiously, I can use the Player app to run all VM´s without problem...

  All solutions?

  Thanks in advance

  Marcus4Aspern

  Is - the name change "vmware.exe" with something else?

• Unable to start the virtual machine after Migration - ESXi hosts

  Last night I wanted to move a virtual machine to a host of test to a production cluster.  All hosts (test and production) have shared access to the same LUN, so I usually am able to simply remove the virtual machines of the inventory in the test environment and add them to the production environment by accessing the .vmx on the data store file.  Two of the 3 hosts migrate perfectly and are running in the production environment.  However, the third server, while the migration starts.

  First he gave me errors that it was missing some files.  The only thing I did was different to rename the folder for the virtual machine on the data store.  It was called 'New Virtual Machine' for a reason, so I renamed it to "Antivirus."  However, something strange happened.  Instead of renaming the folder, it seems was created a new folder named "Antivirus" and the old folder 'New Virtual Machine' was still there.  In addition, the renamed folder 'Antivirus' had only SOME of the files needed.  So I just copied from the old folder in the folder "Antivirus" and he hung up the virtual disk of 20 GB file.  So I closed the VI client and checked the vdmk 20 GB folder and back this morning is in the folder with other files.  However, when I try to start the virtual machine, I get the "cannot access a file because it is locked" error message.

  I've done some detective and I noticed that in my second datastore where was the other folder vdmk, the file was now .40kB in size.  Looks like I've lost my other vdmk folder.  What happens here?

  It looks that the virtual machine was still running when you tried to change the name, so the old folder could not be renamed because of the lock. That's why a new folder has been created instead, and why your vm hung on the vmdk file until the lock has been released. Don't know what happened to the 2nd vmdk file, but the file vmware.log in virtual machine directory must have some info as to why does not start the virtual machine. If the 2nd vmdk is gone, this might be a reason.

  -KjB

  VMware vExpert

  Post edited by: kjb007: changed vm in vmdk

• Unable to start the virtual machine after restoration

  Guests including Test host: ESXi 5.1.0.1065491

  Vm problem: 32-bit, Server 2003

  I use Veeam Backup & Restore 6.5 to back up my vm.  I always do a test restore to ensure that my backups are good.  I'm having a problem with a restore.  The 32-bit Server 2003 vm starts just fine on the main host it runs on.  All the vm are 64-bit except for one who is a 32-bit Server 2003 vm.  Restoring the machine virtual and implemented on a host except the 32-Bit vm Server 2003 test.  After restoration and trying power to the top, I get the following error:

  Unable to start the virtual machine.

  Turn on VPCM module has failed.

  Viewed performance counters require version 3 or greater of architectural performance monitoring.

  Anyone know if there is a fix for this problem?

  TIA,

  Mux

  I assume you are using different hardware (CPUs, the BIOS settings) for VMS restored!

  The virtual machine has VPCM enabled, which causes the problem. You can either disable it in vSphere Web Client (you can do this in the vSphere Client Windows), or directly modify the .vmx VM by setting vpmc.enable to "FALSE".

  For how toggle this setting in the Web Client see allow virtual in the Web Client vSphere CPU Performance counters. If you want to edit the .vmx file manually, you need to delete/re-add the VM from the inventory or recharge (see http://kb.vmware.com/kb/1026043)

  André

• Trouble entering the Configuration Page of the BIOS to start the virtual machine by key pressing (F2).

  To start the virtual machine guest OS (Win XP), I want to enter BIOS, by key configuration page by pressing "F2", to change the order of boot options.

  But the initial startup if page flashes quickly, so that I don't get time to press 'F2', most of the time.

  The problem is exasperated because my press F2 is not taken initially without first mouse clicking, somehere in the start page.

  So the order of actions is

  b click the mouse on the settings window, so as he prepares to receive the keystrokes.

  (b) and press 'F2 '.

  Before these two actions are completed, pages flashes by so quickly.

  Anyone can suggest a quick and easy solution for this?

  concerning

  Note: don't know if it is the appropriate forum category.

  + I also not my button "Start a new Discussion" in the General category page? +

  Hello.

  You can manually edit the. VMX file to the virtual machine and add the following line:

  bios.bootDelay = "5000".

  for a period of 5 seconds.

  Good luck!

• IP not set to start the virtual machine

  Environment: ESX 4 server, hosting VMware Studio 2.0 (final version), will deploy device created in the same ESX host.

  -

  ---

  I was not yet able to determine if my wait will not, but I expected that my VM would be marketing it would have an assigned IP address already if I finish the network settings section in the build settings. But when I start my VM, it starts with IP = 0.0.0.0.

  I'm going to network Type = static and by filling in all the details for the IP, mask subnet, gateway, DNS 1 and 2. It seems that they are used when the virtual machine is in 'construction' on the host, but I'm not entirely sure about this.

  In the OVF IP assignment settings, I tried selecting OVF environment, but have not set of OVF properties (I don't think that this should be mandatory if I am already addressing in the build settings).

  After construction, into my vSphere Client (ESX4), I chose the file & gt; Deploy the template OVF... & gt; Deploy from URL and paste the URL of the virtual machine built recently. I start the virtual machine and watch the console screen boot and load the operating system. IP address is never assigned and the console device is displayed with IP = 0.0.0.0.

  I then have to connect with the image, manually assign the IP settings and then everything works. I expect this happen at boot time so that my firstbootscript can take advantage of the assigned IP address.

  -

  ---

  Maybe I go about it the wrong way, but my usecase is as follows:

  Build a VM & gt; Distribute the VM on end user & gt;  end user deploys on ESX and chooses address IP & gt; end user boots VM for the first time & gt; firstbootscript runs automatically

  Am I missing something? Can I have different expectations about how IP assignment is supposed to work? I read about IP Pools, but this isn't an option in my vSphere Client.

  Property of the FVO is the best option to set an IP address.

  Long back for Linux OS, I have written a shell script to set the IP address and the hostname in firstboot Virginia you can try this for your going here is the link for the same thing.

  http://communities.VMware.com/docs/doc-10953

  In the OS from VMware Studio tab you can paste this script in the script firstboot.

  First of all, please run this script manually and then use it in VMware Studio firstboot.

• Cannot start multiple virtual machines.  Maybe I corrupted the model

  We had problems with disk space, and I was looking around to see if he had left garbage data store.  I am very new to VM, but even though I'm new I'm responsible for helping maintain.  So I learn a lesson the hard way.

  I found a number of virtual machines in organized which did not seem to relate to existing models.  For example, we have a model name 000729-Server2008 Server 2008, that they are in lm401\729.  But it appers to be a clone of 729 to lm401\16.  I'm going to guess that 16 was the original version and changes or clones have been made for him and we are now sitting to 729.

  Then I moved 16 in another data store, but it failed because there is a lock on the hard master.  So I moved everything back.  Now, when we try to start up of VMs driven from this model we get "file & lt; filename not specified & gt; not found"I went back and tried to deploy and supply on the model but I get

  Impossible to deploy virtual machines in the pool of resources 'resgroup-131.

  • Not to feed one or more virtual machines.

  • Error when powering on a virtual machine '2008 X 86'.

  • Cannot power on the operation on a virtual machine
    carried out because one of the files is locked. Consolidation of the
    virtual machine can solve this problem.

  • The operation cannot be performed because a file is locked.

  So I cancelled and tried to consolidate while I get

  Host '172.31.7.111' reported an error. A disk error has occurred: the parent of this virtual disk could not be opened. Host '172.31.7.111' reported an error. A disk error has occurred: the parent of this virtual disk could not be opened.

  Can someone help me?

  This article may help: http://www.vmware.com/kb/1007969

  If you have found this helpful at all prices please points using the correct or useful!  Thank you!

• Cannot start the physical machine converted to a virtual machine under ESXi 4.0

  Hi all

  I have 2 has with the material below

  Dell optiplex 755 2.4 Qcore 4 GB of RAM and 160 GB of HARD drive

  A performer with ESXi 4.0 other runs with Windows 2003.

  I tried to convert physical machine with "Vmware Vcenter converter Stand alone" 4.0.1 build 161434

  I used the tool on the source machine and by another machine on the network.

  The two process converts the physical machine to a virtual machine successfully without any errors.

  After conversion, the virtual machine cannot start, and shows only a small slider that is not flashing too.

  

  The physical machine have a single partition of 160 GB

  The space currently used on the physical machine is 26 GB.

  I reduced the size of the HARD drive to virtual computer with fix / light available in 40 GB.

  point to make here is that the ESX have only 160 GB HDD, so he will not be able to copy all 160 GB because of which I am reducing the 40 GB HARD drive

  I converted a few other physical machines with 40 GB HARD drive and they work well after the conversion.

  Any sugessions would be greatly appreciated.

  Thanks in advance

  Hi Sunil,

  Let me know the drive selected in the custom option controller.

  Thank you

  Krishna

• Unable to start the virtual machine

  Recently had to reboot my computer because windows updates and accidentally shut down the system while the virtual machine is running.

  After the reboot, I noticed the server was not running and cannot be started with the above error.  His runs on 10.1 workstation and I'll show you the log file.  Also deleted the .lck files but still no luck.

  Restart all of the services, they seem to stop and start cutting.

  Please help thanks!

  2015 05-17 T 10: 31:14.613 - 04:00 | VMX | I120: [msg.vmx.nestedHyperV] VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V system role before running VMware Workstation.

  It seems that the system started with Hyper-V active. You have another option of disabled starting with Hyper-V?

  André

• Failed to create snapshot - now I can not start the virtual machine.

  Hi guys,.

  I took a snapshot of my VM and got the error:

  Cannot open disk ' / vmfs/volumes/xxxxxxxx.vmdk' or one of the snapshot disks it depends on.

  Reason: Invalid drive string: cannot mix ESX and hosted style discs in the same chain.

  I deleted the snapshot in the Snapshot Manager, but my VM will always start (same error)

  Can anyone help? Its a vanilla install, just 1 VM on it.

  Thanks in advance

  Always pointing the Flash disk VMX configuration file. Whenever you remove the Flash disk, the drive-VMX configuraiton must be updated correctly. In your case it does not somehow. Anyway, lets get a work around.

  1 take the backup of the VMX configuration file

  2. edit the VMX file

  3 scsi0:0.fileName = "QFES_1.2.25 - RHEL52_x86.vmdk" (Please check the VMDK file name correctly it)

  4. save the file

  5. turn on the virtual machine

  Check your luck now