Is it necessary that the guest OS to support SSD if the file of the virtual machine is placed on an SSD?

Similar Questions

• How to find the name of a VC that the virtual machine is on?

  have a script that allows me to search several VCs at the same time for a VM - I can go back to the host on the virtual machine is but I would rather the name of VC - how to adjust this line to achieve this?

  (get-vm-name VMname here). Home | Select name

  Thank you in advance!

  Hello

  try like this:

  (get-vm-name VMname). Host.ExtensionData.Client.ServiceUrl.Split('/') [2]

  Tim

• VMWAre HA MUST have an MS cluster so that the virtual machine have to reboot?

  This statement is correct?

  HA does not have 0 downtime. There is a period where the virtual machines will be inaccessible until the node determines she is isolated and HA procedures begin.

  The clustering of MS bit is the Microsoft implementation of virtualization also HypeV, it does not provide 100% uptime as the cluster failover event takes time to complete.

  Now, I hear with continuous availability ESX 4, we get 100% uptime on the VMS during outages of the host, but we will have to wait and see.

• Mount an .iso that is stored IN the virtual machine.

  Briefing Note: deploy us thin client on several campuses. Create us the model, deploy in each site, and then rebuild each pool. We now need to mount an image file .iso for one of the required programs. The .iso image file cannot be mounted with the software of in the virtual environment, because it uses a software of PortectDISC. We have the right number of drives, but customers have no disk drives.

  Problem: Since deploying the model, we must include the file .iso with her image. Normally, you would ride a .iso manually. However, load the file on each remote server .iso image and enter in each of hundreds of machines virtual one at a time to set the .iso way are not possible. Mount the .iso image file is our only option. Is there a way to store the .iso image file in the hard disk of the virtual machine and the virtual machine settings to rise from this point .iso? Or is it possible to include the image .iso with the model file when we deploy it is with each virtual machine and the path in the settings is already pointing to it?

  We tried to put the file .iso image on a store of data on one of our ESX servers, and then modified the model gold on this machine to point to the .iso image file. We reconstructed the pool, and the image .iso file mounted correctly. The problem with that is that we have 20 + machines trying to access the same file at the same time. Let the first few machines work, but the rest said it had disc read errors. So, we want to each machine to have its own .iso.

  Any help is greatly appreciated.

  Hello

  I have to add a warning that I use not models, but I don't think it is very relevant to my answer.

  @wila: well, I had thought about it, but when deploy us the image, it will automatically change the path to the file? For example, if we note the virtual drive to mount the .iso file to "\vm_template\cd.iso", then deploy, each of the virtual machines will not have this same path in their settings? Then they will all point to '\vm_template\cd.iso' instead of their own institution ' "\vm_##\cd.iso? '" If so, this would require we go each of hundreds of machines and set up manually every time that we deploy a model.

  If you do not add a path, then the iso that the virtual machine will try to open will be local to the virtual machine. You can simply do this by copying the vm to the path of your virtual machine, for example "[storage1] \vm_template" and affecting the CD this specific path.

  As is the same way, you can wait for the vSphere client is smart enough, it does not remove the path for drives in such a case, but not for CD...

  To use the vSphere Client to create the bases so far

  What I just did, go in the vmx file, deleted information path of superfluous and only left the name of the iso file, and all the true startConnected, not the virtual machine to make sure that my edit is OK, again registered the VM in the vSphere client, then started my VM and mounted the cdrom without any problem whatsoever.

  So - as expected - it works fine the iso file is local to the virtual machine and the local path comes first unless you assign specifically it different in the vmx file.

  --
  Wil
  _____________________________________________________
  VI Toolkit & scripts wiki at http://www.vi-toolkit.com

  Writer to the blog www.planetvm.net

  Twitter: @wilva

• usable RAM is less to installed in the Virtual Machine

  Hi Admins,

  I have a 64-bit VM win2008R2. Recently, I've increased the RAM to 64 GB to 32 GB.

  But when I look in the system 64 GB (32 GB usable) properties.

  This means that the virtual machine has only 32 GB? what needs to be done for the virtual machine to use 64 GB?

  could you please help me?

  Noufel

  You have not written what edition you have, but for example the 'standard' and 'web' editions have maximum 32 GB of RAM. In order to use more, you must have Enterprise/Datacenter/HPC edition...

