The snapshot creates a point-in-time reference and tracks block-level changes to the files in the filesystem. The cloning uses the snapshot and the files to assemble a reasonable picture of what...
See more...
The snapshot creates a point-in-time reference and tracks block-level changes to the files in the filesystem. The cloning uses the snapshot and the files to assemble a reasonable picture of what the entire disk looked like. I imagine that if you start deleting files while the cloning is in progress, those files will not make it across in the cloning.
The Install VMware Tools option is only available for VMs being created on ESX Server. Is your new VM a standalone VM (Workstation, Server)? You will need to manually install VMware Tools and...
See more...
The Install VMware Tools option is only available for VMs being created on ESX Server. Is your new VM a standalone VM (Workstation, Server)? You will need to manually install VMware Tools and manually configure a vmxnet adapter to establish network connectivity in your NT4 guest.
Let me clarify... 1. If you have 2 volumes on the same disk on your physical machine, Converter will create the 2 volumes on a single virtual disk on the new VM by default. There is no way to...
See more...
Let me clarify... 1. If you have 2 volumes on the same disk on your physical machine, Converter will create the 2 volumes on a single virtual disk on the new VM by default. There is no way to separate the 2 volumes into 2 virtual disks. 2. If you have 2 physical disks on your physical machine, Converter will create 2 virtual disks, and you have the option to place them into separate datastores. I got confused by your use of the words LUNs and disks. Volumes are part of disks. Disks are physical or virtual. I'm assuming that virtual disks get placed into datastores in ESX Server which are VMFS LUNs.
If you use cold cloning, you can clone using disk-based cloning. It will copy the disk as-is and use block-level cloning that can be faster. Hot cloning uses volume-based cloning. If you cha...
See more...
If you use cold cloning, you can clone using disk-based cloning. It will copy the disk as-is and use block-level cloning that can be faster. Hot cloning uses volume-based cloning. If you change the sizes of the volumes, it resorts to file-based copying.
As mentioned earlier, you need not use the import function to clone and create a VM. You can continue to create VMs on your own and use your own data replication tool. Once you have populated y...
See more...
As mentioned earlier, you need not use the import function to clone and create a VM. You can continue to create VMs on your own and use your own data replication tool. Once you have populated your virtual disks, simply run Converter -> Configure instead of P2V Assistant to make the VM bootable.
Unfortunately you are correct. The only advanced option you have within Converter is to select the datastore. There isn't an option to specify the type of virtual disk created-- normal virtual ...
See more...
Unfortunately you are correct. The only advanced option you have within Converter is to select the datastore. There isn't an option to specify the type of virtual disk created-- normal virtual disk vs. Mapped SAN LUN.
VM imports have to be for VMs powered off. If it is running, you have to treat these VMs as if they were physical machines and use those options. If you are importing VMs as powered off VMs, ...
See more...
VM imports have to be for VMs powered off. If it is running, you have to treat these VMs as if they were physical machines and use those options. If you are importing VMs as powered off VMs, Converter must be running on an OS greater than or equal to the OSes you are importing. This requirement is relaxed if you are importing physical machines that are powered on.
VirtualCenter is preferred. You are correct that VirtualCenter is used to create the new VM but the actual data transfer goes directly to the ESX Server host. By interacting with VirtualCente...
See more...
VirtualCenter is preferred. You are correct that VirtualCenter is used to create the new VM but the actual data transfer goes directly to the ESX Server host. By interacting with VirtualCenter and not an ESX Server directly, you can ensure that you see all VirtualCenter-level objects not visible from a host itself.
Seems that there is something conflicting between the version number inside the file and what is listed in the registry. If you have the luxury of accessing a Windows 2000 SP4 Post Rollup VM, ...
See more...
Seems that there is something conflicting between the version number inside the file and what is listed in the registry. If you have the luxury of accessing a Windows 2000 SP4 Post Rollup VM, I would grab that scsiport.sys file inside that VM.
The only issue with co-existence is with Workstation 6 Beta. However, it would not be a best practice to install Converter on your VirtualCenter Server. Your VirtualCenter Server machine shou...
See more...
The only issue with co-existence is with Workstation 6 Beta. However, it would not be a best practice to install Converter on your VirtualCenter Server. Your VirtualCenter Server machine should be dedicated for VirtualCenter. Perhaps you can install it in any Windows VM if physical machines are hard to come by.
You could try avoiding giving them administrator privileges and restricting the network. If they have that inside the Guest then there's really no way to stop them from doing a hot clone into a ...
See more...
You could try avoiding giving them administrator privileges and restricting the network. If they have that inside the Guest then there's really no way to stop them from doing a hot clone into a new VM. It's no different than giving them access to a physical machine-- if they can image it they can run off with a VM copy using Converter.