search

churchers / vm-bhyve

Shell based, minimal dependency bhyve manager
BSD 2-Clause "Simplified" License
839 stars 179 forks source link

clone after vm renamed #36

Open WanpengQian opened 8 years ago

WanpengQian commented 8 years ago

Here is the story...

root@bhyve:~ # vm snapshot vm01@test
root@bhyve:~ # vm rename vm01 newvm01
root@bhyve:~ # vm clone newvm01@test newvm02
mv: rename /zones/vm/newvm02/newvm01.conf to /zones/vm/newvm02/newvm02.conf: No such file or directory
tail: /zones/vm/newvm02/newvm02.conf: No such file or directory

Maybe for vm, the config name just a fixed name such as vm.config ?

churchers commented 8 years ago

I haven't forgotten about this issue. As you mention, the only real fix for this is to have a standard config file name. We could try and scan the guest directory for a .conf file, but that isn't ideal.

I am still considering the option of changing the config file name, but this obviously needs to be carefully planned. Either users will have to rename guest config files (with us providing some sort of UPDATING bulletin), or I'll have to try and automate it.