VM does not start after cloning

[mykolaq]

i have created vm, installed some packages and made some comfigurations. After that i made clone of this vm and now it doesnt work (have no access to disk).

is it ok?

 

[KrisBee]

What version of FreeNAS are you using? Your images are too small to see. So, is it the original VM that does not boot, or the clone?

 

[mykolaq]

What version of FreeNAS are you using? Your images are too small to see. So, is it the original VM that does not boot, or the clone?

Sorry for images.
FreeNAS-11.1-U6
Both.

 

[KrisBee]

Is this still a problem? Cloning a debian VM works for me on FreeNAS-11.1-U6. What OS is running in your VM? Have you checked that NIC, VNC and disk devices are still correctly attached to the VM?

Could you (re)post any screen caps so they are legible. Before you re-test check you don't have any bhyve processes running on VMs that where not stopped properly after failed boots. A combination of bhyvectl --force-poweroff --vm=xxxx and bhvyectl --destroy --vm=xxxx , or the destroy command on its own, should clear those.

Also at the FreeNAS CLI have a look at the middlewared.log to see what clues it provides as you boot the original and clone VM with tail -f /var/log/middlewared.log

 

[mykolaq]

Is this still a problem? Cloning a debian VM works for me on FreeNAS-11.1-U6. What OS is running in your VM? Have you checked that NIC, VNC and disk devices are still correctly attached to the VM?

Could you (re)post any screen caps so they are legible. Before you re-test check you don't have any bhyve processes running on VMs that where not stopped properly after failed boots. A combination of bhyvectl --force-poweroff --vm=xxxx and bhvyectl --destroy --vm=xxxx , or the destroy command on its own, should clear those.

Also at the FreeNAS CLI have a look at the middlewared.log to see what clues it provides as you boot the original and clone VM with tail -f /var/log/middlewared.log

in logs something like:

Code:

[2018/09/28 12:18:29] (DEBUG) VMService.run():155 - ====> NIC_ATTACH: igb2
[2018/09/28 12:18:29] (DEBUG) VMService.run():231 - Starting bhyve: bhyve -H -w -c 1 -m 2048 -s 0:0,hostbridge -s 31,lpc -l com1,/dev/nmdm4A -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -s 3,e1000,tap0,mac=00:a0:98:72:88:98 -s 4,virtio-blk,/dev/zvol/Mirror/zullip -s 29,fbuf,vncserver,tcp=192.168.3.221:5904,w=1024,h=768,password=98912142, -s 30,xhci,tablet 4_zullip
[2018/09/28 12:18:29] (DEBUG) VMService.run():244 - ==> Start WEBVNC at port 5804 with pid number 32415

i cant see info about attaching disk. is it ok?

upd: understood about disks.

Code:

virtio-blk,/dev/zvol/Mirror/zullip -s 29

 

[KrisBee]

So, if you "exit" the EFI to use the "Boot Maintenance Manager" and then select "Boot from file" to locate and select your relevant <something>64.efi file, does it boot?

 

[mykolaq]

So, if you "exit" the EFI to use the "Boot Maintenance Manager" and then select "Boot from file" to locate and select your relevant <something>64.efi file, does it boot?

thank you for help. live and learn :)now it is booting. and i fixed boot order