NickF
Guru
- Joined
- Jun 12, 2014
- Messages
- 763
Been doing more testing in SCALE as I am committed to help push the limits where I can. I have a weird bug that I filed today.
I can't create a VM with an existing ZVOL I just created in latest nightly on an Alderlake box. Tomorrow I'll probably do a re-install on stable (only tried nightly because Kernel 5.15) to see if the problem persists. Before I do that, does anyone have a work around I can potentially employ to get me past this stopping point?
Log in with Atlassian account
Log in to Jira, Confluence, and all other Atlassian Cloud products here. Not an Atlassian user? Sign up for free.
ixsystems.atlassian.net
Testing on TrueNAS-SCALE-22.12-MASTER-20220815-015219
Intel Core i5 12600T, 16GB RAM, two 512GB NVME drives, Intel i219 ethernet
Hi,
I created a ZVOL nested inside of a dataset. I named it, checked the "Force Size" and "Sparse" checkboxes, and inherited everything else.
I tried to add that ZVOL as an existing drive to a VM in the wizard, or as a device after the VM was created. In either case the UI doesn't "see" the ZVOL.
If I navigate VIA SSH to /dev/zvol/nvmed/vms I can see the ZVOL
I can't create a VM with an existing ZVOL I just created in latest nightly on an Alderlake box. Tomorrow I'll probably do a re-install on stable (only tried nightly because Kernel 5.15) to see if the problem persists. Before I do that, does anyone have a work around I can potentially employ to get me past this stopping point?