Upgrade to TrueNAS CORE 13.3 and VMs stopped booting

TrueNAS General
,
1

Hi all, I’m struggling with an upgrade issue where I moved from TrueNAS-13.0-U6.7 to 13.3 and my VMs stopped booting up and I could not manually start them. I have reverted back to 13.0 U6.7 and everything is running again.

The reason I went with the update to 13.3 is that there is no mouse functionality through Bhyve and I had read another post that mentioned a fix for that was earmarked for 13.3 if that makes any sense.

Not sure what is broken between the two versions or if there is some fix it work to be done after the upgrade? Any pointers would be great!

2

Hi all, checking back on this one to see if anyone has any pointers. I am hoping to avoid creating new ones but
it’s not a huge inconvenince to do so.

I have one HAOS and one Ubuntu VM if that makes a difference.

Thanks!

3

it would be good to know what release the jails are. iocage list

4

I have one jail running a plex server that runs after the update to 13.3 and two VMs, neither of which run after the update.

The jail, for what it’s worth is 13.2 release.

5

I upgraded again today to see if there was anything else I could provide. One thing I noticed was that each time I attempted to start either of the previous VMs and also the new one I just created, there is a quick circle dialogue like when it’s trying to start and then it goes away. At the same time, I get the following lines in log file as it happens.

The vnet name ticks up one number each time regardless of which VM I try to start.

Feb 20 16:45:50 kernel: tap0: changing name to ‘vnet18’
Feb 20 16:45:50 kernel: vnet18: promiscuous mode enabled
Feb 20 16:45:50 kernel: vnet18: promiscuous mode disabled
Feb 20 16:45:51 kernel: tap0: Ethernet address: XX:ff:bc
Feb 20 16:45:51 kernel: tap0: changing name to ‘vnet19’
Feb 20 16:45:51 kernel: vnet19: promiscuous mode enabled
Feb 20 16:45:51 kernel: vnet19: promiscuous mode disabled
Feb 20 16:45:51 kernel: tap0: Ethernet address: XX:ff:bc
Feb 20 16:45:51 kernel: tap0: changing name to ‘vnet20’
Feb 20 16:45:51 kernel: vnet20: promiscuous mode enabled
Feb 20 16:45:51 kernel: vnet20: promiscuous mode disabled
Feb 20 16:45:51 kernel: tap0: Ethernet address: XX:ff:bc
Feb 20 16:45:51 kernel: tap0: changing name to ‘vnet21’
Feb 20 16:45:51 kernel: vnet21: promiscuous mode enabled
Feb 20 16:45:51 kernel: vnet21: promiscuous mode disabled
Feb 20 16:45:52 kernel: tap0: Ethernet address: XX:ff:bc
Feb 20 16:45:52 kernel: tap0: changing name to ‘vnet22’
Feb 20 16:45:52 kernel: vnet22: promiscuous mode enabled
Feb 20 16:45:52 kernel: vnet22: promiscuous mode disabled

6

Shouldn’t you upgrade the jail first to 13.3 or 13.4?

7

@ddaenen1 isn’t his problem with VMs, not jails?

@imcintyr Since I do not have this problem anywhere on my 13.3 systems, I guess we should compare VM settings. Please post everything - settings, devices, their settings … for one of the VMs.

8

I’m having similar issues. Everything worked in 13.0-U6.7, but VMs are not starting in the 13.3 build. I have tried 13.3-RELEASE and 13.3-U1.1

Here is the log entries I get starting the VM

Feb 22 17:40:56 freenas kernel: tap0: Ethernet address: 58:9c:fc:10:ff:f5
Feb 22 17:40:56 freenas kernel: tap0: changing name to 'vnet2'
Feb 22 17:40:56 freenas kernel: vnet2: promiscuous mode enabled
Feb 22 17:40:56 freenas kernel: vnet2: link state changed to UP
Feb 22 17:40:57 freenas kernel: pid 5417 (bhyve), jid 0, uid 0: exited on signal 6
Feb 22 17:40:57 freenas kernel: vnet2: link state changed to DOWN