https://github.com/thbishop/fission

command line tool to manage vmware fusion vms
https://github.com/thbishop/fission

Keywords from Contributors

activejob activerecord mvc chef

Last synced: about 22 hours ago
JSON representation

Repository metadata

command line tool to manage vmware fusion vms

Host: GitHub
URL: https://github.com/thbishop/fission
Owner: thbishop
License: mit
Created: 2011-05-12T21:44:49.000Z (almost 15 years ago)
Default Branch: master
Last Pushed: 2013-10-05T05:31:06.000Z (over 12 years ago)
Last Synced: 2026-02-22T19:49:04.357Z (9 days ago)
Language: Ruby
Homepage:
Size: 728 KB
Stars: 80
Watchers: 3
Forks: 22
Open Issues: 6
Releases: 0
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE

Fission

Intro

Fission is a simple command line tool for managing VMware Fusion VMs. Only Fusion 3.x is currently
supported. See Fusion Version Support for more info.

Install

gem install fission

Usage

Clone

fission clone existing_vm new_vm [--start]

If you provide '--start', then the new VM will be powered on after cloning

Delete

fission delete my_vm [--force]

Deletes the VM. This will delete the files from disk and remove the related metadata in Fusion.

By default, the VM will not be deleted if:

The VM is running
The Fusion GUI is running (as the metadata cannot be cleanly removed)

Providing '--force' will:

Stop the VM if it's running
Delete the VM even if the Fusion GUI is running

Info

fission info my_vm

Outputs information about the VM

Snapshot Create

fission snapshot create my_vm snapshot_name

Creates a snapshot for the VM

In order to create the snapshot:

The VM must be running
The snapshot name must be unique

Snapshot Delete

fission snapshot delete my_vm snapshot_name

Deletes a snapshot for the VM

If you have the Fusion GUI running, the VM must be running in order to delete the snapshot.

Snapshot List

fission snapshot list my_vm

Lists the snapshots for the VM

Snapshot Revert

fission snapshot revert my_vm existing_snapshot

Reverts a VM to an existing snapshot

In order to revert to the snapshot:

The Fusion GUI cannot be running

Start

fission start my_vm [--headless]

Starts the VM

Providng '--headless' will start the VM without a Fusion GUI console

Note that the Fusion GUI cannot be running to start a VM with '--headless'

Status

fission status

Displays the status (running or not) of all of the VMs found

Stop

fission stop my_vm

Stops the VM

Suspend

fission suspend [my_vm | --all]

Suspends the VM or all running VMs

Help

fission -h

or just

fission

Configuration

By default, fission will use the default VMware Fusion VM directory
(~/Documents/Virtual Machines.localized/) when cloning. If you want to use a
different directory, you can set this in a config file.

The config file needs to be in YAML format and live at '~/.fissionrc'

$cat ~/.fissionrc
---
vm_dir: "/vm"

Fusion Version Support

