Binary Buddha
Contributor
- Joined
- Mar 6, 2016
- Messages
- 126
Code:
sectorsize: 0 type: AHCI path: /dev/zvol/MAIN/JAILS/Centos-aqnqfq
So, when I created the VM it stated to location to be
Code:
/mnt/MAIN/JAILS
JAILS is a dataset in the MAIN zfs pool.
-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum has become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
Bhyve "disk" location explanation
- Thread starter Binary Buddha
- Start date
So, when I created the VM it stated to location to be
JAILS is a dataset in the MAIN zfs pool.
D
dlavigne
Guest
Did you find the answer to your question?
Binary Buddha
Contributor
- Joined
- Mar 6, 2016
- Messages
- 126
Nope. And apparently stating an ISO as a "RAW" file didn't work the way I thought it would.
D
dlavigne
Guest
That location looks correct according to the definition of RAW at https://www.ixsystems.com/documentation/freenas/11.2/virtualmachines.html#vms-raw-file. Does that answer your question?
Binary Buddha
Contributor
- Joined
- Mar 6, 2016
- Messages
- 126
I found out my confusion. Apparently I needed to state an ".img" file with the location. Although, the question now is what image formats are used? VDI? VMDK? ISO?
D
dlavigne
Guest
Did you find the answer to that last question?
Binary Buddha
Contributor
- Joined
- Mar 6, 2016
- Messages
- 126
Not yet.
Ok, let me see if I can explain this properly.
You can have two elements backing a virtual hard drive, for now at least.
1. A file, which has it's own limitations
2. A zvol which, again, has it's own particularity
A zvol is similar to a logical volume. This allows zfs to work its magic whereas the image file strategy does not allow, zfs sees a file and treats your data as a file in a data set.
The problem with zvols is that you don't have access to your data from freenas just as a regular dataset and your data doesn't look like a file which you can easily copy. But you can make snapshots of a zvol, you can replicate them, copy them locally so you may let's say go back in time with a vm that was messed up.
All in all you want zvols, not image files. Oh and zvols can be grown without stopping the vm. You know almost prod like :D
P.S.: Don't try to clone a VM just yet, the UI errors out. You can do it by hand.
You can have two elements backing a virtual hard drive, for now at least.
1. A file, which has it's own limitations
2. A zvol which, again, has it's own particularity
A zvol is similar to a logical volume. This allows zfs to work its magic whereas the image file strategy does not allow, zfs sees a file and treats your data as a file in a data set.
The problem with zvols is that you don't have access to your data from freenas just as a regular dataset and your data doesn't look like a file which you can easily copy. But you can make snapshots of a zvol, you can replicate them, copy them locally so you may let's say go back in time with a vm that was messed up.
All in all you want zvols, not image files. Oh and zvols can be grown without stopping the vm. You know almost prod like :D
P.S.: Don't try to clone a VM just yet, the UI errors out. You can do it by hand.
