Hello, 

 

I have just installed version 7.0 . When creating a VM I have noticed that it is now also creating a share with the same name. Is this normal?

 

Thanks,

 

Andrew

Edited January 14, 20251 yr by andrewhuk

Any folder at the top level of array disk or pool is automatically a user share. Always has been even before v6 allowed VMs.

It's strange that they were never shown in my shares tab when I was using V6. Thanks for your feedback.

I noticed them too since 7.0, even after deleting the VMs they're still there and if I delete the folders they are recreated at the next boot, don't think this is normal behavior.

 

Edited January 14, 20251 yr by bubbl3

What paths did you specify when creating the VM?

That's the thing, I did not setup shares for them.

It isn't necessary to setup a user share to get a user share.

54 minutes ago, trurl said:

Any folder at the top level of array disk or pool is automatically a user share. Always has been even before v6 allowed VMs.

Just specifying a path at the top level of array or pool will automatically result in a user share named for that top level folder. Doesn't matter whether this is the result of using VMs or some other reason.

I get that, but it doesn't really explain my issue, the VMs do not exist anymore, i deleted those 2 shares configuration wise and removed the folders. But they're gonna be recreated the next time i start the array. It's puzzling.

12 minutes ago, trurl said:

or some other reason.

Are you sure nothing else is specifying a path at the top level of array or pool? Container, script, ...

Decided to dig in, stopped the array and deleted the .cgf files manually


Started the array and shares were in the UI, deleted them again, stopped the array.

 

Verified cfg files were not there anymore, started the array again and now they're gone.

I had them since RC1, so may be a fixed issue as new VMs don't create random shares anymore unless i define them.

Edited January 14, 20251 yr by bubbl3

This can happen if the domains share resides on a zfs pool and the folder is not a dataset, it creates a share with the VM name on the pool, it should be fixed soon, for now, you can just ignore and delete those shares, you can also make domains a dataset and the issue will no longer occur.

HI JorgeB.

 

I am new to this. How would I make a domain a dataset? 

 

Thanks,

Andrew

If you disable VM service and delete/rename the existing one, it should create a new one as a dataset, not that if you have existing VMs, you would need to copy the vdisks back after.