-
-
Notifications
You must be signed in to change notification settings - Fork 184
Virtual Disks
Matt Churchyard edited this page Apr 11, 2016
·
6 revisions
When a guest is created from a template, a disk image is created for each disk specified in the template. If you would like to add disks to a guest after it has been created, you can either use the vm add
command, or create the disk image then update the configuration file manually.
Below are some examples of supported disk configurations
disk0_type="virtio-blk"
disk0_name="disk0.img"
Non sparse zvols are also supported by just specifying disk0_dev="zvol"
disk0_type="virtio-blk"
disk0_name="disk0"
disk0_dev="sparse-zvol"
This allows you to specify a custom path to a disk image. The disk could be a sparse
file, a ZVOL, or even a real disk under /dev/
disk0_type="virtio-blk"
disk0_name="/dev/ada10"
disk0_dev="custom"
disk0_type="virtio-blk"
disk0_name="disk0.img"
disk0_opts="nocache,direct"
Status
How-To / Examples
- Quickstart
- Full Example Template
- Using tmux
- Supported Guest Examples
- Disks
- Network Interfaces
- Datastores
- Virtual Switches
- NAT
- Grub Configuration
- Running Windows
- Running OmniOS
- Running Linux
- UEFI Graphics (VNC)
- Info Output Explained
- Serial Console Output with the UEFI
- VM migration
- Cloud Images
Development