Virtual machines do not start

Description

upgraded from Truenas 12.1 dailies from March 31st, no issues with VM's booting now after 13.0 upgrade they fail to start, they create a core dump which is attached, and in /var/log/libvirt/bhyve/3_Portainer.log

/usr/sbin/bhyve -c cpus=2,sockets=1,cores=2,threads=1 -m 1024 -A -w -H -s 0:0,hostbridge -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd -s 3:0,ahci,hd:/dev/zvol/Volume_1/Portainer-3tzt9v -s 30:0,xhci,tablet -s 31,lpc -s 2:0,ahc>
Assertion failed: ((nvl) != ((void *)0)), function nvlist_find, file /data/workspace/TrueNAS_13.0_Nightlies/freenas/_BE/os/sys/contrib/libnv/nvlist.c, line 387.

Problem/Justification

None

Impact

None

Linked work items

is cloned by

NAS-114387

Upstream bhyve ahci config regression fix

Activity

Jared

February 2, 2022 at 6:40 PM

New Debug upload if required

Jared

February 2, 2022 at 6:40 PM

The last two dailies released, have the bhyve/virtual machines booting as i can access portainer and its objects, BUT cannot access VNC either the builtin noVNC, which loads but fails to connect, and when i use realVNC.

Running:
TrueNAS-13.0-MASTER-202202020601

Ryan Moeller

January 19, 2022 at 4:37 PM

This appears to be a regression in bhyve on FreeBSD stable/13. I'll forward a bug report to people working on bhyve.

Michelle Johnson

January 17, 2022 at 1:10 PM

Thanks you for your report, @Jared

This issue ticket is now in our queue for review. An engineering representative will update with further details or questions in the near future.

Jared

January 15, 2022 at 5:35 AM

also received

Error: [Errno 32] Broken pipe

when doing this error report under support on Truenas, had to manually upload attachments

Resize work item view side panel

Complete

Details

Assignee

Ryan Moeller(Deactivated)

Reporter

Jared

Labels

NoDocsImpactfrom_uiready_for_review

Time remaining

Components

Fix versions

13.0-BETA1

Affects versions

Master - TrueNAS Nightlies

Priority

Medium

Katalon Platform

Created January 15, 2022 at 5:30 AM

Updated July 1, 2022 at 2:38 PM

Resolved January 19, 2022 at 8:17 PM