• List not updated virtual machines after the migration of the virtual machine to a different data store

  My vSphere infrastructure 5 uses several data stores.

  Two data warehouses are associated with NFS on different NAS shares.

  I migrate VM to a data to another store.

  The navigation data store, I see that the files are moved from the old data store to the new and that no file belonging to the migrated VM still does exist on the old data store.

  If I look at the list of VMs on the old data store, I still see the old VM.

  I see it in the list of the virtual machine on the new data store as well.

  I checked that no .iso no pagefile is in the old data store.

  How can I update the list of the virtual machine on the old data store?

  Above all, how can I safely delete the old data store by ensuring that the virtual machine works very well on the new data store and I don't lose anything?

  Concerning

  Marius

  This use of data store 'Phantom' is usually observed, if the current configuration of the virtual computer points to the 'old' data store (diskette, CD-ROM) or the virtual machine contains snapshots where - at the time where tone have been created - the VM has had these references. Once the snapshots are deleted from data store 'ghost' will go away from summary of the virtual machine.

  André

• No network connection between the virtual machines on different hosts ESXi

  I have several 5.0 ESXi hosts in a cluster managed by vCenter Server 5 and I have network problems:

  1. [Host A] running a virtual machine can ping any other computer virtual running on the [host A] great!
  2. A virtual machine running on host [B] can ping any other virtual machine running on [B] home - very well!
  3. [host A] (from the ESXi console) can ping any virtual machine running on [B] home - even better!
  4. [B] home (from the ESXi console) can ping any virtual machine running [host A] - beautiful set!
  5. A virtual machine running [host A] can not ping any virtual computer running on host [B] and vice versa - bad, very bad!

  So basically the problem is that the virtual machines can communicate on hosts. It is a major problem that I need to fix, for obvious reasons.

  Networking on all hosts is configured exactly the same way: a unique and standard vSwitch with a pair of gigabit network cards grouped, vmkernels configured for the vMotion, NFS and network management and a group of ports configured for the VIRTUAL local area network used by the VMs. (vMotion works fine on hosts, storage vMotion works very well too.) All virtual machines are servers Windows (2003 and 2008).

  Reason #3 and #4 above, my assumption is that #5 must be the result of an ESXi/vCenter configuration issue and not a problem with the switches of material upstream. Is this a reasonable assumption?

  Whatever it is, can anyone offer suggestions on how can I fix? It is quite annoying as I'm pretty sure that these hosts are configured in the same manner as those of our production cluster, which does not at all these problems!

  Thanks in advance for any help you guys can provide.

  To be honest, it looks like a problem with your physical network-

  How is the physical network configured - are NIC connects it to the same physical switches? Are the virtual machines on the same subnet? If this is not the case, they are able to ping the gateway sbnet? Can you piing host IP address from the virtual machines?

  I also moved it to a forum more approiate.

• Method to move the virtual machines in the data store temporary so I can rebuild pool recommended NFS

  Our current data store is a mounting NFS on Nexenta (zfs), which has a pool, I need to rebuild (migration of raidz2 to mirror striped for performance). Initially, I was relying on the judgment of all virtual machines, create a new pool, copy (cp - r) of the Nexenta console all virtual machines to the new pool, recreating the pool mirror and then copy (cp - r) all the data back.

  I have seen several discussions on this topic and seems like the simplest method would be to use the feature to "Migrate" so that the virtual machines are not fragmented. However in some of my pre-test when I copy a virtual machine between the basins of the Nexenta console it appears (from the data store Explorer) to initially create the vmdk provisioned and then once completed it copy looks too thin.

  I hope that I can simply copy the Nexenta console, using the option "Migrate" in vCenter on each of my 40 MV looks like it would be * quite * tedious compared to the simple issuance of an order of 'cp - r' and leave all the copies of VMs (1.5 to) during the night and then adding them to each host.

  Does anyone have experience with this? Or maybe a way to generate scripts easily (?) the option "migrate" in vCenter?

  Thank you all!

  You can select multiple VMs in vCenter regularly using CTRL + click or shift + click and both migrate them as long as they have the same storage destination.  You can also schedule it as a task.    Add manually each computer virtual back in hand is not less painful than migrating individually, anyway.

• 'Create a snapshot of the Virtual Machine' suspended the process - how to kill?

  I tried to rename a virtual machine when I received a message from VCenter that "another task is already underway."

  I did some research and found that the virtual machine, I am trying to rename is currently creating a snapshot of the Virtual Machine.  Or - at least the host thinks Yes.

  The snap was initiated by vpxuser about 20:00 in the night a few days - and is still ongoing.  I can't kill him since the VIC when it is directly attached to the host.

  Looking to my data warehouses - I don't see that he actually created the snap, because I see no 0000001 or something like that.   At this point, I don't like, I don't know why he even launched the snap in the first place.

  Is there a way I can kill that process with the help of the console?   It's hosted on vSphere 4.

  Sven

  You have restarted these services on the host computer?

  service mgmt-vmware restart

  restarting the service vmware-vxpa

  • Kyle

