Hi,
Thanks for reply.
I connect to every VM throught RDP but it's strange this "problem", because I see de cursor but can't click.
Anyway, that's not a problem for me because I only use vSphere to see and controll the system and to connect them I use RDP, but it's a problem to VMware Developers solve later.
But yes, It's a little bit annoying because after install I cant configure with mouse, even to configure the IP's for RDP connection 
Best regards,
José Simões
Hi everybody,
I'm currently VCAP5-DCD and VCAP5-DCA and I'm looking for become a VCDX5-DCV. I head about this course, but could not find information either.
If someone has any information about it, please let me know.
Thank you very much!
Dear Guys
Im new to SRM. i want to install SRM 5.8 in a test environment. i have 2 ESXi server for testing SRM.
The srm 5.8 installation guide didnt explicitly mentioned about the above questions of me.
We are moving from VSphere 4.1 to 5.5. We are very small with only 3 hosts running about 20 guest VM's on a SAN. Our old VCenter VM is still on Win 2003 and I am changing this as well.
So rather than doing an upgrade from 4.1 to 5.5 and converting the older vcenter 4.1, we decided to just complete a brand new installation of VSphere 5.5 to a new server we have. We also installed a brand new Vcenter 5.5 Appliance as well. So essentially we have two different installs of Vcenter, old and new running. Then we plan to manually move the existing esxi 4.1 hosts into the new Vcenter appliance. Then eventually move over the guests from an existing host to the new box and then wipe and reload each older host with 5.5
So I have already completed the first half of this project. But I have a question.
During the changeover from Windows VCenter 4.1 to the new esx host and VCenter appliance 5.5. I will be running both VCenter's (ver 4.1 and ver 5.5) simultaneously for a short period of a few days. One still running on the older 4.1 host and the new vcenter 5.5 running on the brand new esx 5.5 host.
We will walk one host at a time from the old VCenter and it will be added to the new Vcenter 5.5 appliance. But I will be sharing my only SAN of course. If I am doing this and running both versions of VCenter (old and new) at the same time and sharing my same SAN datastores at the same time, is there any problems with doing this? I didn't think so but I am not sure.
I installed the first new esxi host and I have pointed to my SAN datastores with no problems. And the datastores appeared as they should. But when I add this new host to the new VCenter, as part of the setup process it displays all the relevant San datastores. I thought this was odd to show during the VCenter “Add a host” step. Are there any restrictions to running two different VCenter VERSIONS at the same time on the same datastores ?
Thank you.
HMorris
my VMware Certified Professional 5 - Data Center Virtualization will expire in march.
Is it enough if I take the VCP-Desktop Exam (VCPD510) exam?
Hello Team,
You can ... Here is what you need to do. I assume you want to use vSphere Replication 5.8, since if you use SRM 5.8, you need to have storage array base replication.
Get two vCenter server , add one ESXi host to each vCenter server, then deploy the vSphere Replication appliance on each of the ESXi host.
Here is link which shows how to deploy and configure vSphere Replication, VR ( vSphere replication work with local datastore with out shared datastore )
VMware vSphere Replication 5.X Basic Deployment and Configuration | vDiscussion
vCenter server does not need to be in linked mode.
Regards
Mohammed Emaad
Hi Darius
You are a star!
Just for the record and maybe help for others:-
I own a mid-2011 iMac (i7)
I upgraded to Fusion 6.0.5 last week. I also upgraded to Yosemite on 25 Oct.
My Win2012 Guest was performing fine since I upgraded to Yosemite.
I had to completely shutdown my iMac two days ago. When I started the guest it took 30 minutes to become usable but was very slow.
Even tried installing a fresh Win2012 guest but even that would not start up.
I completely uninstalled Fusion 6.0.5 and brought in my backup of the guest prior to upgrading to Yosemite. Still no joy. What on earth was going on?
I then upgraded to a trial Fusion 7.0.1 thinking that it would fix any issues. The guest was still slow!!
Saw your tip, applied it and bingo... back to full speed.
What a hellish few days of trying to work out if I had changed something or corrupted some config.
Many many thanks
Thank you Jim, but all thanks must go to Mark who gave the right idea about incorrect height of an element. =)
Hello Lucd
Thanks For response, Please find script, let me know what changes went wrong ;-)
Hi ahaines69,
The work-around you introduced in this post worked for my environment, CentOS 6.6.
Thanks!
Regards,
Ta-chang
I understand this is 6 years old, and I was unable to find an answer for RDM using any language/API - and came across this post.
I figured it out, so thought I'd post here in case anyone else has the same issue.
There are two strands to achieving this.
1) Create the VirtualDisk VMDK file with backing for the RDM mapping
2) Attach the VirtualDisk to the VM
I'm using pyVmomi, so the breakdown in these strands are:
Preparation) Collect the data you will need.
a) Using your scsiLun object, retrieve the scsiLun.capacity.block and scsiLun.capacity.blockSize attributes.
calculte the capacityInKB value with scsiLun.capacity.block * scsiLun.capacity.blockSize / 1024
b) You need to find the controllerKey from the VirtualMachine object.
Iterate virtualMachine.config.hardware.device looking for each device being an instance of:
vim.vm.device.ParaVirtualSCSIController
vim.vm.device.VirtualLsiLogicController
vim.vm.device.VirtualLsiLogicSASController
vim.vm.device.VirtualBusLogicController
You need to store these somewhere - these are your scsi controller devices in the VM, they will have a .key value that you need.
Next (or at the same time as above - I separated them out) you need to iterate virtualMachine.config.hardware.device looking for
vim.vm.device.VirtualDisk instances
Each of these devices will have two attributes .controllerKey and .unitNumber
The controllerKey will correspond to the .key values discovered when looking for the scsiControllers. This tells you which controller "connects" this VirtualDisk.
The unitNumber is the controller scsiid - every disk needs a unique number between 0-15 (but don't use 7 as that is for the controller itself).
Using the above information you can calculate the controllerKey and unitNumber value for your new disk. My method is to walk the controllers, and walk each disk on that specific controller. I remove the unitNumber from a prepopulated array/list of 0..6,8..15. If by the end of the walk, the array size is > 0 then I choose that controllerKey and the first element in the list (will be the first unused unitNumber).
c) Find the Datacenter used by your VirtualMachine (needed for the CreateVirtualDisk method)
To do this I take the virtualMachine object and if it has an attribute .parent then I recursively follow the .parent objects until I find one of the instance type vim.Datacenter
d) Figure out where to store the .vmdk - If you want, like me, to put it with the VM files:
rdmFilename = os.path.dirname(virtualMachine.config.files.vmPathName) + "/" + scsiLun.canonicalName + ".vmdk"
1) Create the RDM VirtualDisk device
#Create the devicespec
newVirtualDiskSpec = vim.VirtualDiskManager.DeviceBackedVirtualDiskSpec(diskType="rdm",
adapterType="lsiLogic",
device=scsiLun.deviceName)
#And create the disk with a task
createDiskTask = self.vmContent.virtualDiskManager.CreateVirtualDisk(name=rdmFilename,
datacenter=vmDatacenter,
spec=newVirtualDiskSpec)
Like all tasks, you need to wait for it to complete (or error)
2) Attach the VirtualDisk for the VM
It might appear that most of this information should be above in the VMDK, but really we're now just describing the above VMDK RDM container to to the VM.
deviceBlockCount = scsiLun.capacity.block
deviceBlockSize = scsiLun.capacity.blockSize
deviceSizeInKB = (deviceBlockSize * deviceBlockCount) / 1024
newdisk = vim.vm.device.VirtualDisk()
newdisk.deviceInfo = vim.Description()
newdisk.deviceInfo.label = scsiLun.deviceName
newdisk.deviceInfo.summary = str(deviceSizeInKB/1024/1024) + " GB"
newdisk.backing = vim.vm.device.VirtualDisk.RawDiskMappingVer1BackingInfo()
newdisk.backing.compatibilityMode = vim.vm.device.VirtualDiskOption.CompatibilityMode.physicalMode
newdisk.backing.diskMode = vim.vm.device.VirtualDiskOption.DiskMode.independent_persistent
newdisk.backing.fileName = rdmFilename # same as above in step 1
newdisk.backing.deviceName = scsiLun.deviceName
newdisk.backing.lunUuid = scsiLun.uuid
newdisk.capacityInKB = deviceSizeInKB # calculated from lun attributes
newdisk.controllerKey = scsiControllerKey # one we discovered in this VM
newdisk.unitNumber = unitNumber # calculated unused scsiid
# Create the new DiskDevice object
newdiskDevice = vim.vm.device.VirtualDeviceSpec()
newdiskDevice.device = newdisk
newdiskDevice.operation = vim.vm.device.VirtualDeviceSpec.Operation.add
# And attach it to the VM via a ReconfigVM_Task
configSpec = vim.vm.ConfigSpec(deviceChange=[newdiskDevice])
reconfigTask = virtualMachine.ReconfigVM_Task(configSpec)
And again wait for the task to complete/
Tearing it down involves finding the VirtualDisk object (I'm searching vmdisk.backing.lunUuid for the WWN I'm interested in) and
# Create a config to remove the virtualdisk
diskDevice = vim.vm.device.VirtualDeviceSpec()
diskDevice.device = vDisk
diskDevice.operation = vim.vm.device.VirtualDeviceSpec.Operation.remove
# And remove it from the VM
configSpec = vim.vm.ConfigSpec(deviceChange=[diskDevice])
reconfigTask = testVm.ReconfigVM_Task(configSpec)
Note we still have the VMDK for the RDM lying in the VM's datastore directory, so we remove that with
# Finally, delete the vmdk from the datastore
deleteDiskTask = self.vmContent.virtualDiskManager.DeleteVirtualDisk(
name=vDisk.backing.fileName,
datacenter=vmDatacenter)
#Wait for the DeleteVirtualDisk task to complete
Hope this helps.
Hi all,
I seem to remember folks doing this sometime back.
You use bootcamp, install whatever windows you want into the bootcamp partition. You can now run MacOS or boot into the Windows install in bootcamp.
But then someone mentioned or had running a VMWare Fusion (or perhaps it was Parallels) VM that ran in MacOS but was using the windows installed in bootcamp.
I'm curious if this works. I would be concerned about the drivers needing to change between native bootcamp operation and Fusion operation.
Any thoughts? Anyone doing it?
My windows XP server machine i just ported using the vmware vConverter center seems to be working fine, at the exception that i do not chose my users anymore, and that it goes directly to a user that most of the settings were locked.
That being said, i cannot open a terminal or anything, and the boot proceess, i do not see a black screen at all it just directly goes to the wndows screen..
Any possibilities here on why this is not actually working ?
I actually just need to go change this VM ip so that users can keep on logging from distance (remote desktop).
I have to mention windows does now tell me that my windows is not genuine, while i am pretty sure it was before as i never got any of those message on the actual physical machine.
Agreed - same issue here. Killing the the VMWare Fusion Start Menu.app process at the command line stops the log messages, but I suspect they will resume the next time I launch and/or shutdown a VM and exit Fusion (6.0.4).
Хорошій топік по поводу нексенти вот тут http://community.spiceworks.com/topic/220902-nexentastor-18tb-isn-t-free
Еще замечательно FreeBSD работает - всего-то делов NFS шару "оттопиріть" ))
Я для демок разних OpenSuse іспользую (тоже с NFS) как віртуальную машіну под VMware Fusion
--
В данной теме незаслуженно забыли такой продукт как Nexenta.
After many attempts to create create this not to use a shared session, I changed it to use a shared session and entered credentials. This created the view as in your screen shot. I will need to create a user account to configure this for use. When I change my password it will break. Thanks for the input
I want to disconnect an adapter from an ESXi host - VDS and move an adapter back to VSS for time being, will disconnecting the adapter at host level (Configuration tab > Networking > Manage Physical Adapters) remove the adapter from other hosts in the cluster?
It will remove the physical adapter from vDS only in host you're working.... but remember that to keep connectivity with host you will need at least two physical adapter on vDS to be able to remove one and maintain connectivity.
при всей моей фанатской любви к freebsd, винда+старвинд в разы быстрее и проще настраивается.
Thank you
EPT is required for virtualized hardware-assisted virtualization. Does server A support EPT? (i.e., is it Nehalem or later?)