Quantcast
Channel: VMware Communities: Message List
Viewing all 187854 articles
Browse latest View live

Re: About Live Storage Migration in VMware ESX5.1

0
0

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:

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-vsphere-storage-api-array-integration…

 

 

 

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


Relationships between Application (deployment) and VM's (VMware Virtual Machine Instance)???

0
0

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

Re: Win10 Workstation USB won't work

0
0

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

Re: Can the ITSM plugin gather more detail from the vRA VM instance to place into the CMDB?

0
0

Any updates on extra fields being passed into CMDB such as IP address, Storage info, Datastores, Cluster?


Dave

Re: The connection for the USB device was unsuccess (all usb devices)

Re: VMware 5.1 VM with large RDM - options to get VM into Vcenter 6.0 system?

0
0

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.

Re: Problem to mount a USB stick

0
0

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

 

 

Re: VMware Fusion for Mac 10.13 High Sierra Support

0
0

exact same error here.


vSphere Web Client SDK 6.5 error when accessing the web client through local host

0
0

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

Re: Can't Import Certificate running Add Powershell Host Workflow

0
0

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.

Re: VMware Workstation has stopped working!!

0
0

No, this doesn't fix it. I can't believe that still fail after than 2 months.

Re: VMware Workstation has stopped working!!

0
0

Delete .lck folders and try again.

Re: No valid connection to the host

0
0

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.

Re: new-vm menu option

0
0

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]

 

Re: Unmount datastores from all hosts

0
0

Try something like this

 

Get-Datastore-Name (Get-Contentdatastores.txt) |%{

    $esx=Get-View-Id$_.ExtensionData.host[0]

    $storSys=Get-View-Id$esx.ConfigManager.StorageSystem

    $storSys.UnmountVmfsVolume($ds.ExtensionData.Info.vmfs.uuid)

}

 


After RDM resize script shows old disk size instead of new

0
0

Hi All,

 

After RDM resize, below script still shows the old size but in the guest, I can see the new size capacity.

 

RDM is presented as Physical currently

 

Get-VM db1 | Get-HardDisk | where {"RawPhysical","RawVirtual" -contains $_.DiskType} | Select @{N="VM";E={$_.Parent.Name}},Name,CapacityGB,ScsiCanonicalName

 

Please help

 

Thanks

Madhusudan

Re: Unmount datastores from all hosts

0
0

That shouldn't be $ds but $_, I updated the code

Re: After RDM resize script shows old disk size instead of new

0
0

Does it keep giving the old size?

Normally the datastore info is updated on an interval, did you check after a couple of minutes?

Re: After RDM resize script shows old disk size instead of new

0
0

Yes, I tried after 1 hour, 1 days and after a week.

 

New size doesnt show in cli or report. But when I login to the VM, I can see

VMWare Fusion 8.5.8 Not recognizing USB

0
0

Can you please help me if anyone has the answer to my issue?  I am running VMware Fusion 8.5.8 and it does not recognized the USB ports. I uninstalled it and  I went back to the previews version WMw 8.5.7 I was using but it is not working either.  Any help would be appreciated. Thank you

Viewing all 187854 articles
Browse latest View live




Latest Images