Scribd
Upload
467 views2 pages

My Vmware Notes

The document provides prerequisites and requirements for various VMware virtualization migration tasks: 1) VMotion requires vmkernel networking, shared storage, licensing, and VMs configured for migration with NICs of at least 1GB. If using RDM, the destination server needs access to storage. 2) V2V migration involves moving VMs from one hypervisor to another, such as from VMware Workstation to ESXi, to change platforms. 3) For P2V and V2V, determine if migration should be hot or cold based on applications. Separate VMs may be needed for Active Directory. Physical hardware devices must have virtual equivalents available. Check storage, memory, and

Uploaded by

nilesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
467 views2 pages

My Vmware Notes

The document provides prerequisites and requirements for various VMware virtualization migration tasks: 1) VMotion requires vmkernel networking, shared storage, licensing, and VMs configured for migration with NICs of at least 1GB. If using RDM, the destination server needs access to storage. 2) V2V migration involves moving VMs from one hypervisor to another, such as from VMware Workstation to ESXi, to change platforms. 3) For P2V and V2V, determine if migration should be hot or cold based on applications. Separate VMs may be needed for Active Directory. Physical hardware devices must have virtual equivalents available. Check storage, memory, and

Uploaded by

nilesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

prereq for vmotion

-->
vmkernal network configured
shared storage
license
vm should be configure for vmotion
nic should be min 1 GB
if RDM , des server shoukd have acces to that
processor compatiblity
##################################
why to do v2v migration
-->we d v2v migration when we are migrating vm from 1 hyper to other
for examp;le migrating vm fromvmware workstation to vmware esx/esxi
########################################
prereq of p2v and v2v
-->
Decide on Hot OR cold.. If its AD, Mail or database server go for cold
For ad its recomended to create sep vm and promote it as a Dc and then deolish o
ld AD
If server is having serial port , still p2v is possible but vm will reside on es
x having serial port
If server havinf parralel device attached , thev converted Vm will reside on esx
server havinf parallel device attached to it
if physical server using usb device then u have to use usb anywgere which will a
llow usb to work up on network
check if enough of disk space is there for vm
check if enough of memory is there
check if enough of cpu is free for vm
Check the network to which phy macine is connected , it should be accessable to
virtual network
#################################################
why disk increase option is grayed out for my vm in esxi
->need to delete snapshot , as we can not increase disk size if the snapshot is
present
you night not be a admin user , so permision issue could be the issue
It might be disk drive used are different , try with v2v and it will solve the i
ssue , while converting
you need to select proper bus logic
still issue persisi , create one snapshot and then delete it and try
still not , reboot the vm

######################################################
All options are grayed out for Vm.
-->
*Permission issue
*task ruuning in baground for same vm , check using
to list all vm -- "vim-cmd vmsvc/getallvms"
to list runing service *vim-cmd vmsvc/get.tasklist vmid*
Now you you have a choice to either wait for the jobs to complete, or restart th
e Management agent to terminate this job
*invalid entry in vmx
Open the .vmx file using any text editor.
Search for any blank lines and delete them.
Note: To delete a single line using vi editor, press d twice.
Compare the .vmx file with a working virtual machine .vmx file and see if there
are any invalid arguments.
To apply the changes, reload the .vmx file by running the command:
"vim-cmd vmsvc/reload vmid"

You might also like