"Fossies" - the Fresh Open Source Software Archive

Member "vagrant-2.2.14/website/pages/docs/disks/vmware/common-issues.mdx" (20 Nov 2020, 1801 Bytes) of package /linux/misc/vagrant-2.2.14.tar.gz:

As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 ---
    2 layout: docs
    3 page_title: Common Issues - Disks VMWare Provider
    4 sidebar_title: Common Issues
    5 description: |-
    6   HashiCorp develops an official VMware Fusion and VMware Workstation provider
    7   for Vagrant. This provider allows Vagrant to power VMware based machines and
    8   take advantage of the improved stability and performance that VMware software
    9   offers.
   10 ---
   12 # Common Issues and Troubleshooting
   14 This page lists some common issues people run into with Vagrant and VMWare
   15 as well as solutions for those issues.
   17 ## Are my disks attached?
   19 A handy way to figure out what disks are attached (or not attached) to your guest
   20 is to open up the VMWare GUI and open up the guest settings and selecting the
   21 disks options.
   23 ## How many disks can I attach?
   25 Vagrant will attempt to attach all disks specified in the Vagrantfile. If more than
   26 four `ide` type disks are specified, only the first four will be attached. 
   28 ## Applying Vagrant disk configuration changes to guests
   30 Due to how VMware works, you must reload your guest for any disk config changes
   31 to be applied. So if you update your Vagrantfile to update or even remove disks, make
   32 sure to `vagrant reload` your guests for these changes to be applied. Also note, that 
   33 Vagrant will not decrease the size of a disk.
   35 ## Disk functionality with snapshots
   37 If snapshots exist for a VM, disk functionality will be limited. Vagrant will return
   38 an error for any actions that are limited due to the existence of snapshots. In order
   39 to restore functionality the snapshots must be removed. This can be done using the
   40 [`vagrant snapshot delete`](/docs/cli/snapshot) command. To delete all snapshots 
   41 for a VMWare backed VM try `vagrant cap provider delete_all_snapshots --target <target vm name>`.
   42 Note once a snapshot is deleted, it can not be restored.