Team,
I’m running a macOS Sierra 10.12.5 VM on ESXi 6.5 but when I change the VM resolution to the same as the native resolution of my MacBook Pro 15” w/ Retina (2880×1800) the image is too large for the screen. A VM resolution of 1440×900 creates the correct size image but it’s not very sharp; it’s somewhat blurry. Any idea on how I can correct this? Thanks in advance!
Regards,
Brad
hello,you can look at website below,hope can help you.
VMware 12.5.7 is out, and I can confirm that this now works OK with Kernel 4.12 (tested with 4.12-rc6)
Thanks!
Robert Gadsdon
rglinuxtech.com
Thanks for your help~ Sureshkumar M,
Actually, I have a Windows 7 VM, which is the thin-provisioned VM and the used space is 75.6GB.
Current VM spaces (Used 75.6GB):
Current datastore used space on the VM (Have the Virtual Disk of the VM used 85,829,632.00 KB ~around 85 GB):
Can reclaim the space of 10 GB back???... Now, I deleted more 5GB. When can it reclaim back? Local Disk cannot reclaim??
Have configured alarm action to run a command, Is there a way for me to pass the Esxi host name for which the alarm has been triggered ?
TIA
BACKUP THE DATABASE, then connect to the database and execute the SQL command:
alter table VPX_EXT_PRIVS drop constraint PK_VPX_EXT_PRIVS
...then try the upgrade again.
vCenter Upgrade from 5.1 to 6.0 with external SQL 2008 fails during schema validation
How Storage vMotion Works
1. First, vSphere copies over the nonvolatile files that make up a VM: the configuration file (VMX), VMkernel swap, log files, and snapshots.
2. Next, vSphere starts a ghost or shadow VM on the destination datastore. Because thisghost VM does not yet have a virtual disk (that hasn’t been copied over yet), it sits idle waiting for its virtual disk.
3. Storage vMotion fi rst creates the destination disk. Then a mirror device—a new driver that mirrors I/Os between the source and destination—is inserted into the data path between the VM and the underlying storage. SVM Mirror Device Information in the Logs If you review the vmkernel log fi les on an ESXi host during and after a Storage vMotion operation, you will see log entries prefi xed with SVM that show the creation of the mirror device and that provide information about the operation of the mirror device.
4. With the I/O mirroring driver in place, vSphere makes a single-pass copy of the virtual disk(s) from the source to the destination. As changes are made to the source, the I/O mirror driver ensures that those changes are also reflected at the destination.
5. When the virtual disk copy is complete, vSphere quickly suspends and resumes in order to transfer control over to the ghost VM created on the destination datastore earlier. This generally happens so quickly that there is no disruption of service, as with vMotion.
6. The files on the source datastore are deleted.
Reference:
Book Titled "Mastering VMware vSphere 5.5" by Nick Marshall and Scott Lowe
Note: More on I/O mirroring driver
• fsdm
– This is the legacy Data Mover, the most basic version. It is the slowest because the data moves all the
way up the stack and then down again.
• fs3dm
(software) – This is the software Data Mover, which was introduced with vSphere 4.0 and contained
some substantial optimizations whereby data does not travel through all stacks.
• fs3dm
(hardware) – This is the hardware offload Data Mover, introduced with vSphere 4.1. It still is the fs3dm,
but VAAI hardware offload is leveraged with this version. fs3dm is used in software mode when hardware
offload (VAAI) capabilities are not available.
Reference:
When the source filesystem uses a different blocksize from the destination filesystem, the legacy datamover (FSDM) is used. When the blocksizes of source and destination are equal, the new datamover (FS3DM) is used. FS3DM uses VAAI or just the software component. In either case, null blocks are not reclaimed.
Reference:
Storage vMotion to thin disk does not reclaim null blocks (2004155) | VMware KB
If you found this or any other answer helpful, please consider the use of the Helpful to award points.
Best Regards,
Deepak Koshal
CNE|CLA|CWMA|VCP4|VCP5|CCAH
Is there a way to show these relationships in vRA? Ideally, we'd want all the networks and associated items that come along with the deployment to fall under a parent/child relationship.
Dave
This is probably caused by USB devices with remote device wakeup capability.
You can try if the following steps work around the issue
1. Go to device manager on the host
2. Right click on the failing device
3. Click on the 'Power Management' tab
4. Uncheck 'Allow the computer to turn off this device to save power
Thanks,
Lance
Any updates on extra fields being passed into CMDB such as IP address, Storage info, Datastores, Cluster?
Dave
Due to unforseen circumstances we had to cancel our conversion, but we ran a test instead.
We used our SAN to create a copy of the 9 TB LUN/RDM.
We attached that copy to a test VM in Vcenter v5.5
We used a cold storage vmotion to convert the RDM to a thin-provisioned VMDK.
The data traversed a 10GB fibre link, but our old SAN is limited to 4 GB fibre channel (due to old Cisco switch), whilst new SAN has 10 GB links. Basically we're limited to a 4 GB fibre channel speed.
The RDM only had 3.13 TB of used space (just an FYI).
The conversion took 17 hours.
In case anyone is wondering.
Check if it's caused by power management
You can try if the following steps work around the issue
1. Go to device manager on the host
2. Right click on the failing device
3. Click on the 'Power Management' tab
4. Uncheck 'Allow the computer to turn off this device to save power
If the above does not work for you, try connect the device to one of the back pane ports which usually directly connect to the root hub and has sufficient power
Thanks,
Lance
exact same error here.
I have been working through the documentation for the setup of VMware 6.5 Web Client SDK and am currently trying to get the hello world plug-in working. I finally got the virgo server to start, but when I try to access the web client from local host I get the following error:
This site can’t be reached
localhost unexpectedly closed the connection.
Try:
Checking the connection
Checking the proxy and the firewall
Running Network Diagnostics
ERR_CONNECTION_CLOSED
I also received the same error message with the fire wall disabled. I was wondering if anyone could provide some insight into this?
Best,
Eric
Hi,
Is this PowerShell version 5.1? We are aware of the incompatibility issue of current vRO PowerShell plug-in with version 5.1 of PowerShell, and we are working on a fix. Hopefully, an updated plug-in build will be released soon.
BTW, we have some customers reporting that this issue is not reproducible with the latest Windows versions (Windows 10/Windows Server 2016); only Windows 8/Windows Server 2012 and older versions are affected.
No, this doesn't fix it. I can't believe that still fail after than 2 months.
Delete .lck folders and try again.
Were the hosts connected to this vCenter at any time? Or another vCenter?
Are you able to ping the Host(s) form the vCenter Appliance console?
Let me know if this is the right direction for your issue.
No need to use a Switch, unless your Datastore selection options depend on the remote office selection.
If not, you could do something along these lines.
If there is more logic involved to determine the New-VM parameters, you will have to build in that logic.
Note that the New-VM cmdlet at the end is not complete.
[int]$RemoteOffice=0
while ( $RemoteOffice-lt1-or$RemoteOffice-gt4 ){
Write-host"1. SF"
Write-host"2. SD"
Write-host"3. AST"
Write-host"4. Quit and exit"
[Int]$RemoteOffice=read-host"Please enter an option 1 to 4..."
}
if($RemoteOffice-eq4){
return
}
$dsNames='DS1','DS2','DS3'
[int]$dsName=0
while ( $dsName-lt1-or$dsName-gt4 ){
Write-host"1. DS1"
Write-host"2. DS2"
Write-host"3. DS3"
Write-host"4. Quit and exit"
[Int]$dsName=read-host"Please enter an option 1 to 4..."
}
if($dsName-eq4){
return
}
New-VM-Name$vmName-Datastore$dsNames[$dsName]