• Open with: 'Application name' - 'Name of the Virtual Machine' (2.0.4) AND (2.0.5)

  Hello

  Looking for help here...

  I notice that if I try to open a file on my Mac with an application of my virtual machine (Win XP Professional) I get 2 options for each windows application:

  1. Windows Media Player - Windows XP Professional (2.0.4)

  2. Windows Media Player - Windows XP Professional (2.0.5)

  The 2.0.4 option never works but the 2.0.5 option. I know this has something to do with the upgrade to the latest 2.0.5 version, but how do you / is it possible to remove the non-fonctionnel 2.0.4 options?

  Help, please! It's pretty boring.

  I have only haveone of virtual machine set up.

  Rich

  Make sure that the virtual machine is turned off and not suspended.  First locate the virtual machine in the finder.  You can do it by Ctrlclicking on it from the library of the virtual machine and choose Show in Finder.  In Finder Ctrlthe .vmwarevm of the virtual machine and choose "show package content".  If some shows as a folder go there.  Of in the virtual machine folder, you will see a folder named Applications.  Applications are the links to the Applications that you open in the virtual machine.  Remove vouchers there should do.  You may be able to determine the good by the update and the last number should be also the most recent.  These changes to take effect, you will need to reboot or restart the finder.  To restart the finder press and hold Esc, command,Option, and choose finder in there and restart.

  You can also just delete the Applications folder and then start the virtual machine.  Once that the virtual machine is started just enter the unit.  Entering the unit will recreate this Applications folder with the correct files in there.  You should always restart or restart the finder once this is done before it takes effect in the mac operating system.

• 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

• Where the virtual machine is stored on a Mac

  I know that the virtual machine is stored on the hard drive by default but I have additional disks internal and external drives connected and I prefer to put the VM on one of them so that I can give him a decent amount of space.  Is this possible and if so, how?

  Thank you

  David

  As you walk through the Wizard New VM, you can choose to save it where you want.

• Host detects the virus that is ran in the virtual machine

  When I google search for "virus to test download" and open the 2nd link in my windows 7 VM, avast on my host computer is like VIRUS DETECTED. I'm guessing that this occurs because the virtual computer uses the internet hosts.

  PS: it was once my I.T. teacher told me that he was sure navigation in a virtual machine.

  Host antivirus can detect the test virus in the network traffic and also could detect when the VM saves on hard drive of the virtual machine (which, after all, is stored just as a set of files on the hard drive of the host).  Some antivirus programs scan even the memory used by all processes running, in which case it can also discover that the test virus from the data in the memory of the virtualization engine.  None of these situations are a source of real concern for the host.

  Navigation in a virtual machine is generally considered safe from the point of view of the host, but virtualization will do nothing to directly protect the OS itself invited to malware that it can capture.

  Note that VMware Workstation has a few features that deliberately to break the isolation barrier and could expose the host to a malicious client.  If you are worried about it, a good starting point to lock the virtual computer is to go in the settings of the virtual machine, choose the Options tab, make sure the shared folders is disabled (under Guest insulation), make sure that the Clipboard and features drag-and - drop are disabled.

  See you soon,.

  --

  Darius

• Disks of the virtual machine consolidation is necessary - vCenter 5.1 U1 + ESXi 5.1 + VDP 5.8.0

  Hello

  I am facing problem as many other people do, when snapshot is deleted, the delta files are still there and warning message "consolidation of disks of virtual machines is necessary" is shown on the virtual machine.

  It happened only few but try to find the root cause. He arrived only on virtual machine located on ESXi 5.1 build 799733 which is located in the task of the WTP 5.8.0 backup.

  Is this snapshot problem, a bug in the version of ESXi?

  Unable to find the release notes, where this is documented as bug.

  Thank you

  Finally, I found a reason, therefore, for other users... ESXi 5.1 build 799733 has a bug that is resolved in the update 1 and higher and is connected to the suspended snapshots created by POS, that is why are there so many discs of delta.

  ESXi 5.1 Update 1 Release Notes

  • When the slowdown of snapshot fails the redo logs are not consolidated
    • When you try to take a snapshot of the suspension of a virtual machine, if the snapshot operation fails near the end of its realization, recovery logs created as part of the snapshot are not consolidated. Recovery logs can consume a lot of space to store data.
    • This issue is fixed in this version. If the snapshot suspended operation fails, the redo log files are consolidated.

• Help. The CPU has been disabled by the guest operating system. Power off or reset the virtual machine. WHY?

  Greetings.

  I have a 5.5 with an operating system Red Hat 5.10 ESXi environment. The OS worked fine until a few days ago. ESXi displays the error "the CPU has been disabled by the guest operating system. Power off or reset the virtual machine. I Don t know why my server displays the error if my environment was OK. Could be a kernel problem? operating system problem?

  Ideas?

  Thanks for the help.

  Have a look here. http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2000542

  Did you recently patch your VM? Looks like when the guest operating system runs the incorrect commands that it can have a deactivated processor.