As of now, only Fusion 3.x is supported (that's what I have available to test).
It's my understanding that some folks are currently using fission with Fusion
4.x as well. In order to have fission work with Fusion 4.x, you will need to
tell fission where the Fusion 4.x vmrun file is. You can do so with the
following item placed in your ~/.fissionrc (remember, YAML format):

vmrun_bin: /Applications/VMware Fusion.app/Contents/Library/vmrun

Other Notable Info

The name of the VM used in the previous examples should be the directory name
of the VM minus the '.vmwarevm' extension. Typically the VM name and the
directory name are the same.

As of now, VMware Fusion doesn't provide an easy, out of
the box, way to modify the personality (hostname, ip, etc.) of a VM. Because of
this, a clone created by fission is an exact copy of the original (including
hostname, ip address, etc.). Most likely, this isn't what you want.

One approach is to create a VM which will act as a template. Create the VM with
the desired install method (ideally with easy install) and settings, but do not
power on the VM. You can then create clones from this VM 'template'. When you
power on the clone, it will start the OS install process (and assign a new ip, etc.).

Fission with RVM

Please see the following gist for a walkthrough of making fission available
regardless of ruby environment when using RVM https://gist.github.com/1203167

Contribute

Fork the project
Make your feature addition or bug fix (with tests and docs) in a topic branch
Bonus points for not mucking with the gemspec or version
Send a pull request and I'll get it integrated

License

See LICENSE

Owner metadata

Name: Tommy Bishop
Login: thbishop
Email:
Kind: user
Description:
Website:
Location: San Diego, CA
Twitter:
Company:
Icon url: https://avatars.githubusercontent.com/u/5088?u=37b0f0e26b69f8ca74db47078311e6e007859fdd&v=4
Repositories: 40
Last ynced at: 2023-04-21T10:48:02.584Z
Profile URL: https://github.com/thbishop

GitHub Events

Total

Last Year

Committers metadata

Last synced: about 24 hours ago

Total Commits: 309
Total Committers: 9
Avg Commits per committer: 34.333
Development Distribution Score (DDS): 0.065

Commits in past year: 0
Committers in past year: 0
Avg Commits per committer in past year: 0.0
Development Distribution Score (DDS) in past year: 0.0

Name	Email	Commits
Tommy Bishop	b**s@g**m	289
Erik Michaels-Ober	s**k@g**m	9
Cody Herriges	c**s@g**m	5
Wayne E. Seguin	w**n@g**m	1
Taliesin Sisson	t**s@y**m	1
Pat Downey	p**y@g**m	1
David Calavera	d**a@g**m	1
jtimberman	j**a@o**m	1
Nigel Kersten	n**l@p**m	1

Committer domains:

puppetlabs.com: 1
opscode.com: 1

Issue and Pull Request metadata

Last synced: 7 days ago

Total issues: 19
Total pull requests: 17
Average time to close issues: 6 months
Average time to close pull requests: 14 days
Total issue authors: 13
Total pull request authors: 10
Average comments per issue: 1.84
Average comments per pull request: 1.94
Merged pull request: 14
Bot issues: 0
Bot pull requests: 0

Past year issues: 0
Past year pull requests: 0
Past year average time to close issues: N/A
Past year average time to close pull requests: N/A
Past year issue authors: 0
Past year pull request authors: 0
Past year average comments per issue: 0
Past year average comments per pull request: 0
Past year merged pull request: 0
Past year bot issues: 0
Past year bot pull requests: 0

More stats: https://issues.ecosyste.ms/repositories/lookup?url=https://github.com/thbishop/fission

Top Issue Authors

nigelkersten (4)
ody (3)
jedi4ever (2)
danielqo-zz (1)
bf4 (1)
thbishop (1)
matschaffer (1)
mattray (1)
bkhl (1)
taliesins (1)
pravi (1)
jasonberanek (1)
sferik (1)

Top Pull Request Authors

sferik (5)
ody (3)
jedi4ever (2)
jtimberman (1)
codegoalie (1)
wayneeseguin (1)
taliesins (1)
nigelkersten (1)
calavera (1)
patdowney (1)

Top Issue Labels

feature (4)
bug (3)

Top Pull Request Labels

feature (4)
bug (1)

Package metadata

Total packages: 8
Total downloads:
- rubygems: 87,433,186 total
Total docker downloads: 4,174,520
Total dependent packages: 30 (may contain duplicates)
Total dependent repositories: 7,192 (may contain duplicates)
Total versions: 26
Total maintainers: 1

gem.coop: fission

A simple utility to manage VMware Fusion VMs from the command line

Homepage: https://github.com/thbishop/fission
Documentation: http://www.rubydoc.info/gems/fission/
Licenses: mit
Latest release: 0.5.0 (published over 12 years ago)
Last Synced: 2026-03-01T21:01:32.841Z (2 days ago)
Versions: 10
Dependent Packages: 0
Dependent Repositories: 0
Downloads: 43,716,882 Total
Docker Downloads: 2,087,260
Rankings:
- Dependent repos count: 0.0%
- Dependent packages count: 0.0%
- Average: 0.489%
- Downloads: 0.551%
- Docker downloads count: 1.403%
Maintainers (1)
- thbishop

rubygems.org: fission