[Bug 271782] VM crashes with: bhyve exited with status 0

From: <bugzilla-noreply_at_freebsd.org>
Date: Wed, 21 Jun 2023 10:57:07 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271782

--- Comment #2 from Yuri Dolgoruki <urtp5@yandex.by> ---
Mark, good day!

How can I help to provide additional diagnosting?
May problem in datastore structure for BHyVe?

I have a FS /mySSD/BHyVe in ZFS, but VM directory (/mySSD/BHyVe/Win2016) is not
a FS but regular directory. Also some messages related to "dataset does not
exists" in vm info:

zfs list | grep BHyVe
------------------
mySSD/BHyVe                               200G   226G      200G  /mySSD/BHyVe
mySSD/BHyVe/.templates                    100K   226G      100K 
/mySSD/BHyVe/.templates

ls -la /mySSD/BHyVe
------------------
drwxr-xr-x  7 root       wheel  7 Jun  2 12:15 .
drwxr-xr-x  4 root       wheel  4 Apr 28 11:00 ..
drwxr-xr-x  2 root       wheel  4 May  4 22:34 .config
drwxr-xr-x  2 root       wheel  2 May  4 21:16 .img
drwxr-xr-x  2 root       wheel  2 May  4 21:16 .iso
drwxr-xr-x  2 root       wheel  3 May  4 21:16 .templates
drwxr-xr-x  2 root       wheel  7 Jun 20 08:11 Win2016

vm info Win2016
------------------
Virtual Machine: Win2016
------------------------
  state: running (81219)
  datastore: default
  loader: uefi
  uuid: 39387cd6-e074-11ed-9e3c-d8bbc11c8171
  cpu: 4
  cpu-topology: sockets=1, cores=4
  memory: 16G
  memory-resident: 17219084288 (16.036G)

  console-ports
    com1: /dev/nmdm-Win2016.1B
    vnc: 0.0.0.0:5900

  network-interface
    number: 0
    emulation: virtio-net
    virtual-switch: public
    fixed-mac-address: 58:9c:fc:0c:3a:c7
    fixed-device: -
    active-device: -
    desc: -
    mtu:
    bridge: bridge0

  virtual-disk
    number: 0
    device-type: file
    emulation: nvme
    options: -
    system-path: /mySSD/BHyVe/Win2016/disk0.img
    bytes-size: 214748364800 (200.000G)
    bytes-used: 214794060800 (200.042G)
cannot open 'mySSD/BHyVe/Win2016': dataset does not exist
cannot open 'mySSD/BHyVe/Win2016': dataset does not exist

  clone-origin

-- 
You are receiving this mail because:
You are the assignee for the bug.